How we check codes and release times

We compare each code with the places the game’s developer publishes codes, such as the game’s Roblox page description or its official Trello board. Every code list shows “Last checked against official sources” and how long ago that was. When a check fails we keep showing the last successful time instead of pretending it is fresh.

We cannot log in to every game and try every code, so we never call a code “verified”. A new code we find waits for review before it is listed. A code that disappears from the official source is marked “Likely expired” first, not deleted.

Anyone can tap “Works” or “Doesn’t work” on a code. One vote per code per day, at most 20 votes an hour from one network, and a site-wide cap per minute keep the counts honest. When at least 5 players in 24 hours say a code doesn’t work, and they are at least 70% of that day’s votes, the code is marked “Likely expired” until the next official check.

We store no account, no email and no IP address. A vote keeps only a one-way hash of your IP mixed with a salt that changes every day, so votes cannot be linked across days.

Dates and unlock times come from the publisher, the platform stores and the platform blogs, each linked next to the fact. When a publisher gives a rule (for example “midnight local time in all regions”) instead of a time, our table converts the rule for common time zones and says that it is our conversion.

Rumors and leaks are not stated as facts. If something is not announced, the page says “not announced”. Titles carry the month we last checked the page, not the current month.

We do not use official art, logos or screenshots. The colored tiles with short names are drawn by us. This site is independent and not affiliated with or endorsed by any game publisher or platform.