Account data
Discord OAuth identity, display name, avatar, email when provided by Discord, and authentication session data handled through Supabase.
GDPR aware
Privacy Policy
This page explains what dscrd.wtf processes, why it is processed, and how people can ask for access, correction, deletion, or export. It is written for an EU-operated private project.
Server listing data
Server names, descriptions, invite links, tags, pages, images, votes, moderation status, and public listing metadata you submit or manage.
Operational data
UploadThing upload metadata, database records, shortlink clicks, reports, audit logs, and basic technical logs needed to keep the service secure.
Billing data
Checkout and subscription state may be processed by Lemon Squeezy when paid products are enabled. dscrd.wtf should not receive full card numbers.
Purposes and lawful bases
We process data to provide accounts, public listings, server pages, uploads, voting, moderation, abuse prevention, checkout, and support. Depending on the action, the basis is contract performance, legitimate interests in operating and securing the service, consent where requested, or legal obligations.
Retention
Account and listing data stays while the account or listing is active. Moderation, audit, billing, and security records may be retained longer where needed for abuse prevention, accounting, disputes, or legal obligations.
Processors
The project uses Supabase for auth/database, Discord for OAuth and server data, UploadThing for uploads, and Lemon Squeezy for billing when enabled. These providers may process data in line with their own terms and privacy notices.
Your rights
If GDPR applies to you, you can request access, rectification, erasure, restriction, portability, objection, and withdrawal of consent where processing is based on consent.
International transfers
Some providers may process data outside the EU/EEA. Where that happens, the service relies on provider safeguards such as contractual protections and transfer mechanisms offered by those providers.
Security
We use provider-managed authentication, database permissions, upload controls, moderation tooling, and operational logs. No public website can promise perfect security, but the project is designed to keep access limited to what is needed.
Cookies and sessions
dscrd.wtf uses essential authentication/session cookies from Supabase. If analytics or marketing cookies are added later, they should be disclosed and, where required, gated behind consent.
Contact
For privacy requests, use the project owner contact published by something dev or the support channel linked from the Discord community. Include the Discord account or listing URL involved.
This policy describes how dscrd.wtf handles data for the current product. Last updated: June 17, 2026.