Most game-code pages say "all codes verified, updated today". I run a small codes and release-date site, and I stopped writing that, because I can't log in to every Roblox game and redeem every code. Here's what the page shows instead.

"Last checked", not "verified"

Each code list is compared with the places the developer actually publishes codes, usually the game's Roblox description or its official Trello board. The list then shows "Last checked against official sources" and how long ago that was. If a check fails, the page keeps the last good time instead of pretending it's fresh. A code that disappears from the official source becomes "Likely expired" first. It is not deleted.

Letting players vote, without tracking them

Anyone can tap "Works" or "Doesn't work". When at least 5 players in 24 hours say a code doesn't work, and they make up at least 70% of that day's votes, it's marked "Likely expired" until the next official check. Limits are one vote per code per day and 20 votes an hour per network. The only thing stored is a one-way hash of the IP, salted with a value that changes daily, so votes can't be linked across days.

Release times are converted, and the page says so

For GTA 6's release date and unlock times by region, the publisher gives a rule ("midnight local time") rather than a time. The table converts that rule for common time zones and labels it as our conversion. Rumors are never stated as facts: if it isn't announced, the page says "not announced".

You can see it on the game codes page or a single game such as Rob Run. The full rules are in how we check codes. Disclosure: it's my site.

How do you handle data you can't fully verify? I'd like to hear other approaches.