declaude. privacy

The text you paste is never written to a database, a log file, or a disk anywhere we control. It exists in memory for as long as the rewrite takes, and then it is gone.

That is the whole promise, and the rest of this page is what it does and does not cover. Written plainly because a privacy page that needs a lawyer to read is not telling you anything.

What we never store

• Your text. Not what you paste, not what comes back. It is not in our database, not in our logs, and not on disk.
• Your rewrites. There is no history feature, and that is deliberate rather than unfinished. Results live in your browser tab; close it and they are gone.
• Your raw IP address. See below — we keep a hash, and a deliberately weak one.

What we do store

• Measurements about each request, with no content: word counts in and out, how much the register moved, how long it took, and what it cost us. This is how we know whether the tool works and what to charge.
• A daily-rotating hash of your IP address. Salted with a secret that changes every day, so two requests from you on the same day can be recognised as the same source — which is how the free-tier limits work — and requests from different days cannot be linked at all. It is not reversible to your address.
• If you have an account: your email address, your credit balance, a hash of each API key (never the key itself), and the same per-request measurements above, attached to your account.
• If you previously asked to be notified: that email address, until you unsubscribe. That list is not joined to anything else.

Who else sees your text

This is the part most privacy pages skip, and it is the honest limit of the promise above.

declaude does not run the language models itself. To rewrite your text we send it to OpenRouter, which runs a model and returns the result. We do not control their retention, and we will not pretend otherwise: "we never store your text" is a statement about us, not about the entire path your text takes.

We do not send your name, your email, your account, or your IP to them — only the text and the instructions for rewriting it.

Who we use

• Railway — hosting.
• Cloudflare — the network in front of the site.
• Supabase — the database holding accounts and the measurements above.
• Stripe — payments. We never see your card; Stripe holds it and we hold a reference.
• Resend — sign-in links and notices.
• OpenRouter — the rewrite itself, as above.

Cookies

One, and only if you sign in: a session cookie so you stay signed in. No analytics, no advertising, no third-party trackers, nothing to consent to.

Your account

Email [email protected] to get a copy of what we hold on you, correct it, or delete it. Deleting removes your email, balance and keys. Anonymised measurements may remain, because by then they are no longer connected to you.

Unused paid credit is refundable — ask. See also terms.

Changes

If this page changes in a way that matters, account holders get an email. We will not quietly widen what we collect.

Last updated 23 August 2026. Questions: [email protected].