OPENME
Cookies & browser storage
OpenMe keeps its own storage footprint small. Most app preferences are stored in your browser, while third-party providers may use cookies or similar technologies when authentication, checkout, or analytics are involved.
1. What OpenMe stores directly
- Local storage: used for small UI and app state values such as dismissed prompts, studio preferences, sign-in flow helpers, and telemetry session identifiers.
- Consent cookie: used to remember that you dismissed the cookie/storage notice.
- Session storage: used for short-lived experience state such as splash behavior during the current session.
- Secure session cookie: when you sign in, OpenMe can maintain a secure server-readable session cookie to support future authenticated server features.
2. Third-party cookies and similar technologies
Some third-party providers used by OpenMe may place cookies or use equivalent browser technologies when their services are active.
- Firebase Authentication / Google sign-in: sign-in providers may use cookies as part of authentication, session integrity, and fraud prevention.
- Paddle: checkout and payment flows may use cookies or similar technologies for payment security, fraud checks, and purchase session handling.
- Vercel Analytics: analytics tooling may use browser identifiers or similar mechanisms to measure site usage.
3. Why these technologies are used
- • Keep you signed in and route you through authentication securely.
- • Remember app-level preferences and dismissed notices.
- • Support payment, fraud prevention, and billing operations.
- • Measure product usage so the app can be improved.
4. Your choices
You can clear local browser storage through your browser settings. Disabling or blocking third-party cookies may affect sign-in, checkout, and analytics-dependent features.
For the broader service terms, see Terms of Service.
