Cookie Policy
Effective Date: March 1, 2026 · Version 1.0
2. How We Use Cookies
Customer City uses cookies and similar technologies for the following purposes:
- Authentication: To identify you when you sign in and maintain your session
- Analytics: To understand how users interact with the Service, which features are used most, and where users encounter issues
- Error monitoring: To detect, diagnose, and resolve software errors and performance issues
- Preferences: To remember your interface preferences (such as dark/light mode and sidebar state)
- Extension caching: To store health scores and deal data locally in the Chrome Extension for faster load times
We do not use cookies for advertising, retargeting, cross-site tracking, or selling data to third parties.
3. Strictly Necessary Cookies
These cookies are essential for the Service to function. They cannot be disabled without breaking core functionality. No consent is required for strictly necessary cookies under the ePrivacy Directive.
| Provider | Cookie Name | Purpose | Type | Duration |
|---|---|---|---|---|
| Clerk | __clerk_db_jwt | Authentication session token — verifies your identity across page loads | HTTP cookie | Session |
| Clerk | __clerk_client_uat | Client-side user activity timestamp — keeps your session active while you are using the Service | HTTP cookie | 7 days |
4. Analytics Cookies
These cookies help us understand how you use the Service so we can improve the product experience. Analytics cookies are non-essential — the Service functions without them.
| Provider | Technology | Data Collected | Retention | Opt-Out |
|---|---|---|---|---|
| PostHog | Cookies + localStorage | Page views, feature interactions, session duration, button clicks, feature flag evaluations. Does not collect form input values, keystrokes, or personal identifiers beyond user ID. | 12 months rolling | See Section 9 |
PostHog localStorage keys: PostHog stores a distinct ID and session replay identifiers in localStorage. These persist until cleared by you or until the data expires.
5. Performance and Error Monitoring
We use error monitoring to detect and resolve issues that affect your experience:
| Provider | Purpose | Data Collected | Retention |
|---|---|---|---|
| Sentry | Error tracking and performance monitoring | Error messages, JavaScript stack traces, browser type, OS version, URL where the error occurred. Sentry also records sampled session replays (approximately 10% of normal sessions, 100% of sessions with errors). Session replays record user interactions including clicks, scrolls, and visible page content — sensitive form fields are automatically masked. | 90 days |
Error monitoring is classified as a strictly necessary function required for the secure and reliable operation of the Service. Sentry uses browser storage (localStorage and IndexedDB) for session replay functionality.
6. localStorage and Browser Storage
In addition to cookies, we use browser localStorage (a web storage mechanism) to store certain data locally on your device. This data is never transmitted to our servers unless explicitly stated.
| Category | Examples | Transmitted? | Duration |
|---|---|---|---|
| UI preferences | Dark/light mode, sidebar state, dashboard tab selections | No | Persistent (until cleared) |
| PostHog identifiers | Distinct ID, session replay ID | Yes (to PostHog) | Persistent (until cleared) |
| Zustand state stores | Client-side application state (filter selections, view preferences) | No | Session or persistent (varies by store) |
7. Chrome Extension Storage
The Customer City Chrome Extension uses the Chrome chrome.storage.local API (not browser cookies) to store data locally within the extension environment:
| Data | Purpose | Auto-Expiry |
|---|---|---|
| Cached deal health scores | Avoid re-fetching health data on every page visit | 24 hours |
| Cached portfolio data | Display portfolio health without re-fetching | 1 hour |
| Cached deal descriptions | Store AI-generated deal descriptions locally | 7 days |
| Authentication token | Keep you signed in to the extension | Until sign-out |
| Feature flags | Control which features are enabled for your account | Refreshed on each authentication |
| Analytics opt-out flag | Record your preference to opt out of extension analytics | Persistent (until changed) |
All Chrome Extension storage data remains on your device. Cached data is automatically evicted at the expiry times listed above. You can clear all extension data by removing the extension from Chrome.
8. Third-Party Cookies
Customer City does not use:
- Advertising cookies or tracking pixels
- Cross-site tracking cookies
- Social media cookies or widgets
- Retargeting or remarketing cookies
The only third-party services that set cookies or use browser storage on the Customer City domain are Clerk (authentication), PostHog (analytics), and Sentry (error monitoring), as described in Sections 3, 4, and 5 above.
9. Managing Your Cookie Preferences
You can manage cookies in several ways:
Browser Settings
Most browsers allow you to block or delete cookies through their settings. Note that blocking strictly necessary cookies (Clerk authentication) will prevent you from signing in to the Service.
PostHog Analytics Opt-Out
To opt out of PostHog analytics tracking, contact us at privacy@customercity.com and we will disable analytics for your account. You can also use browser privacy extensions that block third-party scripts.
Chrome Extension Analytics Opt-Out
To opt out of Chrome Extension analytics, set the feature_analyticsOptOut flag to true in the extension's storage, or contact privacy@customercity.com for assistance.
Clearing Extension Data
To clear all data stored by the Chrome Extension, remove the extension from Chrome (Menu → Extensions → Remove) and reinstall it if desired. This clears all cached health scores, authentication tokens, and preferences.
10. Cookie Consent
Under the EU ePrivacy Directive (2002/58/EC, as amended) and GDPR, non-essential cookies require your consent before they are placed on your device. Strictly necessary cookies (such as authentication cookies) do not require consent.
We are implementing a cookie consent mechanism that will allow you to accept or reject non-essential cookies (specifically, PostHog analytics) before they are activated. Until this mechanism is in place, you may opt out of analytics tracking by contacting privacy@customercity.com or by using browser-level cookie controls.
We will update this section when the cookie consent mechanism is deployed.
11. Changes to This Policy
We may update this Cookie Policy from time to time as our use of cookies changes. For material changes (such as adding new tracking technologies or new categories of cookies), we will:
- Update this page with a new effective date and version number
- Note the changes in our Privacy Policy change log
The most current version of this Cookie Policy is always available at app.customercity.com/cookies.
12. Contact Us
If you have questions about our use of cookies or this Cookie Policy, contact us:
Customer City, Inc.
11335 NE 122nd Way, Suite 105
Kirkland, WA 98034
United States
Privacy inquiries: privacy@customercity.com
Website: www.customercity.com