What we collect, why we collect it, and how to get rid of it. No dark patterns, no selling your data.
Last updated: 4 August 2026
Cordryx is built and run by one independent developer in Alabama, United States.
Questions about your data: support@cordryx.net
Requests go straight to the person who builds it — there's no ticket queue to get lost in.
In legal terms, Cordryx is the "data controller" for the information described here — meaning we're the ones who decide what gets collected and why, and we're accountable for how it's handled.
This policy covers cordryx.net and the Cordryx Discord bot.
Cordryx is an independent tool that connects to Discord through Discord's public API. It is not affiliated with, endorsed by, or sponsored by Discord Inc. "Discord" is a trademark of Discord Inc.
That matters for your privacy, not just for branding. Discord is a separate data controller running under its own Privacy Policy. Your Discord account, your messages, your servers and everything else you do inside Discord are collected and held by Discord under that policy — not this one. We can't change it, can't answer for it, and can't delete anything from it on your behalf. This policy covers only the data Cordryx itself holds, which is listed in section 2.
We use Discord's OAuth login. Discord gives us only what you approve on the consent screen:
| Data | Where it comes from |
|---|---|
| Discord user ID | Discord identify scope |
| Username and display name | Discord identify scope |
| Avatar image URL | Discord identify scope |
| List of servers you're in, and whether you can manage them | Discord guilds scope |
| Account created date, last login | Recorded by us |
| Discord access and refresh tokens | Issued by Discord when you approve the login. We store them so your session keeps working without making you sign in again |
We deliberately do not request your email address from Discord.
That list is not a summary we wrote from memory. It is checked against ERASURE_MAP in our Worker — the single declaration of every table that holds customer data, which our deletion routine runs down and our tests fail on if a new table appears in neither it nor the short list of tables holding no personal data at all. If we can delete it, it is disclosed here.
Only for features you switch on:
| Feature | What gets stored |
|---|---|
| Levels & XP | Member ID, username, avatar, XP, level, message and voice-minute counts |
| Economy | Member ID, username, balance, last daily claim |
| Moderation | Warnings: who, by whom, reason, timestamp |
| Invite tracking | Who invited whom, and invite counts |
| Birthdays | Day and month a member chooses to share — not the year |
| Tickets | Thread ID, who opened it, when, and any rating given |
| Giveaways | Prize, end time, and the IDs of people who entered |
| Polls | Member ID and which option they picked. Nobody, including staff, can see this through the bot — but we hold it, so it is listed here |
| Suggestion votes | Member ID and whether they voted up or down on each suggestion |
| Trivia | Member ID, username and win count |
| Counting | The ID of whoever posted the last number, so the same person can't count twice in a row |
| Temporary roles | Member ID, which role, and when it expires |
| AFK | Member ID, the reason a member typed into /afk, when they went AFK, and the nickname to restore afterwards. See the callout in section 3 |
| Suggestions | The text a member suggests, who posted it, and what staff decided. See the callout in section 3, which lists every feature that keeps text somebody typed — this is one of them |
| Audit trail | Moderation and configuration actions taken through Cordryx: what happened, who did it, when, and a short summary. A warning's reason text is included |
| Backups | A snapshot of your channel, category and role structure — names, types, channel topics, and role colours and permissions. No messages |
| Message builder | The buttons and menus you build, what each one does, and the ID of whoever built it |
| Builds and scheduled builds | Which layout was deployed to the server, by whom, when, and the IDs of the channels and roles it created — that last part is what makes one-click undo possible |
| Template publishing | Who last asked to sync a template to the server. One row per server, overwritten by the next request |
| Publish results | What came of that sync: for each panel, whether it went up or what stopped it — a channel that isn't there, a role that doesn't resolve, a rename Discord is still cooling down — plus how many attempts in a row have failed and since when. One row per server, replaced outright by the next publish. It names nobody: it records what happened to the server's own panels, not who pressed the button |
| Server statistics | Running counts of joins, leaves and messages for the server, for the analytics digest. Totals only — no member IDs, no message text |
| Health Check runs | One row each time a Health Check is run: the score and grade, the category scores, how many checks actually ran, when it ran, and the ID of the account that ran it. It is what draws the score-history chart. If that account is later deleted, its ID is removed from the row but the server's history stays — the chart belongs to the server, not to whoever happened to press Run. Deleting the server's data removes the rows outright |
| Other per-server state | Whichever of these you switch on: feed and alert positions (so you aren't told about the same stream or post twice), which messages a starboard has already reposted, panel state, and audit-mirror state. This row names nobody — it is here so the list is complete rather than only interesting |
Stripe processes the payment and stores your card details — we never see or hold your full card number. We keep your Stripe customer and subscription IDs, your plan, and a record of the amount and date, which we need for accounting.
If a payment is refunded or charged back we keep a record of that too: which payment it was, how much went back, and what it reversed — the plan, the commission or the marketplace sale. We need it for the same accounting reasons, and it is also what stops the same refund being processed twice. If you delete your account your ID is removed from that record and the financial details stay, exactly as they do for the payment itself.
/afk with a reason, we store that reason until they come back, so the bot can tell people why they're away.| Purpose | Lawful basis (UK/EU) |
|---|---|
| Log you in and show your servers | Performance of a contract |
| Apply your settings to your Discord server | Performance of a contract |
| Take payment and manage your plan | Performance of a contract |
| Keep records for accounting and tax | Legal obligation |
| Prevent abuse, spam and fraud | Legitimate interests |
| Improve the product using usage analytics | Legitimate interests |
We do not sell your personal data, and we don't run advertising.
As a server owner, that means you should:
Members can also contact us directly at support@cordryx.net to have their data removed from a server's records.
| Data | Kept for |
|---|---|
| Account details | Until you ask us to delete your account |
| Server settings and layouts | Until you delete them, or until you ask us to remove the server's data |
| Levels, economy, invites, birthdays, warnings, suggestions | Until deleted, or until you ask us to remove the server's data |
| Audit trail | 90 days, then rows are pruned automatically. Studio servers can change this to 30 days, 90 days, a year, or keep it indefinitely |
| Backups | Until you delete them, or until the eleventh replaces the oldest. Backups are a Pro feature — Free and Plus servers have none, so there is nothing to keep |
| Feed and alert state | 60 days |
| Payment records | As long as tax and accounting law requires — usually 6–7 years |
| Product analytics | Until you ask us to delete your account |
Wherever you live, you can ask us to:
Access and export you can now do yourself, from the dashboard, without asking us and without a paid plan — see the three exports below. For the rest, email support@cordryx.net — we'll respond within 30 days. There's no charge and you don't need a paid plan to ask.
An export that is short says so. Both complete exports name, inside the file, in a
response header and in the file's own name, every table we could not read and every table
that hit our per-table row cap. A partial file arrives labelled INCOMPLETE rather than
arriving quietly and reading like the whole of it. Live credentials — a bot token you
stored with us, an API key hash — are replaced with [withheld] in every
export, including your own, and the file says which columns those were.
If you're in the UK or EU and think we've handled your data badly, you can complain to your national data protection authority. In California, you have rights under the CCPA/CPRA including access, deletion, and the right not to be discriminated against for exercising them — we don't sell personal information, so there's nothing to opt out of.
What they run is not a hand-written list of tables typed out under a deadline. It is one routine that walks a single declared map of every table holding customer data, deletes or anonymises each one, and reports back a row count per table plus an explicit list of anything it could not reach. A table that fails is reported as failed rather than skipped quietly, and a table added to Cordryx without a deletion path fails our tests before it ships. The default is a dry run; the real erasure needs the subject's ID typed back as confirmation. If you want the numbers for your own erasure, ask and we'll send them.
To remove a single server's data: email us the server ID and we'll delete it. Removing the bot from the server doesn't do this on its own — the bot leaves and the records stay, so you have to ask.
To delete your whole account: email support@cordryx.net from an address we can tie to your account, or message us with your Discord account. We'll delete:
What we keep, and why. Payment records stay, because tax law requires them — but we overwrite your ID on them first, so the amount and the date survive without you attached. That applies to both our billing records and your marketplace purchases.
Some records name you inside somebody else's data, and stay with it. Those belong to that server's owner, and we won't rewrite their records on a third party's request — ask that server's owner instead, and they can have the whole server's data deleted. The full list, rather than a sample of it:
The one thing a server deletion can't reach. Poll votes are stored against the Discord message they were cast on, with nothing recording which server that message was in — so clearing a server leaves them. Ask for an account deletion and yours go, wherever they were cast.
Deleting a server's data doesn't remove any channel or role from Discord itself, and removing the bot doesn't delete data. They're separate — ask for whichever you want. Deletion is permanent and can't be undone.
What we do:
No system is perfectly secure. If a breach affects your data, we'll notify you and any required regulator without undue delay.
We use very few, and none for advertising:
| Name | Purpose |
|---|---|
| Session cookie | Keeps you logged in |
| Discord token cookie | Lets us read your server list on your behalf |
| Referral cookie | Set for 60 days only if you arrive through an affiliate link, so the affiliate gets credit if you sign up. It records which link you came from, nothing about you. Unlike the two above, it's set in the page and readable by scripts on our own site |
| Local storage | Remembers your last selected server, language and interface preferences |
You can clear these at any time in your browser; you'll simply be logged out.
Some browsers can send a "Do Not Track" signal. There is still no common standard for how sites should respond to it, so we don't act on it differently — but that's largely academic here, because we don't track you across other websites at all.
We don't run advertising, we don't use advertising or social media pixels, and we don't allow third parties to collect personally identifiable information about your browsing on other sites through Cordryx. The only things stored in your browser are the sign-in cookie and your interface preferences, described in section 11.
We also honour Global Privacy Control (GPC) signals where they apply. Since we don't sell or share personal information, there is nothing to opt out of.
Cordryx isn't intended for children under 13, or under the minimum age Discord requires in your country if that's higher. We don't knowingly collect data from them. If you believe a child's data is in our systems, email us and we'll delete it.
Our providers operate globally, so your data may be processed outside your country, including in the United States. Where data leaves the UK or EEA, we rely on the safeguards our providers have in place — typically Standard Contractual Clauses or an approved adequacy framework.
We'll update this policy when what we do changes. If a change materially affects you, we'll give notice in the dashboard at least 14 days beforehand. The "last updated" date always shows the current version.
Privacy questions, data requests, or anything else:
support@cordryx.net