Home/Cookie Policy
Last updated
Cookie Policy
Sign-in storage, Google sign-in cookies, and Google Analytics used for product measurement — not for ads on EraseText.
This policy explains what EraseText stores in your browser. We do not use advertising cookies or social-media pixels. We do use Google Analytics for aggregated product measurement, as described below.
1. What cookies and browser storage are
Cookies are small files a website places in your browser; local storage is a similar browser feature that keeps data on your device. Both can be “first-party” (set by the site you are visiting) or “third-party” (set by someone else).
2. What we use
- Sign-in session (local storage, first-party): if you sign in, your session token is kept in your browser's local storage so you stay signed in between visits. It is removed when you sign out. If you never sign in, this is not created.
- Sign-in with Google (third-party, only during sign-in): when you choose Google sign-in, Google sets cookies on its own domain as part of the OAuth flow, governed by Google's cookie and privacy policies.
- Google Analytics 4 (third-party): used to measure site and product usage (pages viewed, key actions). Google may set cookies or use similar technology and process technical data such as IP address and browser type under Google's policies. We do not use these for advertising personalization on EraseText.
- Strictly necessary state: short-lived values needed to complete an action you started, such as finishing a sign-in redirect.
Your uploaded images are never stored in cookies or local storage.
3. Managing cookies and storage
Signing out removes your session from the browser. You can clear cookies and site data at any time through your browser settings, or block them entirely — the editor itself keeps working without sign-in, since erasing does not require an account. Analytics may be limited by browser controls or Google's opt-out tools; blocking analytics does not affect erase quality.
4. Changes and contact
If we change what we store in the browser, we will update this policy first. Questions: [email protected].