We store nothing you type into the free tools.
Not a shortened version of a longer policy — this is the whole policy. If it were longer than a screen, that would itself be the problem.
The free tools
The readability check and the fix generator both run entirely in your browser. Nothing you paste into them is sent to us, because there is no server on the other end to send it to. That is why the readability check asks you to paste your page source instead of giving it a URL: a URL box would require our server to fetch your page, which would mean a copy of it passing through our infrastructure every time you press a button.
Why there is not even a saved preference. An earlier version of this site kept your language choice in the browser. We took it out. English lives at the root and Chinese lives at /zh/, so the language is a property of the address you are on — there is nothing to remember, nothing to clear, and no reason for the site to leave a file on your machine. The two free tools behave the same way: they hold what you paste in memory for as long as the tab is open, and drop it when you close it.
The submission form
Submitting a page is the only thing on this site that stores anything about you, so it gets its own section rather than a clause buried in a longer one. It stores exactly what you typed: the domain, the query, the page URL if you gave one, your email address, your note, and the report from the check you ran — plus a hash of your IP address and your browser's user-agent string. That is the whole row.
The receipt number you get back is how you look the submission up later. It is a lookup key, not a login — whoever holds it can see that row, and nobody can guess it. Ask us to delete the row and it goes; there is no retention period to argue about and no backup copy kept for compliance.
Why the IP is hashed rather than dropped. Rate limiting needs to know whether two submissions came from the same place, and it needs nothing else. A hash answers that question without keeping the address. It is pseudonymous, not anonymous: IPv4 is a small enough space that someone holding both the database and the salt could enumerate it. We say so because calling it anonymous would be a lie, and it is an easy lie to get away with.
The paid jobs
A paid job requires access to your site, and that changes the situation honestly. We ask for the narrowest access that lets us make the agreed changes — usually a staging environment, a CMS login, or a repository with a branch we can open a pull request against. We do not ask for your payment provider, your customer database, or anything the job does not need.
What we look at while doing the job is your public pages and the files the job concerns. We do not copy your content elsewhere, we do not train anything on it, and we do not use it as an example in our own marketing without asking first.
Access is revoked when the job closes. If you want it revoked sooner, revoke it — we will ask you to re-grant it if a follow-up is needed, rather than holding a key we no longer need.
Payment is handled by a third-party processor. We never see your card number and we do not store it.
The monitoring plans
Monitoring stores the domain and the queries you asked us to track, so that we can show you what changed since last month. That is the whole dataset. We do not build a profile of your visitors, because we never see your visitors.
You can delete a monitored brand at any time and the stored queries go with it.
Privacy questions
Do you log IP addresses?
Two things touch it, and both are stated here rather than implied. The submission form stores a SHA-256 hash of your IP with a fixed site-wide salt — not the address itself — and only to count how many submissions came from one source in an hour. The site check on the submission page sends the URL you paste to our edge function, which fetches it the way a crawler would, so that request carries your IP to our host like any request to any site. Everything else, including every free tool that runs in your browser, sends nothing anywhere.
What do you keep when I submit my site?
Exactly what you typed: the domain, the query, the page URL if you gave one, your email address, your note, and the report from the check you ran — plus the IP hash above and your browser user-agent. Nothing else. The receipt number you get back is the lookup key, and asking us to delete the row deletes it.
Is there analytics on this site?
No. No Google Analytics, no Plausible, no pixel, no session recording. We do not know how many people visited today, and we decided that was an acceptable price for not counting you. It also means we cannot show you a traffic chart, which is a real cost to us rather than a boast.
Why is there no cookie banner?
Because there is nothing to consent to. A banner exists to ask permission for tracking; this site sets no cookies and runs no tracking, so a banner would be asking permission we do not need. If we ever add one thing that tracks, the banner comes with it — not the other way round.
What do you keep if I buy something?
The payment processor keeps the transaction; we see a confirmation carrying the amount and the email you paid with, not your card number. A monitoring plan additionally stores the domain and the queries you asked us to track, and deleting the brand deletes both.
Can I use the generated files for client work?
Yes. The files the generators produce are yours — no attribution, no licence fee, no restriction on commercial use. We did not invent llms.txt or schema.org and we are not going to pretend to own the output of a form.
How do I reach you about privacy?
Write to the address below. It is one address, a person reads it, and privacy questions go there too — no separate portal, no form that files your request into a queue and answers nothing. If you want something you sent us deleted, say so in the message and it gets deleted.