Checks
Two checks for publishing honestly
Free, no account, and they run entirely in your browser. Nothing you paste or tick is uploaded, stored or logged.
Claim checker
Paste a landing page, a README or an app store description. It points at the sentences a reader could hold you to but could not check — absolutes, popularity with no number, implied availability, compliance and security assertions, unmeasured speed — and says what to write instead.
Use it when: You are about to publish copy and want to know which sentences will not survive being asked about.
Trust page checklist
Answer eight questions about what your site actually does. It works out which trust pages you owe your readers — privacy, cookies, terms, refunds, disclosure — what each one has to contain, and the UK rule it comes from.
Use it when: You are launching something and are not sure which policy pages you genuinely need.
Why these two
Everything else on this site is a description of something hosted elsewhere. These two are not: they run here, on this page, and they exist because they are the two checks this site runs on itself before anything is published.
The first is a gate in the build. No product page here can use a phrase that asserts something without a record behind it, which is why the status page says three of the ten products are unfinished instead of describing plans in the present tense. The second is the reasoning that produced the trust centre — the list of pages this site owed its readers once it was honest about what it does.
Both were useful enough internally to be worth handing to anyone else publishing something. Neither is a legal review, and each says plainly what it cannot do on its own page.
What they will not do
They cannot tell you whether a claim is true, only that it is a claim. They cannot see your site. They are English-only. And a clean result means nothing matched a rule — not that a reviewer, a regulator or a reader will agree with you. Where a real answer matters, the regulator’s own guidance is the authority and these are a prompt to go and read it.
Something wrong, missing or wrongly flagged? Email kpleelaaravind@gmail.com — that is how corrections work here. A rule that flags ordinary writing is a bug worth reporting, and so is one that misses something it should catch.