Editorial policy

Every fact on this site is tied to a public page. One source stays labelled as one source. Two sources that disagree are both printed.

What counts as checked

I use studio pages, store pages, board certificates, reviews and databases. Source counts refer to independent publishers supporting a claim: a store, its API and its developer search are one source, and an article repeating another report is not independent confirmation. A search-result snippet is a clue, not a fact, until I open the page it points at. Scores always carry a date and a sample size when the source prints one. Release dates for unreleased films stay at the announced day. The Steam game stays “coming soon” until the store page says otherwise.

I write a short first-person note on each page about the judgment I made. The boundary of that judgment is one Limitation sentence. I do not describe the plumbing of how a page was fetched.

Corrections, takedowns, and generated footage

Email [email protected] with the URL and the source. I aim to reply within five business days. A copyright note about an image gets the image removed or replaced if you show you hold the rights. Fake “full movie” uploads are described as uploads, not embedded. I will not add a link whose only purpose is to play a pirated copy.

Pages are not opened for guest posts. There is no review score written by this site, and no star average that I calculated myself.

Questions people ask

Do you test codes inside a game?

There is no code list, because Christmas Heist on Steam is not released. If a studio posts codes later, the page will say how many public sources mention each code.

Will you add a language edition?

Only after a localised title is confirmed by two sources. A translated search suggestion on its own is not enough.

Sources

Advertisement