Privacy policy
The formal version of the privacy promise: who is responsible for what, on what basis, for how long, and what you can ask for.
Last changed 9 November 2026
In short
- For members who verify, the server's owner decides and Anchor processes for them; for owners and this website, we are responsible.
- Discord is asked only who you are and for permission to add you to a server: never your email, messages or server list.
- Your IP address is not stored: only its country, and a one-way hash for catching alt accounts that is deleted after 30 days. Everything that identifies you is encrypted under a key for that one server.
- Verifying lets that server add you back to itself if it is restored - never to anyone else, and your membership is never sold.
- A server's checks can refuse a verification on their own; the owner can change the check or give you the role by hand.
- Revoke at /me at any time, and your record for that server is deleted on the spot.
A summary to help you find your way. The full text below is what applies.
Who we are
Anchor is a service of CARTIQO, CVR 46925351, Ottosgade 22, 6000 Kolding, Denmark, Denmark. Write to [email protected].
We have two roles. For owner accounts (people who run a server on Anchor) and for this website, we are the controller. For verified members, the owner of the server you verified in is the controller, and we process your data on their behalf under a data processing agreement (the DPA).
Verified members
When you verify in a server that uses Anchor, the server keeps:
- your Discord user ID, and when you verified;
- your username and avatar, and a Discord login token allowing the server to add you back to itself if it is restored - all encrypted;
- a keyed one-way hash of your IP address, for matching alternative accounts, deleted after 30 days. The IP address itself is read once when you verify and never stored;
- the country and type of network the IP address belongs to, and your browser, operating system and device type.
No device fingerprint is made: nothing is read from your browser beyond what every request carries.
Discord is asked for identify and guilds.join only: not your email, your messages or your server list. The country comes from Cloudflare, which already carries the request, or else from MaxMind's GeoLite data; the network type and network owner come from GeoLite. Anchor looks GeoLite up on its own server: no IP address is sent to MaxMind. This product includes GeoLite Data created by MaxMind, available from https://www.maxmind.com. The server owner uses this to verify you, to keep out banned and alternative accounts, and to add you back if their server is lost and restored - only into servers they have linked to the same Anchor account. Your membership is never sold or handed to anyone else. Their legal basis is set out in their own server rules; the verify page tells you what is collected before you start.
The record is kept until you revoke it at /me, you remove Anchor's access in Discord, or the owner removes the server, which deletes it after 7 days. The verification log keeps what the owner's logging level allows for up to 12 months; revoking anonymises your entries in it.
Owners
For an owner account we keep your name, email and avatar from the login you use, which logins are linked, the login provider's tokens (encrypted), which CARTIQO account you log in with and its login token (encrypted), your bot's credentials (encrypted), your servers and their settings, and a log of what you do in the dashboard. We process this to provide the service you signed up for (article 6(1)(b) GDPR). If you pay, CARTIQO and Stripe handle the payment for Anchor's plans; Anchor asks CARTIQO only which plan a server has. For an older Anchor plan we keep your plan and Stripe customer ID, and Stripe keeps the invoices for as long as Danish bookkeeping law requires (article 6(1)(c)).
Deleting your account under Account stops everything at once and deletes your account and everything in it after 7 days. Your CARTIQO account stays. Deleting the CARTIQO account your Anchor account is linked to deletes your Anchor account too: nothing changes during CARTIQO's 14 days to undo, and when those end CARTIQO tells us and your account goes at once, with your bot, servers, their members' records and backups. CARTIQO sends us only its account ID for that.
When you start the free trial, we note that your Discord account has had it (the one linked to your owner account or to your CARTIQO account): a keyed one-way hash of its Discord ID (never the ID itself, and it can't be turned back without a key the database doesn't hold) and the day. It stays after your account is deleted, because its only use is to stop the same Discord account starting another trial on a new Anchor account (our legitimate interest, article 6(1)(f)), and it is deleted after 2 years.
A server linked to the CARTIQO Bot
A server's owner can link it to the CARTIQO Bot, which is also run by CARTIQO. While it's linked, only IDs and event metadata go between the two: Discord user, role, channel and server IDs, names, the reason and source of a blacklist entry, counts and times. Your IP address, its hash, your email and the encrypted fields above never go to the bot.
- From Anchor to the bot: that you verified, were blocked or look like an alt, so the bot can give its roles and log it; blacklist, backup, restore and member pull events.
- From the bot to Anchor: bans in the server (and the bot's kick cases, if the owner chose), which go on the server's blacklist; and, when you join, your account's age, whether the server was in a raid lockdown, whether you were caught by its honeypot and whether you're on CARTIQO's shared scammer list. Those join signals count toward the server's checks and are deleted after 24 hours.
Unlinking stops all of it, on both sides.
Why the data may be used
Each use rests on a legal basis in article 6 GDPR:
| Use | Legal basis |
|---|---|
| Verifying members, the checks the owner turns on, and adding them back | The server owner's, as controller: normally their legitimate interest in protecting their community (6(1)(f)), as set out in their server rules |
| Owner accounts and the dashboard | Providing the service you signed up for (6(1)(b)) |
| Payments and invoices | The contract (6(1)(b)), and Danish bookkeeping law (6(1)(c)) |
| Application logs and abuse protection | Our legitimate interest in a service that is secure and works (6(1)(f)) |
How long, at a glance
When a period ends, the data is deleted, not archived.
| What | Kept for |
|---|---|
| Your IP address | Not stored: read once, for the country and the hash |
| The hash of your IP address | 30 days |
| A member's record in a server | Until you revoke, remove Anchor's access in Discord, or the owner removes the server (then 7 days) |
| The verification log | Up to 12 months, as the owner's logging level allows |
| An owner account | 7 days after you delete it, or at once when the linked CARTIQO account is deleted |
| Application logs | No IP addresses or tokens. Rotated by size: at most 5 files of 10 MB per service on the server, the oldest overwritten first |
| Encrypted database backups | Age out within 14 days |
| Invoices (kept by Stripe) | As long as Danish bookkeeping law requires |
Decisions made automatically
When you verify, the checks the server's owner switched on run by themselves: the captcha, whether Discord marks the account as a spammer, a profile picture or two-factor sign-in if the owner asks for them, the owner's blacklist and Discord bans, blocked networks, VPNs, proxies and Tor, mobile networks if the owner blocks them, account age, and whether the account looks like a second account of someone already verified or blacklisted.
If one of them fails, the verification is refused and the page tells you which check it was. That only means you can't verify in that one server for now: it doesn't touch your Discord account or other servers. You have the right not to be held to a decision made only by a machine: ask the server's owner, who sees in the verification log which check stopped you, and can change or turn off that check, or give you the verified role in Discord by hand.
Visitors to this website
We set only the cookies the site needs to work: a sign-in session, a short-lived, encrypted cookie that carries a verification across the trip to Discord, and, if you pick a language on the verify page or /me, one that remembers it. No advertising or tracking cookies.
To stop one address hammering the site, starting a verification, signing in at /me and failed calls from a linked bot are counted per address for a short window: a keyed one-way hash of the IP address (never the address itself) is kept in Anchor's cache (Redis) for 1 minute, or 5 minutes for the bot calls, then dropped. The basis is our legitimate interest in keeping the service available (article 6(1)(f) GDPR).
Cookies
| Cookie | What it is for |
|---|---|
| anchor.session_token | Keeps an owner signed in to the dashboard. Up to 14 days. |
| anchor_hub_state | Checks that a CARTIQO login came back to the browser that started it. 10 minutes. |
| anchor_hub_pending | Holds a CARTIQO login (encrypted) while you link it to an Anchor account. 30 minutes. |
| anchor_member | Keeps a member signed in at /me. 1 hour. |
| anchor_verify | Carries a verification across the trip to Discord. 10 minutes. |
| anchor_lang | The language you picked on the verify page or /me, and nothing else. 1 year. |
| anchor_me_state | Checks that a sign-in at /me came back to the page that started it. 10 minutes. |
The first four are needed for the site to work, so no banner asks about them. Your choice in the cookie banner is remembered in your browser's storage, not in a cookie.
Security
Everything that identifies a member is encrypted with AES-256-GCM under a key that belongs to that one server, itself encrypted by a master key kept outside the database. Hashes are keyed, so they can't be reversed with a table. Application logs hold no IP addresses or tokens, and are rotated by size (at most 5 files of 10 MB per service), so the oldest lines are overwritten first.
If a breach puts personal data at risk, we tell the owners affected within 48 hours, tell the Datatilsynet within 72 hours where the law asks for it, and tell the people affected directly when the risk to them is high.
Who processes data for us
Data is stored in the EU. These providers process it for us, each under a data processing agreement. Where one processes data outside the EU or EEA, it does so under the European Commission's standard contractual clauses or the EU-US Data Privacy Framework.
| Provider | What for, and where |
|---|---|
| Oracle Cloud Infrastructure (Frankfurt, Germany) | The server Anchor runs on: the website, the worker, the queue and the database (all stored data, encrypted where it identifies someone). Frankfurt, Germany (EU). |
| Cloudflare | DNS, protection in front of the server, the visitor's country (from the IP it already handles), and the captcha on verify pages (Turnstile). Global network; a US company. |
| Stripe | Payments and receipts, for owners on a paid plan (through the CARTIQO account). Ireland and the USA. |
Your rights
You can ask to see, correct, delete or receive your data, to restrict or object to its processing, and to withdraw consent you gave. Members can see and delete their own records at any time at /me; for anything else, write to us, and for member data we pass your request to the server owner and help them answer it. You can complain to the Datatilsynet, the Danish data protection authority.
Age
Owners must be at least 16. Members need to be old enough to use Discord where they live, which is at least 13; we don't knowingly keep data about anyone younger.
Changes
If this policy changes in a way that matters, owners hear about it by email first. The date at the top says when it last changed.
See also the privacy policy, the terms, the data processing agreement, refunds and the company details.