Cookies and browser storage
Cookies are small records a website can store in your browser and receive again with later requests. Web applications can also use local storage, which stays in the browser but is not sent with every request. This policy distinguishes the public website from the signed-in app.
How We Use Cookies
Contextter uses cookies or local storage only where the relevant surface or provider needs them for the purposes below:
- Essential Cookies: Keep a signed-in session working and protect account access.
- Functional Cookies: Remember app preferences. The current theme setting is stored in local storage, not in a theme cookie.
- Analytics: Measure visits and campaigns on the public website with self-hosted Umami, without analytics cookies in the current standard setup. The signed-in app uses PostHog product analytics.
- Performance Cookies: Help us investigate loading and runtime failures through technical measurement and error diagnostics. Whether browser storage is involved depends on the tool and surface.
Storage used in the signed-in app
The table lists the main identifiers currently used or expected in the signed-in app. Exact names and lifetimes can change when an authentication or analytics provider updates its implementation:
These cookies are set in the signed-in app at app.contextter.com. The public website you are reading now does not set them.
| Storage identifier | Purpose | Duration |
|---|---|---|
| __clerk_* | Authentication session | Session or provider configuration |
| __session | User session management | Session or provider configuration |
| ph_*_posthog | PostHog product analytics and pseudonymous session state in the signed-in app | Configuration-dependent or until deleted |
Analytics & Measurement
The public website and the signed-in product are measured separately:
- Umami (self-hosted): Self-hosted website and help-center analytics for page views, referrers, campaigns, browser, device, and country in aggregate form
- PostHog: Product analytics in the signed-in app; depending on its configuration, PostHog can use a cookie and local storage and can associate events with an account
Umami is self-hosted and runs without analytics cookies in the standard setup on the public website and help center.
Third-Party Cookies
The following providers can set or read browser storage when you use the relevant feature:
- Clerk: Authentication provider
- Polar.sh: Checkout and customer portal when you buy or manage a subscription
- PostHog: Product measurement within the signed-in app
Managing Cookies
You can remove or block cookies and site data in your browser. Blocking authentication storage can prevent sign-in. Removing product-analytics storage resets the local identifier but does not remove account or billing records held for other purposes.
Most browsers allow you to:
- View what cookies are stored and delete them individually
- Block third-party cookies
- Block cookies from specific sites
- Block all cookies
- Delete all cookies when you close your browser
Browser-Specific Instructions
Menu labels change between browser versions, but these paths are a useful starting point:
- Chrome: Settings > Privacy and security > Third-party cookies or Site data
- Firefox: Settings > Privacy & Security > Cookies and Site Data
- Safari: Settings > Privacy > Manage Website Data
- Edge: Settings > Cookies and site permissions > Manage and delete cookies and site data
Updates to This Policy
We update this policy when the storage we use, a provider or its configuration changes. The date above identifies the current version.
Contact Us
If you have any questions about our use of cookies, please contact us at info@contextter.com