Privacy

Last updated 9 August 2026

We do not store your drafts. A draft you check is sent to a model and a search engine to be checked, and what we keep afterwards is a fingerprint of the text, the individual sentences we identified as factual claims, and the verdicts we reached. We do not sell data, we run no advertising, and we add no analytics of our own.

What we keep when you check a draft

This is the part that matters most, so it goes first and in detail.

We do not store the draft. The full text you submit is held in memory for the length of the check and is not written to our database. The column that could hold it stays empty on every request our service makes.

What we do write down for each check:

  • A SHA-256 hash of the text. This is a one-way fingerprint. It lets us recognise a draft we have already checked so a repeat returns instantly, and it cannot be turned back into your writing.
  • The sentences we identified as factual claims, and the exact span each one came from. These are excerpts of your draft, and we are telling you plainly that we keep them. Without them we cannot show you a result, a history, or a source.
  • The verdict, score, reasoning and source URL for each claim.
  • Counts and costs: how many characters, how many claims, how many searches, how long it took, what it cost us. No text.

So the honest summary is not “we store nothing”. It is: we store the sentences we checked and the answers, and never the draft they sat in.

Your account

If you create an account we store your email address and a hash of your password. We never hold the password itself and cannot recover it, only reset it.

API keys are stored hashed as well. This is why a key is shown once when you create it and never again — we genuinely cannot look it up.

If you check a draft without signing in, we identify you by a hash of your IP address rather than the address itself, purely to apply the daily free limit.

Who else sees your text

Checking a claim means asking other services. We cannot do the work without sending your text out, so here is exactly who receives what.

  • OpenRouter routes our requests to the language models that extract and judge claims. It receives the draft text.
  • Serper, Brave Search and SerpAPI run the web searches. They receive short search queries built from individual claims, not your draft.
  • Neon hosts our database and Fly.io runs the application, so both hold the records described above.
  • Paddle is our merchant of record and handles all payment. See below.

We do not send your text anywhere else, and we do not sell or share it with anyone for advertising or training.

Payment

Paddle sells the subscription, not us. We never see your card details — they do not pass through our servers at any point. We store only the customer and subscription identifiers Paddle gives us, so we know which plan your account is on.

Paddle's own privacy terms cover what they collect at checkout.

Cookies and tracking

We set one cookie, and only after you sign in: a session cookie that keeps you signed in. That is the entire list.

We run no analytics of our own. No Google Analytics, no Plausible, no PostHog, no pixels, no advertising network. Nothing we have added measures you.

The one exception is the checkout: our payment provider loads its own script on the pricing page to measure how its checkout performs. That is Paddle's, not ours, and it runs only where the checkout does.

How long we keep it

Check records and their claims are kept while your account exists, so your history stays available to you. We do not currently delete them automatically after a fixed period, and we would rather say so than imply a schedule we do not run.

Cached results are stored against the text hash so a repeated check can be answered without spending money on it again.

Getting your data, or getting rid of it

Email support@useclaimcheck.com and we will:

  • send you everything we hold about your account, or
  • delete your account and its checks and claims, or
  • correct anything that is wrong.

We aim to do this within 30 days. You do not need to give a reason, and we will not ask you to sit through a retention offer.

Age

Claim Check is a tool for people who publish work. It is not intended for anyone under 16, and we do not knowingly hold data about children.

Changes to this page

If we change what we collect or who we send it to, we will update this page and move the date at the top. If a change is material — a new processor receiving your text, for instance — we will email account holders rather than rely on you noticing.

The Terms cover what the service does and what it does not promise.

Questions about this page: support@useclaimcheck.com. See also Privacy and Terms and Refunds.