Deletion is handled as a controller review; it does not run an automatic global deletion. This is necessary because some records are controlled by a Discord server operator, include other people's data, or must be retained for a lawful reason.
How the request is handled
- Sign in with Discord and open an erasure request.
- Choose Archivian or one Discord server as the controller for that request.
- The controller reviews a structured inventory and decides what to delete, partially erase, or retain.
- Approved actions run only against the concrete records included in that review.
- Your dashboard shows the request status and whether the completed outcome was full erasure, partial erasure, or retention.
Data that can normally be erased or disconnected
- account preferences and notification settings no longer needed;
- direct support or communication records where no retention reason applies;
- user-authored optional content where deletion does not impair another person's rights or a Customer record;
- files and message data whose configured retention has ended and which are not preserved by an active moderation workflow; and
- identifiers that can be removed from shared public templates without breaking other Customers' use.
Data that may remain
- active bans and timeouts, together with the minimum information needed to administer the sanction and prevent circumvention;
- unresolved reports while they remain active moderation tasks;
- recent moderation records used to identify related incidents and support consistent decisions;
- moderation cases, reports, appeals, strikes, audit records, and necessary incident evidence where the original decision must remain reviewable or appealable;
- records needed for security, abuse prevention, legal obligations, or establishing or defending claims;
- data involving other people where deletion would adversely affect their rights;
- minimal suppression or request records needed to remember and prove the deletion; and
- protected infrastructure backups until ordinary rotation, once that operational period is confirmed.
These are not automatic legal exemptions. The relevant controller must determine that continued processing is necessary and proportionate for the particular record. Archivian may propose a retention decision in the review interface, but the controller can override it and remains responsible for the final decision.
When data is retained, the request status provides a category-level explanation without disclosing private case evidence or information about other people. You may ask the controller to reconsider, complain to a supervisory authority, or seek a judicial remedy. Email [email protected] if you cannot sign in or need another identity-verification method.
For an Archivian-controller request, an approved erasure removes Archivian's cached Discord profile. Archivian may fetch that profile from Discord again if a feature later needs to display it. Deleting the profile at its source requires deleting the Discord account with Discord. A current voice-state record is retained while the account remains connected to a voice call and becomes eligible for deletion after the call ends.