Privacy

Last updated 6 November 2026

The short version

Everything that measures text — width in pixels, character counts, hreflang tags, keyword consistency — runs inside your browser and never leaves it. The single exception is a title or description you explicitly ask a model to rewrite. That string, its market code and its measured width are sent to our server and then to a model provider. Nothing else is.

What never leaves your browser

The six tools parse and measure text with JavaScript running in your own tab. There is no request to our servers while you paste a title, drop a CSV into the batch audit, or generate an hreflang block. You can disconnect the network, reload a tool and it still works.

What is sent, and only when you press a rewrite button

Asking a model to shorten a title is the one operation that costs money per call, so it has to happen on our side. That request contains:

Our function adds your account id only to charge one credit. The model provider sees the string and the instructions, not your account.

What we store

Error summaries from a failed model call may be kept in the ledger for debugging. They contain the failure reason, not your text.

Cookies and local storage

We set no analytics or advertising cookies. Your signed-in session is kept in your browser's local storage and is removed when you sign out. Our host, Cloudflare, may set a security cookie to tell humans from bots.

Who else is involved

Deleting your data

Ask and the account, its balance and its ledger rows are deleted. The one thing we may keep is the minimum accounting record a payment provider requires, if you have ever paid us.

Contact

Anything on this page, or a deletion request: [email protected].