This Privacy Policy explains what information the Admit Discord bot ("Admit," "we," "us,"
"our") collects when it is added to a Discord server or used by a member of one, and how that
information is stored, used, and shared. It should be read together with our
Terms of Service.
1. Introduction
We built Admit to do its job — moderation and server utility — without collecting more than
that job requires. This policy is written to be specific about what is and is not stored, so
server owners can make an informed decision before adding the bot.
2. Information we collect
We collect information in three ways: automatically through Discord's API, from configuration you provide, and from your own interactions with commands.
2.1 Information received from Discord
- Identifiers: server (guild) ID, channel IDs, user IDs, and role IDs needed to route commands and apply permissions.
- Message content, limited to command use: the text of slash commands and their parameters. Admit does not read, log, or store the content of ordinary messages outside of the moderation filters described below.
- Moderation-relevant content: when a message triggers a configured filter (for example, a spam or scam-link filter), the flagged message content and its author are logged to your server's designated log channel so moderators can review the action.
- Server metadata: server name, member count, and icon, used to display your server correctly in any dashboard or support context.
2.2 Information you provide directly
- Configuration settings — such as filter thresholds, log channel selections, custom command responses, and assigned staff roles.
- Messages sent to us directly for support, such as bug reports or feature requests.
2.3 Information we do not collect
- We do not collect your Discord password or authentication credentials — authentication is handled entirely by Discord's own OAuth2 system.
- We do not access direct messages between users, except messages sent directly to the bot itself (for example, as part of a support request).
- We do not sell personal information to data brokers or advertisers.
3. How we use information
We use the information described above only to:
- Execute commands and apply the moderation or utility actions you configure;
- Maintain moderation case history (warnings, mutes, bans) so servers have a consistent record;
- Diagnose and fix technical issues, including error logs that may temporarily include relevant identifiers;
- Detect abuse of the Service itself, such as attempts to exploit or overload it;
- Respond to support requests you send us directly.
We do not use collected data to build advertising profiles, and we do not use message content for any purpose beyond the moderation and utility functions you've enabled.
4. Data storage & retention
- Configuration data is retained for as long as the Service remains added to your server, and is deleted within [30 days] of removal.
- Moderation case logs (warnings, mutes, bans and their reasons) are retained for [90 days / 1 year — set your own window] to support appeals and pattern detection, after which they are automatically purged unless a server administrator exports them first.
- Command usage data processed to execute a command is not stored longer than necessary to complete that action, unless it becomes part of a moderation case log as described above.
- Data is stored using [hosting provider / database, e.g. a managed PostgreSQL instance on [Provider]], located in [region].
5. How information is shared
We do not sell or rent your information. We share it only in the following circumstances:
- Service providers: infrastructure and hosting providers that store or process data strictly on our behalf, under confidentiality obligations, and only to the extent needed to run the Service.
- Discord: all interaction with the Service necessarily passes through Discord's platform and is subject to
Discord's own Privacy Policy.
- Legal requirements: where we are required to disclose information to comply with a valid legal process, protect the rights or safety of our users, or investigate violations of our
Terms of Service.
- Business transfers: if the Service is transferred as part of a merger, acquisition, or sale of assets, data may transfer as part of that transaction, subject to this policy or a comparable one.
6. Security
We apply reasonable technical and organizational measures to protect stored data, including
access controls limiting who can query production data and encryption in transit between the
Service and its infrastructure. No method of storage or transmission is completely secure, and
we cannot guarantee absolute security, but we work to keep the amount of data we hold, and the
time we hold it, to what the Service actually needs.
7. Your choices & rights
Depending on your location, you may have rights to access, correct, or delete personal information we hold about you. In all cases:
- Server administrators can delete stored configuration and case-log data for their server at any time by using /data delete or by removing the Service from the server, which begins the deletion window described in Section 4.
- Individual members can request a copy of, or deletion of, the moderation-relevant data associated with their user ID by contacting us using the details in Section 11. We may need to verify the request comes from the relevant Discord account before acting on it.
- Where applicable law (such as the GDPR or CCPA) grants additional rights — including the right to restrict processing, object to processing, or lodge a complaint with a supervisory authority — we will honor those rights on request, subject to identity verification.
8. Children's privacy
The Service is intended for use in accordance with Discord's own minimum age requirements. We
do not knowingly collect personal information from anyone below the age required by Discord's
Terms of Service. If we become aware that we have collected such information, we will delete
it promptly.
9. International data transfers
Because Discord and our infrastructure providers operate globally, information may be
processed or stored in a country other than the one you reside in, including
[country/region], which may have different data protection laws than your
own. Where required, we rely on appropriate safeguards, such as standard contractual clauses,
to protect information transferred internationally.
10. Changes to this policy
We may update this Privacy Policy periodically to reflect changes to the Service or applicable
law. Material changes will be reflected in the "Last updated" date at the top of this page, and
significant changes will be announced through our support server where practical. Continued use
of the Service after an update takes effect constitutes acceptance of the revised policy.
For privacy questions, data access requests, or deletion requests, contact us at
[[email protected]] or through our
support server. We aim to respond to verified requests
within [30 days].
This document is a template starting point and does not constitute legal advice. Fill in every
bracketed placeholder with accurate details about what your bot actually does and stores, and
have it reviewed by a qualified professional — especially if your bot has users in the EU
(GDPR), California (CCPA/CPRA), or other regions with specific data-protection requirements.