Cookie Policy
Effective August 4, 2026
1. What this covers
This policy explains the cookies and browser local storage ResponsiveMe uses. We do not use advertising cookies or sell data to third parties. Section 4 below covers the analytics services we do use, including which ones set cookies directly from their own domain. Everything below exists to make the product work or to help us understand how it’s used in aggregate.
2. Essential cookies (always on)
ResponsiveMe uses Supabase Authentication to keep you signed in. This sets essential, first-party session cookies (managed by our authentication library) that identify your logged-in session. These cannot be turned off without losing the ability to stay signed in — they are not used for tracking or advertising.
3. Local storage (on your device, not sent to a server unless noted)
| Key | Purpose |
|---|---|
theme | Remembers whether you prefer light or dark mode. |
activeWorkspaceId | Remembers which workspace you last switched to, so the sidebar switcher opens where you left off. |
responsiveme:last-result | Caches your most recent AI generation locally so a refresh doesn’t lose unsaved work. This can include the content you generated. |
You can clear any of these at any time through your browser’s site data settings — doing so only resets these preferences and cached drafts, it doesn’t sign you out or delete anything from your account.
4. Analytics and error monitoring (optional, off unless configured)
If enabled by ResponsiveMe, we use PostHog for product analytics (pageviews and feature usage, routed through our own domain rather than a third-party analytics domain directly) and Sentry for error monitoring (to catch and fix bugs). These may set their own first-party-routed cookies/identifiers tied to your account once you’re signed in.
We also use Google Analytics (GA4) to understand aggregate site traffic. Unlike PostHog, Google Analytics is called directly from Google’s own domain and sets its own third-party cookies (for example _ga) in your browser, governed by Google’s privacy policy. None of these analytics tools are used for advertising, and none of this data is sold to third parties.
5. Payment
When you check out, Paddle (our payment processor) may set its own cookies during the checkout overlay to process your payment securely. These are governed by Paddle’s own privacy policy, not this one.
6. Changes
We’ll update the effective date above if what we store changes materially.
7. Contact
Questions can be submitted through the contact page.