Privacy
What CheckRo keeps, and for how long
Every time window on this page is read from the code that deletes the data, not from a plan. If the code changes, this page changes with it.
What CheckRo never does
No IP addresses stored.
To stop floods, a few public pages, such as the account lookup and Roblox sign-in, count requests from each address in memory for up to ten minutes. That count is never written down and is never used to decide anything about you.No tracking cookies and no device fingerprinting.
Nothing reads your browser or device to recognise you. Members get one short-lived security cookie, and only while they sign in with Roblox (see below), and one more for 30 minutes if they use Verify with CheckRo on TackyLeague (see below). The only other cookies are for server staff signing in to the staff dashboard. CheckRo's pages are served through Cloudflare, and Cloudflare's privacy-first Web Analytics counts page views without cookies and without fingerprinting. CheckRo sees only the totals, never who visited.No direct messages.
CheckRo never sends you a private message. It answers in the server, where you spoke to it.No cross-server ban lists and no shared reputation.
A ban or a flag in one server has no effect in any other.No Roblox password, and nothing private.
CheckRo only reads what is public on your Roblox profile.
One number identifies you
CheckRo knows you by the numeric user id of the Roblox account you proved is yours. Usernames can change, the id cannot, and it is the smallest thing that can do the job. Your Discord user id is kept where CheckRo needs it, for example to hold your link or give you a role. Where it only needs to be compared later, it is kept as a salted hash instead.
What CheckRo reads from Roblox
| What is read | What is kept |
|---|---|
| Your public profile, to find the code in your About. | The About text itself is never saved. It is held in memory for about a minute, then dropped. |
| When the account was made, and how many public groups it is in, for the risk note below. | Only the age in days and the count are kept. |
| If you sign in with Roblox, Roblox tells CheckRo your user id, your name and when the account was made, and nothing else is asked for. | Nothing is kept beyond your link, and the sign-in pass Roblox hands over is thrown away straight after. |
One cookie while you sign in with Roblox. When you press Sign in with Roblox, CheckRo sets a cookie called __Host-checkro_signin. It holds a random value and nothing about you. It only checks that the browser coming back from Roblox is the one that left, so nobody can trick you into finishing a sign-in they started. It lasts 10 minutes at most and is deleted as soon as you are back.
Shared with TackyLeague only when you press Allow. TackyLeague can ask CheckRo to confirm your Roblox account (Verify with CheckRo). You sign in here with Discord, using the Discord account linked to your TackyLeague account, and CheckRo shows you exactly what it would share. Only if you press Allow does CheckRo tell TackyLeague your Roblox username and Roblox user id, the Discord user id they are linked to, how you verified and when. CheckRo asks every time and shares nothing without that press. It never sends TackyLeague anything on its own. Signing in sets a cookie called __Host-checkro_connect for 30 minutes; it holds a random value, and CheckRo keeps only a hash of it.
Everything CheckRo keeps
| Record | Holds | When it goes |
|---|---|---|
| Your link | Your Roblox user id, your Discord user id, your Roblox username at the time, and when and how you verified. | Kept while the link stands. It is deleted when you run /unlink, when you link a different Roblox account in its place, or when a different Discord account proves it owns that Roblox account and takes the link over. |
| Unlink records | The Roblox user id, when it was unlinked and why. Your Discord id is not stored here, only a salted hash of it that cannot be turned back into the id. | Deleted after 90 days. They are what makes the 15 day wait for a different Discord account work. |
| Verification attempts | Your Discord user id, the Roblox user id you tried to link, and the code you were given. | A code works for 15 minutes. The record is deleted 30 days after the attempt ends. |
| Verification links | Your Discord user id and the server you ran /verify in. | A link works once, and for 15 minutes at most. The record is deleted within an hour of the link being used or running out. |
| Role handoffs | The server, your Discord user id, your Roblox user id and username, so the bot knows which role to give. If the server shows a verified card, also your Roblox display name, the date your Roblox account was made and the link to your Roblox avatar picture (a link to Roblox, never a copy). | Deleted 7 days after the role is given. One that could never be given is deleted after 30 days. The display name, date and avatar link are erased the moment the role is given. |
| Risk notes | The server, your Discord user id, your Roblox user id, whether the note was clear or flagged and why, the age of the Roblox account in days, and how many public groups it is in. | A clear note is deleted after 90 days. Any other note is deleted after one year. On a note that is still kept, the account age and group count are wiped at 90 days. |
| Appeals | The server, your Discord user id, and anything you chose to write. | Deleted together with the note it answers, so within one year. An appeal against a ban goes after one year, or sooner if the ban goes first. |
| Staff decisions | Which staff member decided, what they decided, when, and any note they wrote. It holds no member id of its own. | Deleted after one year, so a late question about a decision can still be answered. |
| A server's ban list | The banned Roblox user id, the Discord user id that was banned if it was verified, the reason, and who added it. Only that server can read it. | Deleted two years after it was added, whether or not it was lifted. |
| Server settings | The choices a server made, such as its verified role, and the Discord id of the staff member who last changed them. No member data. | There is no automatic expiry on these today. |
| Premium gifts | Server only. Which server was given Premium as a gift, and until when. No member data. | Kept while the gift runs. Usually deleted within a couple of hours of the gift ending, and 7 days after it ends at the latest. |
| Log cards | If a server turns on a log channel, CheckRo posts short cards there, such as who verified. CheckRo keeps a note of which message each card is, with its server and channel, so it can find it again. The note holds no member id. | CheckRo deletes its own log cards from the log channel 90 days after posting them, a few at a time, so a busy channel can take a little longer. The note goes with the card. If CheckRo is removed from a server it can no longer reach its cards there, so the notes are dropped and the cards stay with that server. |
| Staff dashboard sign-ins | Staff only. A hash of the sign-in cookie, never the cookie itself, and the staff member’s Discord user id. | Ends after 7 days without use, and 30 days after signing in at the latest. Signing out deletes it straight away. |
| TackyLeague sign-ins | Only if you use Verify with CheckRo on TackyLeague. A hash of the sign-in cookie, never the cookie itself, your Discord user id, and your Discord username so the page can show who is signed in. | Ends 30 minutes after you sign in, however much you use it. Deleted within an hour after that. Signing out deletes it straight away. |
| TackyLeague requests | Only if you use Verify with CheckRo on TackyLeague. The Discord user id TackyLeague says started the request, and scrambled copies (hashes) of the request, of a check value from TackyLeague and of the one-time code. Once you press Allow, also a scrambled check of the Roblox account you were shown, locked to that one-time code so it cannot be turned back into your Roblox id; it is erased when TackyLeague uses the code, or with the request. No Roblox id. | A request works for 15 minutes and a code for 2 minutes. Used up as soon as TackyLeague uses the code, and deleted within an hour of that or of both running out. |
Deleting means deleting
When a window ends the record is removed, not hidden behind a flag and not moved to an archive. A sweep runs every hour, so a record goes within an hour of its window ending.
Risk notes, and being held for review
When you verify in a server, CheckRo writes a short note for that server's staff. It compares two public facts, how old the Roblox account is and how many groups it is in, against limits the server chose. The note is either clear or flagged, and a flag always carries its reason in plain words for staff.
By default a flagged member still gets their role, and staff take a look afterwards. A server can instead choose to hold the role until a person has looked. Either way the note stays in that one server, and you can run /appeal to say why it is wrong. A person on that server's team reads it.
Removing your data, and who CheckRo is for
Unlink at any time.
Run /unlink and your link is deleted straight away. The hashed unlink record stays for 90 days for the 15 day rule, and everything else goes on the clocks above.Not for anyone under 13.
Roblox only lets people 13 and over sign in to apps like this, and Discord does not allow apps to collect information about anyone under 13. Many members are young, which is why CheckRo keeps so little.Roblox sign-in asks for two permissions only,
openid and profile: who you are on Roblox and your basic public profile.
Questions about your data, and requests to delete it, can be sent to [email protected] or asked in our Discord support server. If you just want your link gone, you do not need to write to anyone: run /unlink in Discord and it is deleted at once. The terms of use say who runs CheckRo.
Last updated 1 November 2026. Every window on this page was read from the code that deletes the data on 24 October 2026.