Legal / privacy

Privacy Policy

Last updated November 1, 2026. This policy covers the information Voltfuscator handles when you use the website, Discord bot, or API.

Code submissionsDiscord IDsAPI keys

1. Data we handle

When you use Voltfuscator, we handle the Lua or Luau code you submit and the output we generate. We also process Discord user IDs and profile details, API key data, request times, file names and sizes, status checks, IP-derived request details, and basic error logs.

Website and APICode, sign-in, and build details
Discord botUser IDs, acceptance, and usage times
SecurityRate limits and abuse-prevention logs

2. Why we use it

We use this information to run builds, apply usage limits and cooldowns, record acceptance of the Terms, sign in Discord accounts, investigate errors, protect the service, and respond to support or API requests.

3. Storage and retention

We process submitted code to create your output; we do not keep it as a long-term archive. Temporary source and output files are removed after compiler processing. The account database keeps Discord profile details, API key hashes, usage totals, and build records such as status, preset, size, duration, and source hashes—not the submitted source or output. Build activity is kept for about 30 days, tier-change audit records for about 90 days, and sign-in sessions for up to seven days. Cleanup can take longer if a backlog builds up. API keys become inactive after 30 days without use. Account records and aggregate totals remain until you ask support to remove them.

The Discord bot may also keep your user ID, when you accepted the Terms, and recent usage times for cooldowns and limits.

4. Service providers

Cloudflare provides DNS, hosting, database, routing, and security services. Discord provides sign-in, bot, and community features. Northflank hosts the compiler. Other infrastructure providers may also process information needed to run Voltfuscator. Their own terms and privacy policies apply to their services.

5. Security

We use safeguards such as HTTPS, authenticated API requests, secure session cookies, rate limits, and private storage for configuration secrets.

Keep secrets out of submitted code.

No online service can promise perfect security. Do not include passwords, tokens, or private credentials in your scripts.

6. Your choices

You can stop using the website, bot, or API at any time. To ask about access to or deletion of records tied to your Discord account or API use, contact us on Discord.

7. Contact

Send privacy questions to @justflaxo on Discord.