Quick answer
The quick answer, before the detail
Most tools on this site never send your text anywhere. They run inside the page, on your own machine, and the text stays there. A smaller set of tools call an AI model, which means the text has to reach a server for that run. Those are clearly marked, because they are the ones with a daily limit attached.
Here is the whole thing in four lines, and the rest of this page is the evidence behind them.
- Browser tools
- Your text never leaves the device. No upload, no limit, nothing to receive.
- AI tools
- One request to our server, forwarded to Groq, result returned. No copy kept.
- What we store
- A counter, keyed to a hash, that expires in 24 hours. Nothing else.
- What we never collect
- No account, no email, no payment details, no profile of you.
Browser tools
The tools that never see your text
Cleaning, removing characters, formatting and scanning for watermarks all happen in JavaScript that arrived with the page. Your text goes into the box, gets processed where it already is, and comes back out. At no point does a request carrying it leave your browser.
That is why these tools have no daily cap and no length limit. Limits exist to control server cost, and there is no server involved in the run. It is also why they keep working if your connection drops after the page has loaded.
You do not have to take this on trust. Open your browser's developer tools, switch to the network tab, and run one. Nothing goes out.
AI tools
The tools that do send your text, and exactly what happens
Humanizing, rewriting, generating and analyzing text need a language model, so those tools post your text to our endpoint. The endpoint checks the request is well formed, counts it against your daily allowance, and hands the text to Groq, the AI provider running the model. Groq returns output, we pass it straight back to your browser, and that is the end of it.
We do not write your text into a database, a log file or a cache anywhere in that chain. The response carries a no-store header, so it is not retained by your browser or any cache in between. An input has to be between 1 and 12,000 characters to be accepted at all.
- Goes with the request
- Your text, the route you are on, which engine family it uses, and any optional instruction you typed in.
- Does not go with it
- No identity, no email, no history. None of that exists here to send.
- Kept afterwards
- Nothing from the text. Only the run counter described next.
The one record
The only thing kept about you, and what is in it
AI runs are capped at 5 per rolling 24 hours, and enforcing that without an account means recognising a repeat visitor somehow. The network address a request arrives on is what makes that possible.
The address itself is never written down. It goes through a SHA-256 hash, the first 32 characters of that hash are taken, and that string is used as the name of a counter. The counter holds one thing: how many runs that key has used. No text, no address, no route, no output.
It deletes itself after 86,400 seconds, which is 24 hours exactly. Nothing archives it first and nothing extends it. That counter is the complete record this service keeps about any visitor.
Measurement
What analytics sees, and what it does not
Google Analytics 4 runs on every page. It counts page views, gives a rough geographic region and records what sort of device you are on, using cookies to tell a returning session from a new one.
What it does not see is anything you paste into a tool. That text is never part of a page view. With a browser tool it does not exist outside your own machine, and with an AI tool it travels in a separate request that analytics plays no part in.
Google handles that measurement data under its own terms, as the company providing the service. The cookie policy names the specific cookies and gives you three ways to block them.
Who else is involved
The three companies in the chain
Being specific about which providers touch what is more useful than a vague line about trusted partners.
- Vercel
- Serves the site and runs the API function. Like any host, its infrastructure handles the connection itself and keeps ordinary server-level request records we do not control.
- Groq
- Runs the model behind the AI tools, so your text reaches Groq during a run. Its Services Agreement says it will not train on customer inputs or outputs without permission, and deletes customer data within 30 days of an account ending.
- Upstash
- Stores the run counter. What sits there is a hashed key and a number, on a 24 hour expiry.
Not collected
Things this site simply does not have
Some privacy guarantees are strongest when the thing being protected does not exist. There is no login, so no password and no session history. No newsletter, so no email list. No checkout, so no card details or billing address.
Nothing is sold or shared with advertisers or data brokers, and there is no store of user data here that could be. No age data is collected either, since no account is created and no profile is assembled about anyone.
Upkeep
When this page changes, and how to ask about it
This policy describes how the site behaves, so it changes when the behaviour does. If a tool ever moved from running in your browser to running on a server, this page would say so and that tool's own page would say so too.
Anything you want to ask, including a request about data held on you, goes through the contact page. Given how little is retained, the honest answer to most data requests is that the only record was a counter that has already expired on its own.