Privacy Policy & Data Charter
Voxen is engineered around a core architectural principle: Data Minimization. We collect and store only the minimal technical identifiers strictly necessary to operate antinuke shields, enforce AutoMod rules, and synchronize your web dashboard.
Data Minimization Guarantee
We firmly believe that user privacy should be built into code, not just legal promises:
- No Selling of Data: We never monetize, sell, or license any Discord telemetry, user IDs, or server configurations to advertising networks or data brokers.
- Purpose Limitation: Collected data is utilized strictly to provide bot services explicitly requested by server owners.
What Data Is Stored in Databases
The following Discord identifiers and operational parameters are maintained in encrypted local databases:
| Category | Stored Fields | Purpose |
|---|---|---|
| Server Config | guild_id, prefix, log_channel_id, welcome_channel_id |
Route bot commands and audit dispatches to designated channels. |
| Antinuke & Whitelist | whitelisted_user_ids, active_sentinels, punishment_mode |
Determine whether administrator actions require emergency mitigation. |
| Moderation Logs | case_id, target_user_id, moderator_id, action, reason, timestamp |
Sequential disciplinary record accessible to server staff via /warn list. |
| Virtual Economy | user_id, wallet_balance, bank_balance, xp_level |
Gamified community progression and server level tracking. |
| Voice Sentinels | channel_id, locked_state, banned_user_ids, continuous_drag_map |
Enforce voice channel access shields and continuous drag parameters. |
Ephemeral In-Memory Processing
Certain advanced features require real-time content evaluation. To preserve privacy, these operations take place entirely in volatile system memory (RAM) and are discarded within milliseconds:
- Heuristic AutoMod: Messages are matched against active server filters (phishing URLs, velocity floods, custom regex). Once processed, the message content string is released from memory immediately.
- Audio DSP & Lavalink: Audio streams are decoded and forwarded directly to Discord Voice Gateway channels. Audio packets are never recorded, archived, or copied to persistent media.
- Audit Log Telemetry: Discord Audit Log events are monitored in real time. Events not triggering security thresholds are discarded without retention.
Security Architecture & Authentication
We enforce stringent technical security controls across our platform:
- Encrypted Transport: All dashboard traffic and API requests are enforced over TLS 1.3 encryption with strict HSTS headers.
- OAuth2 Single-Sign-On: We utilize Discord's official OAuth2 identification flow. Voxen never requests, accesses, or stores your Discord password.
- Cryptographic Session Tokens: Dashboard session cookies are signed with HMAC-SHA256 tokens and protected with
HttpOnly,SameSite=Lax, and anti-tamper verification.
Right to Erasure & Data Deletion
In full compliance with GDPR Article 17 (Right to Erasure) and CCPA regulations, server owners and community members have total control over their data:
- Automated Purge on Bot Kick: When Voxen is removed from a Discord server, all guild-specific settings and active sentinel configurations are automatically flagged for deletion.
- Command-Based Purge: Server administrators can execute
/antinuke resetor/server-backup clearat any time to instantly wipe configurations. - Administrative Reset: Server administrators can manage and purge configuration logs directly via admin commands or through our support team.
- Individual User Requests: Individual users may submit a data deletion request through our Support Server for complete removal of economy records.
GDPR & International Compliance
For residents of the European Economic Area (EEA), United Kingdom, and California:
- Lawful Basis for Processing: We process data under the basis of Legitimate Interests (preventing server raids and maintaining community safety) and Performance of a Contract (delivering bot features requested by users).
- Data Portability: Guild administrators can export server backup configurations using
/backup create.