GRAMMAR CHECK
CORRECTOR
Browser extensions ↗

BROWSER EXTENSION PRIVACY

Your writing stays your choice.

Updated 17 November 2026 · Tiny Leo Company Limited

This policy covers the Grammar Check Corrector browser extension and the browser assistant preview. Our Grammar Privacy Policy also applies to our services.

What happens when you use a tool

The extension detects supported text boxes locally so it can show the Grammar icon. Opening the icon copies the chosen text box into the assistant on your device. It does not send your writing to our AI service while you are simply typing.

When you run a writing tool, the text you submit, your selected writing options, and any Template follow-up answers are sent over HTTPS to our Firebase/Google Cloud backend and OpenAI to generate a response. Text you submit may contain personal information or personal communications. Submit only content you want processed by these services.

Information handled on your device

The extension works without signing in. Its Account button opens the Grammar web app, where you can sign in with Google or Apple to sync account details and verified Premium access. Account credentials, profile information and primary account tokens are not sent back to the extension. The web account uses the Grammar Firebase project, and the server reads subscription status from Qonversion. Mobile purchases remain managed in their store; web purchases, when enabled, are processed by Paddle.

The extension caches verified Pro status for up to 12 hours so reopening the assistant does not repeatedly check it. Account and purchase updates invalidate this cache; AI requests still verify access on the server. This local status cache contains allowance metadata and a hashed browser-profile identifier, not writing or sign-in tokens.

The extension stores site-pause preferences, a private browser-access credential, legacy usage counters, appearance preferences, per-tool writing options (including any additional instructions you choose), and a separate anonymous Firebase session for the AI backend. Pausing a site stores that site’s hostname locally. The toolbar reads the active tab’s hostname to show the site control. These hostnames and your browsing history are not included in AI requests.

When the extension is installed and allowed on grammarcheckcorrector.io, the web app, demo and extension share a daily allowance within that browser profile. A bridge restricted to our own website exchanges a private browser-access credential. The server stores its hash and quota records (request ID, UTC day, timestamps and status), plus an optional linked account ID for verified Pro. No writing or Apple/Google sign-in tokens are exchanged. This browser credential authorizes shared allowance and Pro access; it is not a cross-device sign-in.

To recover an accidentally closed popup, the extension keeps its most recent draft and completed result on your device. An inline result is restored only for the same text box when its original input is unchanged; the toolbar can restore its own latest draft. The cache uses extension session storage where supported, which clears when the browser or extension session ends. Otherwise it uses local extension storage; cached sessions older than 24 hours are not restored. A new edit or tool-option change clears the cached result. Separately, History keeps your last 20 completed inputs and results in local extension storage until replaced by newer results or removed with History → Clear all. Recent tags and History can reopen these results without another AI request. Neither cache is synced to the cloud. Password, payment and one-time-code fields and other recognizable sensitive fields are excluded; this cannot identify sensitive information inside ordinary prose.

Service providers and operational data

Google Firebase provides the extension’s internal AI-backend authentication, writing configuration and backend connection. Optional Google/Apple account sign-in is handled separately on our website. OpenAI processes the writing requests. Cloudflare hosts our website, public configuration endpoint and this policy. Network requests may expose technical data such as IP addresses, timestamps and error information to the service handling them. We do not include an advertising or behavioral analytics SDK in the extension.

Writing content is used to provide the writing feature you request. We do not sell extension user data or use it for personalized advertising, creditworthiness or lending decisions. Our use of extension data is limited to delivering the extension’s stated functionality, security, and support.

Retention and your controls

We do not maintain a writing-history database for transient AI requests. Processing providers may retain requests or security and operational records under their applicable terms and account settings; this policy does not promise zero provider retention. Anonymous backend account records may remain after you remove local extension data.

Local extension preferences and backend authentication data remain until cleared or the extension is removed. Your first-party Grammar account and website sign-in session can remain after uninstalling the extension; use Account to sign out or delete your account. The free allowance resets at midnight UTC. Pending server reservations expire after four minutes; usage records are removed in bounded batches after 35 days. The server keeps a pseudonymous browser profile to recognize its allowance; deleting the linked account disconnects its profile bindings. You can pause individual sites, restrict the extension’s site access in Chrome, close the assistant without applying a result, clear its local data, or uninstall it.

Contact

For privacy questions or data-deletion requests, contact Tiny Leo Company Limited through support@tinyleo.com. Include the product name and relevant details, without sending sensitive writing unnecessarily.