Information Warden Collects
Warden only stores information required to provide moderation functionality:
- Server (guild) IDs and configuration you set with Warden's commands (log channels, whitelist roles, toproles, shift log channels, prefix, and mute role IDs).
- Case records: user IDs of the punished member, moderator ID, punishment type, reason, duration, timestamps, active/expired/revoked state, and Discord API results.
- User tag records: staff-authored title, private note, optional evidence URL, severity, active/removed state, and timestamps.
- Moderator shift records: shift start and end timestamps, computed duration, and action totals per shift.
- Punishment and shift audit events: issue, DM attempt result, expiration, revoke, and mismatch events.
Warden does not collect message content, IP addresses, email addresses, payment information, or biometric data.
How Data Is Used
Collected data is used exclusively to:
- Enforce and expire punishments consistently across restarts.
- Present case history, timelines, and lookups to authorized staff.
- Log moderation activity to your configured log channels.
- Support server owners with troubleshooting and data deletion requests.
Data Storage
Data is stored in a MySQL 8+ database operated by the Warden team. Sessions are forced to UTC, and connection pooling ensures consistent, correct time handling. Backups are taken on a regular schedule.
Data Security
Access to the production database is restricted to a limited set of maintainers. Credentials are stored outside the source repository and rotated when necessary. Warden isolates sensitive staff interfaces through Discord's ephemeral messages and rechecks permissions on every interaction step.
Third-Party Services
Warden integrates with the Discord API to receive events and perform moderation actions. Depending on the hosting environment, the bot may also use standard infrastructure providers for compute, database, and logging. No user data is sold or shared for advertising purposes.
Discord API Usage
Warden communicates with Discord using official APIs and gateway events, using only the intents and permissions listed in the documentation. Discord's own Privacy Policy governs Discord's handling of your data.
Cookies & Local Storage
The Warden bot does not use cookies. The Warden website uses only strictly necessary local storage — see the Cookie Policy.
User Rights
Users may request information about the personal data Warden holds about them (limited to their own Discord user ID and associated case, tag, and shift records). Requests are handled through the HQ Server.
Server Owner Rights
Server owners may request the export or full deletion of all data associated with their guild. Deletion is permanent and cannot be undone.
Data Deletion Requests
Send deletion requests from the HQ Server. Warden will verify server ownership via Discord before executing the request. See the Data Retention Policy for retention windows.
Contact
For privacy questions, contact the Warden team through the HQ Server. A dedicated privacy contact address may be added in a future revision of this policy.
Changes to This Policy
This Privacy Policy may be updated to reflect new features, hosting changes, or legal requirements. Material changes will be announced in the HQ Server.
Governing Law
This policy is provided as a general framework. Users remain subject to the laws of their local jurisdiction. Governing law for disputes will be clarified in a future revision.