Skip to content

DiscoListing Privacy Policy

What information the service uses, why it is needed, who receives it and the choices available to you.

Last updated

Who this policy covers

This policy describes how the DiscoListing team handles information when you visit the directory, sign in, submit a listing, vote, report content, use integrations or buy premium. Operators of listed bots and communities have their own privacy practices. This policy does not cover their services.

Information we collect and use

Discord sign-in provides account identifiers, profile names, avatar and email where supplied. We retain OAuth tokens to verify the servers you can manage and refresh that access. Account records include preferences, session information and relevant moderation status. We do not receive your Discord password.

Listings include server or application IDs, names, descriptions, tags, images, invites, links, commands and reported counts. We also store submitted edits, reviews, votes, reports, evidence, staff decisions, API-key records, webhook configuration and delivery records where those features are used.

Requests may include IP addresses, network information, user agents and technical logs for authentication, rate limits, abuse prevention and troubleshooting. Vote protection uses a salted network hash, including an IPv6 network prefix where applicable. This does not mean every system or service provider receives only hashed IP addresses.

Optional browser reminders store a push endpoint, encryption keys and limited device information. Billing integrations store subscription and transaction references, status and payer associations. The payment provider collects the payment details required for checkout; our application does not store full payment-card numbers.

Directory bot and community activity

If the directory bot is added to a server, it measures activity such as message counts, joins, leaves, voice time and online members. The activity pipeline does not store message text or transcripts. It ignores direct messages, bots and webhooks for message activity counts.

Hourly and daily activity counts use aggregate records and approximate distinct-member counters. Temporary processing can use member and channel identifiers for spam caps, voice sessions, Discord caching and permission checks. Aggregate statistics are not a promise that no identifiers are processed anywhere in the bot.

Why we process information

We use information to authenticate users, verify management permissions, publish listings, calculate discovery statistics, deliver requested reminders and integrations, manage billing, investigate reports, prevent abuse and maintain the service.

Where data-protection law requires a legal basis, processing may be necessary to provide the service you request, meet legal obligations or pursue legitimate interests in security, moderation and reliable operation. Where consent is required, it must be obtained separately; this policy is a notice, not blanket consent to optional tracking.

Cookies and browser storage

Authentication cookies maintain sign-in and session checks. Preference cookies remember theme and palette selections. Browser storage may also support application behaviour such as reminders. Blocking cookies can prevent sign-in or preference persistence.

Cloudflare Turnstile and network protection process technical information to identify abusive traffic. Sentry error monitoring may be enabled for diagnostics; the current configuration disables user-info, cookie, header, request-body and query-parameter collection and does not enable session replay. Error messages and stack traces may still contain technical information.

Public information and service providers

Approved listing content and public statistics can appear on the directory, public API, embeds and search engines. Listing edits awaiting approval and private moderation information are not part of the public listing. Author information associated with public contributions may also be visible.

Authorised staff access information needed for support, review and safety. Infrastructure and service providers may process information to operate the service, including Discord for authentication and API access, Cloudflare for protection, Sentry when diagnostics are enabled, Polar when payments are enabled and your browser push service for requested reminders.

We may disclose relevant information when required by law or necessary to address credible safety threats and abuse. We do not sell personal information. Providers may process information in other countries under their own applicable privacy notices and safeguards.

Retention and deletion

Account and listing records are retained while needed to operate the service; they do not all have automatic deletion schedules. Sessions normally expire after 30 days. Activity records have a 120-day automatic expiry and score snapshots a 90-day expiry. Webhook delivery logs expire after 30 days and notification records after 180 days. Database expiry is asynchronous and may not occur at the exact scheduled instant.

Routine audit records are generally retained for one year. Dismissed reports normally expire after 90 days and upheld reports after two years. Open cases, child-safety reports and certain ban, deletion, staff, settings and payment audit records have no automatic expiry. Retention may be extended for disputes, abuse prevention or legal obligations. Provider retention and backups can differ.

Removing a listing, revoking Discord authorisation or signing out does not automatically erase all account, moderation, billing or backup records. Contact official support to request access, correction or deletion; we assess the request and any applicable retention obligations.

Your choices and privacy rights

You can edit account preferences, disable browser reminders, revoke application access in Discord, remove the directory bot from a server you manage and control cookies in your browser. Public listing changes may require staff approval. Deleting a browser push permission also stops that browser from displaying reminders.

Depending on where you live, you may have rights to access, correct, delete or receive your information, restrict or object to processing, withdraw consent and complain to a relevant data-protection authority. Use official support to make a request. We may verify identity before disclosing information. Do not post passwords, OAuth tokens, government IDs or sensitive evidence in a public support channel.

Age requirements and policy updates

The service is not intended for people below the age permitted by Discord or applicable law. Adult listings require users to be at least 18. Contact staff if you believe a child has supplied information contrary to these requirements. We will assess appropriate restrictions and deletion obligations.

We may update this notice as the service changes. The update date appears above. Questions and privacy requests should go through the official support contact shown below.

Provider privacy notices

Contact and support

Use official support for questions, privacy requests, billing issues and appeals. Ask staff for a private conversation before sharing sensitive information; never post credentials or identity documents in a public channel.

Build a community people come back to

Practical guides for finding your people and growing a welcoming server.

All community guides
  • 3 min read · Community guide

    Promote Your Discord Server Without Spam or Fake Joins

    Promote your Discord server with a clear listing, relevant communities and useful events. Track useful results and avoid spam, fake members and invite quotas.

  • 3 min read · Community guide

    Revive a Quiet Discord Server With a Two-Week Reset

    Revive a quiet Discord server with a realistic reset: reduce empty channels, reconnect with members and test one repeatable activity without mass-ping pressure.