Start here
Two kinds of tool, two different answers
This site runs two categories of tool, with a different privacy answer for each. Local tools do their work in your browser using JavaScript downloaded with the page. AI tools send your text to a server, which passes it to an AI provider and returns the result.
Every tool page says which kind it is, before you paste anything. The cleaners, character removers, formatters and watermark scanners are local. The humanizers, rewriters, generators and text analyzers are the server kind. A daily run limit on a page means a server is doing the work.
The rest of this policy takes each category in turn, then covers the two things that apply to the whole site: analytics and the services the site is built on.
Local tools
Local tools: your text never leaves the device
When a tool is local, the text you paste is held in the page and processed by code running on your own machine: no upload step, no request carrying the text, nothing for us to receive, read or keep. Closing the tab ends it.
This is why local tools carry no run limit and no length cap: a limit exists to protect a server from cost, and none is involved. It's also why they keep working if your connection drops after the page loads.
To verify this yourself, open your browser's network panel and run a local tool. No request leaves during the run.
AI tools
AI tools: one request, and no copy kept
When you run an AI tool, the page sends your text to our API endpoint. That endpoint checks the request is valid, applies the run limit described below, and forwards your text to Groq, the AI provider that produces the output. The result comes back through the same path and returns to your browser.
We don't write your text to a database, a log file or a cache. The response carries a no-store instruction, so it isn't held by browsers or intermediate caches. Once the request finishes, our side of it is over.
There are two limits on what you send in a single run: input must be between 1 and 12,000 characters, and an instruction field, where a tool offers one, travels with the text in the same request.
- What is sent
- The text you pasted, the route you are on, the engine family that route uses, and any optional instruction you typed.
- What is not sent
- No name, no email, no account, no browsing history. There is nothing of that kind to send, because none of it is collected.
- Who receives it
- Our API function, and then Groq, which runs the model that produces the output.
- What is kept afterwards
- Nothing from the text itself. Only the usage counter described in the next section.
The one record
The only thing we store, and what it contains
AI runs are capped at 5 per rolling 24 hours, which requires knowing whether a visitor has already run some. Without an account, that means working from the network address the request arrives on.
That address is never stored: it's hashed with SHA-256, and the first 32 characters of the result become the key of a counter. The counter holds a number, how many runs that key has used, not your address, text, route or output.
The counter expires automatically after 86,400 seconds (24 hours). Nothing renews or archives it before it goes. That's the complete extent of what we retain about a visitor.
Measurement
Analytics, and what it actually measures
Google Analytics 4 loads on every page of this site. It records page views and general usage patterns: which pages get visited, roughly where visitors are, what device they're on. It sets cookies in your browser to recognise a repeat visit as the same session.
Analytics sees the pages you open. It doesn't see the text you paste into a tool, since that text is never part of a page view. For a local tool the text never exists outside your browser; for an AI tool it travels in a separate request analytics has no part in.
Google processes this data under its own terms, as the provider of that service. The cookie policy page lists the specific cookies involved and how to clear or block them.
Dependencies
The services this site is built on
Three companies are involved in running this site, and naming each is more useful than a blanket statement about vendors.
- Vercel
- Hosts the site and runs the API function. As with any web host, its infrastructure handles the connection itself, which involves ordinary server-level request records outside our control.
- Groq
- Runs the AI model behind the server tools. Your text reaches Groq during a run. Groq's Services Agreement says it doesn't train on customer inputs or outputs without permission, and deletes customer data within 30 days of an account ending.
- Upstash
- Holds the usage counter described above. What it stores is a hashed key and a number, with an automatic 24 hour expiry.
Absences
What this site does not collect at all
Some of the strongest privacy statements here are about things that don't exist. There's no account system, so no password, profile or login history. There's no newsletter, no email capture and no contact form that stores what you typed.
Nothing is sold, rented or shared with advertisers or data brokers. This isn't only a policy position: there's no store of user data here that could be sold. No age information is collected either, since no account is ever created and no profile built.
There's no payment system, so no card details, billing address or transaction history exist anywhere in this service.
Upkeep
Changes to this policy, and how to raise something
This policy describes how the site actually behaves, so it changes when the site does. If a tool moves from local to server processing, or a new provider joins a run, this page is updated, and the page in question states it too.
Questions about anything here, including a request about data held about you, go through the contact page. Given how little is retained, the usual answer to a data request is that the only record is a counter that has already expired.