Privacy policy

The word counter, sentence counter, paragraph counter and reading time calculator run entirely in your browser. The text you paste into them is never transmitted, never reaches a server, and cannot be logged — the counting code runs on your own device.

Every other tool sends the text you submit to a large language model for processing and streams the result back to you. This is necessary for the tool to work: a grammar checker cannot correct text it has not received.

GrammarPlus does not write the text you submit, or the result, to a database. Requests are served with Cache-Control: no-store, so the response is not cached by us or by intermediaries.

TO SUPPLY: the name of the AI provider your deployment uses, that provider's data-retention policy for API requests, and whether your account has training on API data disabled. This is the single most important disclosure on this page, and it depends on which provider and plan you run — it cannot be inferred from the code, which only knows there is an OpenAI-compatible endpoint at the other end.

Three things, all of them for keeping the free tools usable rather than for building a profile of you.

• A random browser ID. A UUID generated in your browser and kept in localStorage under gp_client_id. It is sent with AI requests so the rate limiter can recognise a returning browser. It contains no personal data and identifies a browser, not a person. Clearing your site data removes it, and the tools keep working.
• Rate-limit counters. Request timestamps and word totals, keyed by IP address and by that browser ID, held in a short-lived store so per-minute and per-day limits can be enforced. They expire on a rolling window.
• Your theme choice. Light or dark, kept in localStorage so the page does not flash the wrong theme on load. It never leaves your browser.

TO SUPPLY: the retention window for rate-limit counters in your deployment, and whether IP addresses appear in your hosting or reverse-proxy access logs (they usually do) and for how long those are kept.

This site sets no cookies. There is no advertising, no third-party tracking script, and no consent banner because there is nothing to consent to.

Page views are counted with a self-hosted Plausible Analytics instance, which is cookieless and records aggregate data — page URL, referrer, country, browser and device type — without a persistent identifier and without building a profile across sites.

TO SUPPLY: your minimum-age policy. These tools are used heavily by students, so if you intend to serve under-13s (US COPPA) or under-16s (GDPR Article 8, varying by member state) this section has to say so explicitly and describe how consent is handled.

Because the only identifier held is a random browser ID you can delete yourself, most data-subject requests resolve by clearing your site data in the browser. To ask about anything else, email [email protected].

TO SUPPLY: the lawful basis you rely on under GDPR, whether you have an EU or UK representative, your response window for data-subject requests, and the supervisory authority a user may complain to.

Material changes will be reflected here with a revised effective date.