DonutKing uses DonutSMP in-game money only. Nothing is sold, and nothing here can be exchanged for real money. This notice lists what the site keeps about you to sign you in, run your balance and your rounds and keep the community safe, and why. Your data is not sold or shared for advertising. The rules you accept by signing in are on the rules page.
1. Who runs DonutKing
DonutKing is run by DonutKing.gg, which decides what is kept and why. Questions about this notice, or a request about your data: support at donutking.gg or the contact form.
2. What the site keeps, and why
| What | Why | How long |
|---|---|---|
| Discord account: id, username and display name | To sign you in and recognise your account. Discord also sends your avatar at sign-in; it is not stored. An account created with Sign in with Minecraft has none of this until you connect Discord (offered right after that sign-in, or later on your profile). | While your account exists. |
| The Discord "join servers for you" permission | Each Discord sign-in (and connecting Discord) adds you to the DonutKing Discord server if you are not in it, and the permission lets DonutKing add you back, for example after the server was raided or moved. The access and refresh tokens are kept sealed: encrypted so that the website itself cannot read them back, only the DonutKing Discord bot can. With them we keep when you gave and withdrew the permission and the result of the last add. They are used for that add and for revoking them, never to read your servers or messages. | Until you turn it off on your profile or your account is banned. Then it is revoked at Discord and the sealed copy is deleted. Backups keep older copies (section 6). |
| Minecraft account: UUID and name, and how it was verified | Deposits are credited from, and withdrawals paid to, this account only. Once it is linked, your Minecraft name is your name on the site. | While your account exists. |
| Your public username (only if you pick one) | The name other players see instead of your handle or masked name (section 3), and when you last changed it — for the once-a-week limit. Each pick, change or removal, and a staff removal with its reason, is written to the audit log, so staff can act on a report about a name. | Until you remove it or staff do; the audit entries while your account exists. |
| Sign in with Minecraft: each attempt | The Minecraft name you typed, the amount and the deposit account the page showed you, when it expires, a fingerprint (a one-way hash) of the random code your browser keeps in a cookie, and how the attempt ended — signed in, expired or why it was refused — with the in-game payment that completed it. An account created this way stores only your Minecraft UUID and name (above), no Discord, no e-mail and no password. It proves the sign-in, keeps a payment from signing in twice, and lets staff answer "why did my sign-in not work". | While your account exists (an attempt that never signed anyone in: like the payment records it belongs to). |
| Money and game history | Deposits and withdrawals with their in-game payment records, every round (game, entry, result, payout and its fairness inputs), the ledger, Daily Drop tickets and results, XP, cosmetics, and your limits and breaks. This is your balance and its history, what lets anyone verify a result, and what the site's nightly totals are checked against. | While your account exists; after it is closed, they are kept for 12 months, then deleted. |
| Predictions | Your pick on each event (changeable until it closes), the points it earned, and your points total with your correct and resolved picks — to score the events, rank the points leaderboard and award titles. | While your account exists. |
| Skill Arena | Your registrations (removed if you unregister while the event is open), the placements staff verify with your parkour time where there is one, the points they earned and your totals (events and wins) — to run the events, publish their results and award titles. | While your account exists. |
| Site chat | Your messages, and any mute or report about them, for the chat and its moderation. | While your account exists. A message staff remove is hidden from the chat but stays in the moderation record. |
| Messages through the contact form | The topic, your message and the Discord handle you leave (optional), to answer you. | Kept as a support record after the case is closed. |
| Sign-in sessions | A random token in a cookie keeps you signed in. The database stores only a hash of it, when it started and when it was last used. | A sign-in stops working when you sign out, after 14 days without a visit, and after 60 days at most. The session record itself stays while your account exists (it no longer signs anyone in). |
| Who is online | While a page of the site is open, it checks in every few seconds (every 30 seconds in a background tab) for the chat's "N online" count. The site notes your account — or, signed out, the random code in the dk_presence cookie (section 5) — with the time of the last check-in. Crawlers, link previews and scripts are not counted. | In memory only (the site's in-memory cache), never in the database, and the site never logs it: forgotten 2 minutes after the last check-in. A visitor code is dropped when that browser signs in, the account when you sign out. |
| Audit log | Every staff action on your account, and your own changes to limits and breaks, with the time and who made them. | While the site runs. |
| IP address | While you are signed out, requests are rate-limited per IP address (for IPv6, per /64 network) to keep out spam and overload. Signed in, the limit is per account. | The rate limit keeps it in memory only, for the length of the limit window (seconds to minutes). Two anti-abuse checks store a one-way hash of your network (the address block, never the address itself) with the action: a rain join (one join per network per rain) and a redeem-code attempt. The web server's request logs also contain IP addresses: they are kept for up to 30 days. |
| Unusual-activity signals | To decide when to ask for a Turnstile check (section 4), the site counts a few signals per account (signed out: per network) — rate limits hit, codes that failed, a sign-in session that moved to another network, a client that announces itself as a script — and remembers the rough network (country and provider-sized address block) a sign-in session was last used from. | In memory only (the server's memory or its in-memory cache), never in the database: the count for at most an hour, the session's last network for at most 30 days. |
| Server-tag reward | When you claim it, the DonutKing Discord bot asks Discord whether your linked Discord account is a member of the DonutKing server and shows its server tag. We keep each claim: your account, its Discord and Minecraft accounts, the answer (the tag text, or why it did not count) and the amount paid, to pay it once a day and to check claims. | While your account exists. |
3. What other players see
Other players never see your name in full: everywhere public — live rounds, leaderboards, races, big wins, chat and our Discord posts — you are shown by the public username you pick on your profile (3–16 letters, numbers or _, changeable once a week; never your Minecraft or Discord name or anyone else's here — staff remove a username that is offensive or pretends to be someone). Until you pick one you are shown as a handle like Anon-3F9A2C (anonymous mode, on for every account by default); turn anonymous mode off and your name is shown masked instead, only its first and last character with stars in between (like N********D). You see your own name in full; staff see it on the staff panel only. With anonymous mode off, your Minecraft head is shown next to the masked name, served by DonutKing itself: the page never carries your Minecraft UUID or your account id. In anonymous mode no head is shown.
The lobby's live feed and ticker show settled rounds under that public name (your username, else the handle or the masked name; the head only with anonymous mode off), the game, the entry, the multiplier and the payout. The leaderboards and races rank players by it, and chat messages are visible to everyone on the site under it (what you type is your own text: a name you write in a message is shown as you wrote it). There is no setting to hide your rounds from the feed or the leaderboard today.
Predictions: the points leaderboard shows the same public name (your username, handle, or masked name and head), title and points, and carries your number of correct and resolved picks. Other players see how many picked each option, never which option you picked. Skill Arena: a verified event's results list each player's public name (username, handle, or masked name and head), placement, parkour time (where there is one) and points; an open event shows only how many players registered.
4. Who else sees your data
- Discord handles the Discord sign-in and the add to our Discord server. Discord's own privacy policy covers your Discord account. The DonutKing Discord bot also posts staff alerts into a private staff channel of that server — for example a withdrawal held for review, an unusual win or a payment that needs a decision. Those messages carry the player's name, balance and amounts, so Discord stores them, and only staff can read the channel (the bot refuses to post into one that everyone can see).
- Cloudflare runs in front of the site: every request passes through it (it protects the site against attacks and abusive traffic), so it sees your IP address and the pages you open. When the site has Cloudflare Turnstile turned on, it asks for a quick check with Cloudflare before a sign-in, redeeming a code and claiming a reward (rakeback, referral earnings, the server-tag reward), and before a withdrawal or a deposit request when an account's recent activity looks unusual. Your browser then completes a Turnstile check with Cloudflare and the site sends Cloudflare your IP address to verify it.
- mc-heads.net serves the Minecraft heads you see on the site. Other players' heads are fetched by DonutKing's server and served from our own address, so your browser never asks mc-heads.net for them. Only your own head on your own pages (the menu, your profile) loads in your browser from mc-heads.net by your Minecraft UUID, so that service sees your IP address then.
- Mojang: the site looks Minecraft names up in Mojang's public profile service (from our servers, not your browser) — the name you type to sign in with Minecraft, and the name of a player who pays one of the site's accounts — to find the Minecraft account it belongs to.
- DonutSMP: deposits and withdrawals — and the payment that signs you in with Minecraft — are ordinary in-game payments between your Minecraft account and the site's accounts.
- Hosting: the site and its database run with a VPS provider in the EU.
The site has no ads, no analytics and no tracking cookies.
6. Backups
The database is backed up every day, encrypted, on the server and in a second location. 14 daily and 8 weekly copies are kept, so a backup can hold anything above, including a Discord permission you have since turned off (still sealed), for up to about 8 weeks. If a backup is ever restored, permissions turned off after it was taken are revoked again.
7. Your choices and requests
- Turn off the Discord server permission any time on your profile, or remove DonutKing under Discord → User Settings → Authorized Apps. You keep using the site normally.
- Set loss limits or take a break in the Wallet Center (how they work).
- To get a copy of your data, correct it or ask for it to be deleted, write to support at donutking.gg or use the contact form. Staff handle these requests by hand. Records of money that moved are kept as stated in section 2, because every balance on the site depends on them.
- Depending on where you live (for example in the EU or the UK), you may also have the right to object to how your data is used and to complain to your data-protection authority.