Cordryx ← BACK TO SITE
Legal

Privacy Policy

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

The short version We collect your Discord username, avatar and user ID so you can log in; the list of servers you manage so you can pick one; the settings you choose; and — only if you turn those features on — activity data like XP and warnings. We don't sell your data. We can't read your private messages. You can download everything we hold about you yourself, from the dashboard, on any plan including free — and you can ask us to delete it at any time, and we will.

Contents

  1. Who runs Cordryx
  2. What we collect
  3. What we deliberately don't collect
  4. Why we collect it
  5. Data about your server members
  6. Who we share it with
  7. How long we keep it
  8. Your rights
  9. Deleting your data
  10. Security
  11. Cookies and local storage
  12. Do Not Track and cross-site tracking
  13. Children
  14. International transfers
  15. Changes
  16. Contact

01Who runs Cordryx

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 not Discord

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.

02What we collect

When you log in

We use Discord's OAuth login. Discord gives us only what you approve on the consent screen:

DataWhere it comes from
Discord user IDDiscord identify scope
Username and display nameDiscord identify scope
Avatar image URLDiscord identify scope
List of servers you're in, and whether you can manage themDiscord guilds scope
Account created date, last loginRecorded by us
Discord access and refresh tokensIssued 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.

When you use the dashboard

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.

When the bot is in your server

Only for features you switch on:

FeatureWhat gets stored
Levels & XPMember ID, username, avatar, XP, level, message and voice-minute counts
EconomyMember ID, username, balance, last daily claim
ModerationWarnings: who, by whom, reason, timestamp
Invite trackingWho invited whom, and invite counts
BirthdaysDay and month a member chooses to share — not the year
TicketsThread ID, who opened it, when, and any rating given
GiveawaysPrize, end time, and the IDs of people who entered
PollsMember 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 votesMember ID and whether they voted up or down on each suggestion
TriviaMember ID, username and win count
CountingThe ID of whoever posted the last number, so the same person can't count twice in a row
Temporary rolesMember ID, which role, and when it expires
AFKMember ID, the reason a member typed into /afk, when they went AFK, and the nickname to restore afterwards. See the callout in section 3
SuggestionsThe 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 trailModeration and configuration actions taken through Cordryx: what happened, who did it, when, and a short summary. A warning's reason text is included
BackupsA snapshot of your channel, category and role structure — names, types, channel topics, and role colours and permissions. No messages
Message builderThe buttons and menus you build, what each one does, and the ID of whoever built it
Builds and scheduled buildsWhich 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 publishingWho last asked to sync a template to the server. One row per server, overwritten by the next request
Publish resultsWhat 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 statisticsRunning counts of joins, leaves and messages for the server, for the analytics digest. Totals only — no member IDs, no message text
Health Check runsOne 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 stateWhichever 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

When you pay

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.

03What we deliberately don't collect

The exceptions, stated plainly Some features do keep text someone typed, because they'd be useless otherwise:
  • Suggestions. When a member posts in your suggestions channel, the bot removes the original message and stores the text so staff can review, approve or reject it. Our copy becomes the only copy.
  • Support tickets. If you open a ticket — on the site or by DMing the bot — we store what you write and what we reply, so the conversation survives.
  • AFK reasons. If a member runs /afk with a reason, we store that reason until they come back, so the bot can tell people why they're away.
  • Warning reasons and gift notes — both short free-text fields somebody chose to type, both kept with the record they belong to.
Nothing keeps the contents of an ordinary message. Everything above is text deliberately handed to the bot through a command or a form, never something scraped out of your channels: the bot reads normal messages to react to them and then forgets them.

04Why we collect it

PurposeLawful basis (UK/EU)
Log you in and show your serversPerformance of a contract
Apply your settings to your Discord serverPerformance of a contract
Take payment and manage your planPerformance of a contract
Keep records for accounting and taxLegal obligation
Prevent abuse, spam and fraudLegitimate interests
Improve the product using usage analyticsLegitimate interests

We do not sell your personal data, and we don't run advertising.

05Data about your server members

If you run a server, this part matters to you When you enable features like Levels, Economy or Invite tracking, Cordryx stores data about your members. For that data, you are the controller and we act as your processor — we handle it on your instructions.

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.

06Who we share it with

We use these service providers, and only share what each one needs:

ProviderWhat forWhat they get
DiscordLogin, and every bot actionWhatever's needed to perform the action you asked for
CloudflareWebsite hosting, our database, and the AI that runs the AI Builder (Workers AI)Everything stored by Cordryx, including the descriptions you type into the AI Builder
Our server hostRunning the Discord bot. This is a private server we rent and manage ourselves, not a managed platformBot runtime data
StripePaymentsPayment details, plan, amount
Twitch, YouTube and other feed sourcesLive and post alerts, if enabledThe creator names or feed URLs you configure
DeepL or Google TranslateAuto-translate, if enabledMessage text from the channels you configure

That is the whole list. We don't use an advertising network, an analytics SaaS, an error-reporting service or an email provider — product analytics are stored in our own database, and we contact you through Discord rather than by email.

We may also disclose data if legally required, or to protect the rights and safety of our users. If Cordryx is ever sold or merged, your data may transfer with it — we'll tell you before that happens.

07How long we keep it

DataKept for
Account detailsUntil you ask us to delete your account
Server settings and layoutsUntil you delete them, or until you ask us to remove the server's data
Levels, economy, invites, birthdays, warnings, suggestionsUntil deleted, or until you ask us to remove the server's data
Audit trail90 days, then rows are pruned automatically. Studio servers can change this to 30 days, 90 days, a year, or keep it indefinitely
BackupsUntil 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 state60 days
Payment recordsAs long as tax and accounting law requires — usually 6–7 years
Product analyticsUntil you ask us to delete your account
Two things we'd rather say than let you assume
  • Removing the bot doesn't delete the server's data. The bot leaves; the records stay, so nothing is lost if you add it back. If you want a server's data actually gone, ask us — see section 9.
  • Apart from the audit trail, feed state and the backup limit above, nothing expires on a timer. We'd rather tell you that than print a retention period we don't currently enforce.

08Your rights

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.

Three different exports, so you know which one you have
  • Everything we hold about you is self-service, on every plan including free. Dashboard → Settings → Your data → Download everything we hold about me. It spans your account and your activity in every server the bot is in, not one server, and it is the file we would build by hand if you emailed us for one. There is no plan check on it anywhere: getting the data we hold about you is a right, not a feature, so it is not something we are willing to sell you.
  • Everything we hold about one server is self-service on every plan too. Dashboard → your server → Data export → Download everything we hold. Same file, one server wide instead of one person wide. It needs Manage Server on that server and nothing else.
  • A curated server extract is the paid one, on Pro and above. Dashboard → your server → Data export builds a JSON file of that server's levels, economy, warnings, invite counts, birthdays, tickets and audit trail, with chosen columns and leaderboards already sorted, and you choose which of those to include. It is a reporting tool — the thing you paste into a spreadsheet. It contains less than the free complete file above, never more. What Pro buys is the shape and the picker, not the access.

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.

09Deleting your data

How this actually happens, said plainly Deletion is operator-run, not self-service. There is no "delete my account" button in the dashboard, and we'd rather tell you that than let the word "delete" imply one. You ask; a person with owner-level access runs it.

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.

10Security

What we do:

Credentials we have to keep usable, said out loud Some credentials have to come back out again, so we can't hash them the way we hash API keys. We handle the three of them differently:
  • The bot token for the Studio own-bot feature is encrypted at rest (AES-256-GCM, a fresh initialisation vector per row), because that token is total control of your bot. One exception we'd rather state than hide: a token saved before we shipped this is still sitting there in its original form, and only gets encrypted the next time that user saves it.
  • The Discord token from your login is not encrypted. It's what lets us show your server list without making you sign in again. Anyone who could read our database could read it. It expires on Discord's own schedule and you can revoke it at any time from Discord's Authorised Apps settings.
  • The signing secret for an outgoing webhook is not encrypted either. If you set one on Studio, we hold it in readable form alongside that server's settings, because we have to combine it with each payload to produce the signature your endpoint checks. It is a secret you chose and can change or clear at any time in the dashboard — treat it as shared with us, not as private to you.
Either way, treat your bot token like a password: reset it in Discord if you stop using the feature or suspect a problem.

No system is perfectly secure. If a breach affects your data, we'll notify you and any required regulator without undue delay.

11Cookies and local storage

We use very few, and none for advertising:

NamePurpose
Session cookieKeeps you logged in
Discord token cookieLets us read your server list on your behalf
Referral cookieSet 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 storageRemembers your last selected server, language and interface preferences

You can clear these at any time in your browser; you'll simply be logged out.

12Do Not Track and cross-site tracking

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.

13Children

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.

14International transfers

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.

15Changes

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.

16Contact

Privacy questions, data requests, or anything else:
support@cordryx.net

Home Terms of Service © 2026 Cordryx Not affiliated with, endorsed by, or sponsored by Discord Inc. “Discord” is a trademark of Discord Inc.