What this platform is
vodka hosts Lua scripts on behalf of developers and controls who may receive them. A player who wants access completes the requirements a developer configured and receives a licence key. The platform records whether that worked.
Data we collect
Account data. Email address, a password hash, and the timestamps of registration and login. Passwords are stored as scrypt hashes with per-account salts; they are never stored in readable form.
Network data. We never store a full IP address. Requests are truncated to their network prefix (/24 for IPv4, /48 for IPv6), which identifies a network, not a household. Where a correlatable identifier is needed for rate limiting, it is an HMAC that includes the current UTC date, so the link closes at midnight by construction.
Country. Approximate country is derived from server-observed network information, never from a value the client submits. It is country-level only. No location is ever claimed more precise than that.
Reported player identity. A Roblox user ID, username, display name and place ID are supplied by the client that runs the loader. A modified client can send anything. These fields are stored with a reported_ prefix, marked self-reported in activity views and exports. Premium licenses bind to a site account and a Roblox account ID; the loader must report that bound ID to use the license. This match is an access condition, not proof that a modified client controls the Roblox account. Detailed player activity is visible to the script owner and authorized administrators.
Uploaded source code
Original Lua/Luau source, saved drafts and protected output are stored privately with application-level authenticated encryption. Developers can read their own originals and version history. Authorized platform administrators can inspect originals and protected output for support and platform operation; every administrator source access is recorded with the administrator, script, version and time.
Source versions are retained so you can recover earlier work. Deleting a script disables delivery and gives you 30 days to restore it. After that window, stored original source, drafts and protected artifacts are cleared by scheduled maintenance. Originals are never included in public loader responses. Authorized clients receive protected source, which they can inspect; obfuscation deters casual copying and does not guarantee confidentiality after delivery.
Discovery and premium access
Active published scripts appear in Discovery automatically unless unlisted by their owner or an administrator. Listing titles, descriptions, media, supported games, tags, changelogs, creator names and verification badges are public. Comments, ratings and aggregate view/execution counts are public; original source and individual player histories are private. Catalog views are deduplicated using an account or a network/browser hash.
Premium purchases are arranged directly through the administrator on Discord. vodka stores the issued license, its hashed key, bound site account and Roblox ID, activation/expiry and support audit records. The site does not collect payment-card details.
Hardware binding and Discord
HWID locking is off by default and enabled per script by its owner. When on, the loader reports the executor's own client id and the key binds to the first machine that uses it, so a leaked key will not work on a second device. The value is a self-reported machine id used only to compare device against device — it is not a browser or cross-site fingerprint, and it is stored only while binding is enabled. A player can reset their own binding a bounded number of times.
The optional Discord integration stores Discord account ids: a creator who links their account (to be recognised as the owner of their scripts in the bot) and a player's id when they redeem a key through the bot, so the bot can show that player only their own keys. A monetized key step stores the creator's own ad-link id and a sealed anti-bypass secret — never a balance and never anything the ad provider holds on the creator's behalf.
What we do not do
No raw IP storage. No covert device fingerprinting and no cross-site tracking. No advertising trackers. No selling or sharing of data. No precise location. The key page sets no analytics cookies; the loader runs inside Roblox and has no browser cookies at all.
Retention
- Raw event records: 90 days, with older partitions dropped and boundary rows cleared by scheduled maintenance.
- Aggregate daily counters: 24 months. These contain counts only: no IP, no player ID, no session ID.
- Reported-player records: 13 months.
- Login attempt log: 90 days.
Your choices
A developer may export or delete their own project data from the dashboard. A player may request deletion of their reported player record from a developer, or directly from vodka. Operators may suspend or remove accounts and scripts; destructive actions are recorded in an administrative audit log.
Lawful basis
Legitimate interests: operating a licence service that secures a developer's work. The measures above (truncation, daily-rotating hashes, country-only geolocation, labelled self-reported identity) are what keep that proportionate. Where consent is the applicable basis for browser analytics on this site, it is asked for and can be withdrawn.
Contact
Privacy requests and abuse reports: report content or email the address on the landing page.