Overview
Privacy policy overview
As a real-time communication and community platform, Discord may process account, device, interaction, payment, and safety-related information. The most important areas are what information is involved, why it is used, when it may be shared, how long it may be retained, and how users can make privacy-related requests.
Key areas
Account safety, billing records, message privacy, data access, deletion requests, and appeal handling often follow different review paths.
Collected Data
1. Data categories handled by Discord
Different information categories may be involved depending on the feature used, the device signed in, the server or channel activity, the subscription status, or the safety review context.
-
Account information:
username, email, phone number, login credentials, and verification-related information.
-
Usage information:
servers joined, channel activity, direct messages, interaction behavior, and feature usage records.
-
Device and technical information:
device type, operating system, network context, logs, error reports, and client version.
-
Payment-related information:
subscription state, transaction records, billing identifiers, and verification results.
-
Safety and compliance information:
risk-control records, reporting signals, moderation context, appeal materials, and account protection data.
Usage
2. How information may be used
|
Data type
|
Main purpose
|
Common scenario
|
|
Account information
|
Identity, login verification, recovery
|
Registration, sign-in, password reset
|
|
Device and logs
|
Stability, anomaly detection, compatibility
|
Crash review, login protection
|
|
Payment records
|
Subscriptions, order validation, refunds
|
Nitro, gifts, billing support
|
|
Safety data
|
Abuse prevention, appeals, compliance
|
Reports, enforcement reviews, risk detection
|
Sharing
3. Data sharing and disclosure
Data sharing may occur when it is needed for payment processing, infrastructure operations, service security, abuse prevention, support handling, or legal compliance.
-
Payment processors and billing partners for subscriptions, gifts, and refunds
-
Infrastructure, security, and abuse-prevention partners that support service reliability
-
Legal or regulatory disclosures required by valid process or applicable law
Note
Regional law can affect disclosure, request handling, retention, and available user rights. Formal privacy requests should follow the applicable policy and support channels.
Security
4. Security, retention, and account protection
Security controls may include authentication safeguards, access controls, audit records, risk monitoring, suspicious login detection, payment protection, and internal review boundaries that reduce misuse or unauthorized access.
Authentication
Access control
Risk monitoring
Audit logging
Suspicious login detection
Payment security handling
Retention periods can depend on service operation, legal duties, dispute handling, safety investigations, payment records, support history, and account status.
User Rights
5. User rights and privacy requests
Depending on applicable law and policy, users may be able to request access, correction, deletion, processing limits, data explanations, or appeal review related to personal information.
-
Identify the request type, such as account data, payment records, report history, safety review, or deletion.
-
Prepare verification details needed to confirm account ownership or request eligibility.
-
Submit the request through the relevant support or privacy pathway.
-
Provide follow-up information if the review team needs more context.
Contact
6. Privacy contact and support paths
Privacy, account, payment, appeal, and data requests may require different support paths. Account access and billing issues often start in the Help Center, while company entity details belong on the Company Information page.
Support path
Start with the Help Center for account, billing, and product issues. Use the Company Information page when corporate entity, address, or legal-reference details are needed.
