This document is written to be usable, not decorative. Mandatory rights under applicable law always take priority where they provide stronger protection.
1. How to read this schedule
These are standard maximum retention targets, not minimum periods. We may delete or anonymize information earlier when no longer needed. We may retain a record longer for an active investigation, legal obligation, dispute, security incident, child-safety matter, fraud prevention, or documented legal hold.
Discord messages and records held by other platforms are also subject to their controls, backups, and retention practices. Removing a bot database record does not necessarily remove a message stored by Discord or a copy already supplied to a ticket participant.
2. Standard retention periods
| Record | Standard period | Disposition |
|---|---|---|
| Website operational and security logs | Up to 30 days | Delete or aggregate unless needed for an incident |
| General contact, business, press, and collaboration inquiries | 24 months after last substantive contact | Delete or retain a minimal relationship record |
| Discord role subscriptions | Until removed, the member leaves, or deletion is requested | Remove from the bot database |
| Member join/leave metrics | 12 months | Delete or aggregate without member identifiers |
| Open support tickets | While active | Move to the closed-ticket schedule after closure |
| Closed ticket metadata and transcripts | 24 months after closure | Review for deletion or anonymization; platform copies may remain |
| Bug reports and feature requests | 36 months after resolution or release | Delete personal fields or preserve an anonymized engineering record |
| Warnings | Active period plus 12 months after expiry | Delete or anonymize unless connected to a later case |
| Moderation cases and ban appeals | 36 months after closure | Delete or anonymize; serious safety records may be held longer |
| Tester applications, agreements, access, and build audit records | Term of access plus 3 years | Delete or anonymize; remove live access promptly |
| Event RSVPs | 90 days after the event | Delete attendance linkage or retain aggregate counts |
| Staff availability status | 90 days | Delete operational status entries |
| Security and vulnerability reports | 5 years after resolution | Delete unnecessary personal data; retain the security record |
| Transaction, tax, and accounting records | 7 years or legally required period | Secure deletion after obligations expire |
| Encrypted rolling backups | 30 daily recovery copies | Automatically replace the oldest backup |
3. Deletion and anonymization
Deletion removes a record from active systems where reasonably possible. Anonymization removes or irreversibly separates identifiers so remaining information is not reasonably linkable to a person. We may preserve anonymized counts, bug patterns, release history, and security lessons indefinitely.
Eligible community data may be removed with /delete-mydata. Records required for safety, moderation accountability, legal compliance, payment disputes, or security may be restricted instead of immediately deleted. We will explain the category retained when permitted.
4. Backups and restoration
The bot creates encrypted daily database backups with a rolling 30-copy window. A record deleted from the live database may remain in encrypted backups until those backups expire. If a backup is restored, deletion requests and retention checks should be re-applied before ordinary use resumes.
5. Ownership and review
The UnhingedForge owner is responsible for retention oversight. Staff should use approved channels, avoid unnecessary exports, document legal holds, and review this schedule at least annually and whenever a new product, payment flow, analytics tool, or data category is introduced.
Questions or requests
Contact the forge.
Use a private channel for personal, moderation, payment, or security information. Never send passwords, tokens, private keys, full card numbers, or authentication codes.