Privacy policy
Last updated September 2026. This page describes the service’s current technical and operational behavior; it has not yet been reviewed by a lawyer, so treat it as accurate but not a substitute for legal advice.
Information we process
When you use a tool, the text you submit is sent to our API over HTTPS, processed in memory to produce a result, and discarded. It is not written to a database, log file, cache, or analytics system.
What we don't collect
- Accounts, names, or email addresses — there is no sign-up
- The content of what you paste into a tool
- A persistent tracking identifier, unless you explicitly accept the cookie banner for session-replay analytics (see “Third parties” below) — declining, or not answering, means none is ever set
Usage analytics
We track which tools are used, how often, whether an operation succeeded, and how long it took — as categories and buckets (e.g. “under 1 second”), never the text you submitted. This is first-party: it goes to our own database, not a third party, and a technical safeguard rejects any attempt to record raw input, output, a URL, or a search query before it ever reaches our server.
Server logs
Our API logs operational metadata only: timestamp, route, status code, duration, and a request ID. Logs never include request bodies, tool input, or credentials.
Third parties
Microsoft Clarity— session replay and heatmaps, used to understand how visitors use our tools, but only if you accept the cookie banner. Everything typed into or shown in a tool’s input or output is masked before it ever reaches Clarity — see our Cookie policy for what it sets and how to decline, and Microsoft’s own Clarity documentation for what it collects on its end. No other third-party analytics or advertising vendor is integrated. If another is added later, this section will name it the same way, before it ships.
Changes to this policy
Material changes will be reflected here and in the changelog.