JuiceVendor Labs (Outdated)
WebsiteTwitterONEUpdated WP
  • 🍧JuiceVendor Labs
  • JVL Suite
    • 🥂Champagne
      • 🐒Ape Follow Ape
      • 🎁Reward Options
      • 🔒Security & Privacy
      • ⛓️Supported Chains
      • 🖥️Desktop Guide
      • 📱Mobile Guide
      • ❓Holder FAQ
    • 🍹Mojito
      • 🍸Features Overview
      • 🏡Auctions & Raffles
      • 🛍️Marketplace (Shop)
      • 🎁Giveaways
      • 🐎Quests
      • ⚔️Engagement Battles
      • 🪙PFP Rewards (Coming Soon)
      • 📩Weighted Polls
      • 🏅Daily Role Rewards
      • ⏱️Message Scheduling
      • ⬆️Leveling
      • 🛡️Abuse Prevention
      • ⛓️Supported Chains
    • 🚦Signup Process
    • 💵JVL Suite Pricing
    • ❔FAQ
  • About
    • 📙History
    • 👑Team
    • ☎️Contact Us
Powered by GitBook
On this page
  • Security
  • Data Privacy
  1. JVL Suite
  2. Champagne

Security & Privacy

PreviousReward OptionsNextSupported Chains

Last updated 1 year ago

Security

The Champagne Protocol relies fully on read-only permissions (for wallet and Twitter) and publicly available data. The system is not custodial, JVL has no control over holder assets or any of your existing contracts/wallets.

The only thing that the system needs on the Twitter side is to verify that the holder is the owner of that Twitter account. No other permissions are needed.

Data Privacy

JuiceVendor collects depersonalized data for the usage of each project. No data collected can be tied to any individual, and is available only to that specific project. These statistics are for founders' eyes only to help reinforce educated decisions, but cannot be used to target anyone specifically.

🥂
🔒
Phantom & Metamask permissions request.
Twitter account permissions.