Privacy Policy | Discords.ai

1. Introduction

Discord Servers ("we", "us", "our") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service.

2. Information We Collect

We collect the following information when you use the Service:

Discord Account Data: Username, avatar, email address, and Discord user ID - collected via OAuth when you log in.
Server Listings: Server name, description, invite link, category, and other details you provide.
Usage Data: Pages visited, search queries, votes, and bump activity.
Payment Data: Billing information processed by Stripe. We do not store card details directly.
Cookies: See our Cookie Policy for details.

2b. Message Content: Support Tickets and Meeting Notes

If a Discord server you are in uses our bot's ticket system or its Meeting Notes tool, we read and store some of the messages sent there, to produce a record for that server's staff and, for a ticket, for the person who opened it.

Where message text is kept. The bot keeps the text of Discord messages in three places only: the channels and threads its own ticket system created; a channel where a server's staff have started Meeting Notes, from the bot's visible start message until the notes stop; and a message somebody reports or attaches a community note to. It does not keep general server messages, and it holds no persistent connection to Discord that would let it watch them.
Other places the bot reads messages. A few moderation tools read recent messages at the moment they are used: clearing messages with /purge reads the messages it is asked to delete, the honeypot reads who posted in its trap channel, and a moderation case can show a staff member the reported member's recent messages in a reply only that staff member can see, which is not stored and is not part of the case ticket's transcript.
Meeting Notes are announced. Meeting Notes starts only when a server's staff start it. The bot then posts a message in that channel, visible to everyone in it, saying that notes are being taken, who started them, and that messages posted there until they stop go into the notes. Nothing posted before that message or after the notes stop is kept. If that message is deleted, the notes stop at the bot's next check, which runs every five minutes.
What is stored. For a ticket or a meeting: the message text, who sent it, when, the text of any embeds in it, and each attachment's file name and link (not the file itself). For a ticket, every embed and attachment is kept in full as Discord returns it (for an attachment, its size and type too), including the bot's own opening card, which repeats the answers to the opening form and, in a moderation review the reported member was kept out of, lists up to six of the reports against them, each with the name of the member who made it. A ticket also keeps the answers to its opening form and the reason it was closed. For a meeting, also the notes people add with the Add a note button and, on paid plans, the summary.
Community moderation. When a member reports a message or attaches a community note to one, the reported message's text is stored as part of that report so staff can see what was actually said.
How long. Ticket transcripts and meeting notes are kept for 90 days on the free plan, 365 days on Silver, and indefinitely on Gold and above, counted from when the ticket closed or the meeting stopped. They are deleted automatically within a day of that period passing, along with the stored messages, notes and summaries behind them. A ticket that is never closed is kept, with its stored messages and form answers, until it is closed or its listing is deleted, because that period starts at the close; going unanswered only closes a ticket whose type sets an auto-close time, and Discord archiving its thread or somebody deleting its channel by hand does not close it. If a server moves to a plan that keeps transcripts and meeting notes for less time, its tickets and meetings keep the longer period for 30 days after we first see the change, so a late renewal or a short lapse does not delete older transcripts or meeting notes.
Where. Both are stored in our database, and a transcript file is usually saved on Vercel Blob as well, reachable by its link. For example, none is saved when no messages could be found in a ticket, or when the upload fails. Treat a transcript link as private.
Who else can see them. Besides the server's own staff in Discord, three kinds of people can open a server's tickets and meeting notes in the dashboard: the owner of its discords.ai listing; anyone added as a manager of that listing; and discords.ai administrators, for support and moderation. The owner's and managers' Discord permissions are checked once, when they list the server or claim the listing, and not again, so their access lasts after they stop moderating the server.
AI summaries of meetings. On paid plans, when a meeting stops, its messages and notes are sent to Anthropic's Claude models to write the summary. A meeting is only sent if its start message said it would be.

A server's owner and managers can delete a meeting at any time from the Meeting Notes page of the dashboard, which deletes its transcript file, its stored messages, its notes and its summary. That delete does not remove the write-up the bot has already posted in Discord, which carries the summary (its overview, decisions, action items and open questions) or, for a meeting with no summary, the notes with the name of each person who added one: it stays until somebody deletes it in Discord, though the transcript link in it stops working within about five minutes. A server's owner and managers can delete a closed ticket's transcript at any time from the Tickets page of the dashboard, which deletes the transcript file, its stored messages, the answers to its opening form and its close reason. That delete does not remove what the bot has already posted in Discord, such as the ticket's channel or thread and the close card in it (unless the box to delete those too is ticked), a copy posted to a transcript channel, and the direct message sent to the member, though the transcript link in that message and in that copy stops working within about five minutes. Deleting a server listing deletes its meetings and its tickets, and their transcript files, with it, but nothing the bot has posted in Discord: the meeting write-ups, every ticket's channel or thread with the opening and close cards in it, the copies posted to a transcript channel and the direct messages sent to members all stay, though the transcript links in them stop working.

2c. Server Member Data

Some of the bot's tools need to know who is in a server. Where they do, this is what is read and what is kept.

What is read and not kept. Our bot holds no persistent connection to Discord, so it cannot see a member arrive. Instead it asks Discord for the server's member list on a schedule, which returns a Discord user ID, username, roles and join date for each member. That list is used to work out who is new, or who is holding a role, and is then discarded. We do not store it. The only thing kept from it is a timestamp recording how far through the list we have already greeted, so nobody is welcomed twice.

This happens only on servers that have switched on a tool that needs it: welcome messages, roles on arrival, the raid honeypot, or the role tools.

What is kept. Records created by a server's own staff, or by a member's own action, are stored until that server deletes them:

Moderation records. Warnings, notes, bans, kicks, timeouts, mutes and appeals, each with the Discord user ID and username of the member, the moderator who acted, the reason given and the time. This is what lets a server's staff see what has already been done about somebody, and what lets a member appeal it.
Raid trap catches. When a member trips a honeypot trap, we record their Discord user ID and username, what the bot did and when, so the server's staff can see the evidence for an action taken automatically.
Birthdays. Only if a member sets one themselves with the birthday command, and only the day and month, never the year.
Invite tracking. Invite codes belonging to the server, and the Discord user ID and username of whoever created each one.
Server economy. A balance and activity counts against a Discord user ID, for servers running the economy tool.

What we never collect. We do not collect presence, online status, what a member is playing, or voice activity. We do not read general server messages, apart from the cases set out in section 2b. We do not build profiles of members across different servers, and we do not sell or share member data with advertisers.

Who can see it. The staff of the server the record belongs to, through that server's dashboard, and discords.ai administrators, for support and moderation. A member can see what is held about them in a server through their own profile on it.

Deleting it. A server's staff can delete the records held about a member from that server's dashboard, and removing a server's listing deletes the data tied to that listing. If you want data about you removed from a server you are no longer in, or the server will not act, contact us through the Help page and we will deal with it directly. Section 6 sets out your rights and how to exercise them.

3. How We Use Your Information

We use your information to:

Provide and improve the Service
Display your server listings to other users
Process payments and manage subscriptions
Send account-related notifications
Moderate content and enforce our Terms of Service
Analyze usage trends to improve features

4. Data Sharing

We do not sell your personal data. We may share data with:

Stripe and PayPal: For payment processing. We do not store card details directly.
Vercel and Neon: Our infrastructure providers for hosting, database and file storage.
Anthropic: Content you submit may be sent to Anthropic's Claude models for automated moderation checks, for the AI assistant if you use it, and to generate summaries and metadata for articles. On paid plans, the messages and notes from a meeting recorded with Meeting Notes are sent to write that meeting's summary. It is not used to train their models.
Discord: To read and post on your behalf in servers where our bot is installed, with the permissions that server granted it.
Upstash: Rate limiting, which sees your IP address.
Cloudflare: Bot protection on forms, which sees your IP address.
Resend: To send account and notification emails.
Law enforcement: When required by applicable law.

5. Data Retention

We retain your account data for as long as your account is active. A server listing is retained until its owner or one of its managers deletes it; rejecting or suspending a listing in moderation does not delete it. Ticket transcripts, meeting notes and the messages behind them are deleted automatically once the retention period for that server's plan has passed, as described above. You may ask us to delete your data at any time by contacting us through the Help page.

6. Your Rights

Depending on your location, you may have rights including:

Access to your personal data
Correction of inaccurate data
Deletion of your account and data
Objection to data processing
Data portability

You can download everything we hold about your account yourself, at any time, from Settings. The file lists what it contains and what it leaves out. For correction, deletion, objection, or anything the file cannot answer, contact us through the Help page.

7. Children's Privacy

Our Service is not directed at children under 13. We do not knowingly collect personal data from children under 13. If you believe we have collected such data, please contact us immediately.

8. Security

We implement industry-standard security measures to protect your data, including HTTPS encryption and secure database storage. However, no method of transmission over the internet is 100% secure.

9. Third-Party Links

Our Service contains links to Discord servers and external sites. We are not responsible for the privacy practices of those third parties.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of significant changes by updating the date at the top of this page.

11. Contact

For privacy-related questions or requests, please contact us via our Help page or Discord support server.