Sign in with Discord and use the self-service request workflow. Each request covers either data for which Archivian is the controller or data controlled by one Discord server operator, so submit a separate request for each controller whose data you want to access.
How the request is handled
- Sign in with Discord and open a data access request.
- Choose Archivian or one Discord server as the controller for that request.
- Select the data categories relevant to your request.
- Archivian prepares requests for its own data in the workflow. A server-scoped request is sent to that server's authorized staff for review.
- Your dashboard shows the request status and provides the completed response for download.
What may be included
- Archivian account data, cached Discord profile data, and current or recent Discord user state;
- for a server request, the member profile, cached channel permissions, and voice state when it belongs to that server;
- messages, edits, deletion metadata, attachments, and message references;
- cases, case entries, reports, appeals, appeal chat, strikes, and automated-moderation records;
- staff assignments, server configuration contributions, notifications, and support records; and
- technical, security, analytics, and future billing records linked to your account where applicable.
The response may omit or restrict information that identifies other people, exposes security controls, or is subject to a legal restriction. Data controlled by a Discord server operator is reviewed and delivered by that operator through the controller-facing workflow.
Timing and identity
We will respond within the period required by applicable law and will explain any lawful extension. Your authenticated Discord session identifies the account associated with the request. We may request additional information when reasonably necessary to confirm identity, locate data, or protect another person. If you cannot sign in or need another identity-verification method, email [email protected].