Security and data handling
Your work is checked where it already is.
Not a policy promise: the checks are rules in the page. This page states what runs, what is stored and what happens to a file after you close the tab.
- Uploaded when you run a check
- Nothing
- Model calls on your content
- None
- Stored without signing in
- Nothing
- Who can read a saved report
- You, and admins
Look closely before you trust the output.
The console runs on your device
Every check is a rule written in the page you loaded. Your code, copy, document or image is read in browser memory, scored there, and discarded when the tab closes. There is no request carrying your content to a server, which is why the console works on material you could not send to a third party.
Images are decoded locally and measured from the pixel data. Documents are parsed as text. Nothing is sent away to be read.
No model is called on your content
The findings come from deterministic rules, not from a language model looking at your work. The same input produces the same report a year from now, which is what makes a report quotable in a review.
That also means the checks cannot be talked around: there is no prompt to influence.
What is stored, and only if you save it
Signing in is optional. If you save a report, the record holds the label you gave the work, the content type, the score and grade, the verdict, a one-line summary, the findings with their severities, the measured metrics, the number of checks run, and the first few hundred characters of what you submitted.
That excerpt is stored purely so you can recognise a report in your dashboard later. The full submission is never stored.
- Reports are owned by the account that saved them.
- Access rules restrict reads and writes to the owner, with administrators able to review.
- Review requests hold your contact details and the brief you write.
- Contact messages are readable only by administrators.
Retention and deletion
Saved reports stay in your dashboard until you delete them. There is no automatic expiry, and no export pipeline moving them elsewhere. Deleting a report removes the record.
If you want your account and its records removed, say so through the contact page and it is handled directly.
Analytics stop at the event
The console records that a run started and which of the four checkers was used, so we can tell whether the product is working. The content of the run is not part of that event, and no third-party advertising tag is placed on the console.
What this does not claim to be
A report is not a warranty of correctness, a security audit or a legal opinion, and it does not detect who wrote something. It records what specific checks observed in a specific version of a file.
Where a decision carries consequence, a named reviewer signs a stated scope. That signature is the assurance; the report is the evidence it starts from.
Check something confidential
The check that cannot leak is the one people run on drafts.
Nothing is uploaded, no account is needed and closing the tab discards the input.