Loading…
Last updated: 19 September 2026
When you use a text tool — the grammar checker, paraphrasing tool, summarizer, spell checker, prompt generator, originality analyzer or AI-to-human converter — the text you enter is sent to Google's Gemini API to produce your result. That processing is governed by Google's own privacy terms in addition to this policy.
We currently use the free tier of the Gemini API. Under Google's terms for that tier, Google may use the text you submit and the results it generates to improve its products, and human reviewers may read them. For that reason, please do not submit confidential or personal information.
If you are signed in, we store the tool used, your input and the generated output so they can appear in your dashboard history. If you are not signed in, we do not store your text or the result: they are returned to you and kept nowhere on our servers.
For every run of a text tool, signed in or not, we keep a record with no content and no identity in it: which tool ran, how long the text and the result were, how long it took and whether it succeeded. It holds no text, no account and no IP address. It tells us which tools are used and how fast they are.
The image resizer and image compressor run entirely inside your browser. Those images are never uploaded to our servers. The image-to-text tool reads your image inside your browser as well — the text recognition runs on your device, and the image is never uploaded. Only the extracted text is sent to our server, and on to Gemini, to tidy it up; from there it is treated like any other text you submit.
The MD5 generator sends your text to our server to compute the hash. It is not stored or logged.
Creating an account is optional. If you sign up, we store your email address and, when you use Google sign-in, the basic profile details Google returns (name and profile image). We use this only to authenticate you and to show your own generation history. Sign-in links are delivered by email through Brevo, which therefore processes your email address.
While you are signed in, each tool use is also logged against your account together with your IP address, so that misuse of an account can be investigated.
To limit automated abuse we keep a short-lived count of requests per IP address. Each entry expires about a minute after it is created and is deleted automatically within a few minutes.
We use Vercel Web Analytics to count page views. It sets no cookies, does not follow you across sites and does not collect personal data; we see aggregates such as page, referrer, country and device type.
We use Sentry to capture application errors so we can fix them. Error reports can include technical context such as browser type, page URL and a stack trace. We configure it to leave out request bodies — so the text you submit is not included — along with cookies and IP addresses.
For a sample of visits, and for visits where an error occurs, Sentry also records a session replay of the page to help us reproduce problems. All text on the page, and everything typed into it, is masked in your browser before the recording is sent.
We do not sell your data, and we do not use the content you submit to train our own models.
You can request deletion of your account and stored generation history at any time through GitHub Issues. Issues there are public, so do not post your email address or any personal details — just ask for deletion, and we will reply with a private way to confirm the account is yours.
If we change how data is handled, we will update this page and the date shown above.