Legal - Cookies notice
Cookies Notice
Effective from Version 1.1
2. Our cookie categories
We group everything we set on your device into four categories. You control the Analytics and Marketing categories via the cookies banner; strictly necessary items are exempt from consent, and on-device preference storage falls within the functionality exemptions of PECR as amended in 2025.
2.1 Strictly necessary cookies (always on, no consent required)
Without these the service cannot work - they are exempt from consent under PECR Reg. 6.
| Name | Purpose | Duration |
|---|---|---|
| pm_session | Logged-in user session (httpOnly + Secure + SameSite=Lax + signed). | 8 hours |
| pm_ref | The referral code from an affiliate link you followed, so the discount you were promised applies at sign-up and checkout. Holds the code only - no identifier of you. | 30 days |
| pm_csrf | CSRF double-submit cookie protecting POST routes. | session |
2.2 Strictly necessary similar technologies (always on)
These live in your browser's own storage (localStorage / IndexedDB), never travel to third parties, and exist so the app can work securely on your device:
| Name | Kind | Purpose | Duration |
|---|---|---|---|
| pm-consent-v1 | localStorage | Your cookie-consent choices (the record the banner reads). | until you clear it or the banner version changes |
| user | localStorage | Cached account details (name, email) so the page renders instantly after sign-in. | until sign-out |
| pm_active_context | localStorage | Which workspace (personal or a team) you are working in. | until changed |
| pm_ref | localStorage | The referral code you applied, kept until it is attached to your account. | 30 days |
| pm_active_conversation | localStorage | Which conversation is open, to suppress duplicate notifications. | until you leave the conversation |
| pm_e2ee / pm_mls / pm_local_vault | IndexedDB | Your device encryption keys and end-to-end-encryption state - these are what make your DMs readable only on your devices. | until sign-out / browser data cleared |
| pm_mls_plain | IndexedDB | A local, on-device cache of messages your device has already decrypted, so encrypted chats open instantly. | until browser data cleared |
| calendarView, pm_sound_enabled, pm-tips-collapsed and similar pm-* keys | localStorage | On-device UI preferences (calendar view, notification sound, collapsed tips). | until changed |
| short-lived handoffs (openConversationId etc.) | sessionStorage | Carry an action from one page to the next (e.g. "open this conversation"). | current tab session |
2.3 Analytics (consent required - defaults OFF in the UK / EU)
Google Analytics loads only after you accept the Analytics category in the banner - and never while the California "Do Not Sell or Share" opt-out is on. IP anonymisation is enabled and all advertising features (ad storage, ad personalisation) are disabled. In US notice-model regions the category defaults on and you can switch it off at any time.
| Name | Purpose | Duration |
|---|---|---|
| _ga, _ga_* | Google Analytics 4 - aggregated visitor counts + page paths. | up to 2 years |
2.4 Marketing (consent required - defaults OFF in the UK / EU)
We do not currently set any marketing cookies. This category is reserved for the future - if we ever add one, the banner version is bumped and you are asked again.
3. California "Do Not Sell or Share My Personal Information"
PartnerMe AI does not sell or share personal informationas the CCPA / CPRA define those terms - we run no advertising, and our analytics is consent-gated with all advertising features disabled. If you're a California resident the cookies banner still shows a dedicated "Do Not Sell or Share My Personal Information" toggle as a guarantee: setting it on records a CCPA opt-out in our consent log and disables all analytics + marketing cookies regardless of any prior consent - the Google Analytics loader checks it directly. "Reject all" also records the opt-out.
4. Your controls
- Click "Cookie preferences" in the footer to reopen the banner with your current choices. (The home chat screen has no footer - use the "Cookie preferences" button on Privacy & Data there, or any other page's footer.)
- Pressing Escape or clicking outside the banner counts as "Reject all" - we never treat dismissal as consent.
- You can also block cookies in your browser settings - note that doing so may break the strictly-necessary cookies and prevent you from logging in.
- Mobile + assistive-tech users can use keyboard navigation + screen readers; the banner is a proper ARIA dialog with focus trap.
5. How we record your consent
Every consent decision is stored as an audit row containing: a hashed IP (never the raw IP), your browser User-Agent, the region we detected, the version of the banner you saw, and your choices per category. PECR + UK GDPR Article 7(1) require this audit trail; we hold it for as long as you have an account, then delete or anonymise per our Privacy Policy. Anonymous consent records (no account) are pruned after 24 months.
6. Changes
When the cookie list changes materially we bump the banner's version number - this re-prompts you for fresh consent.
7. HIPAA Notice
Our cookies, similar technologies, and analytics are never used to collect, infer, or transmit Protected Health Information ("PHI"). They operate on the same non-PHI basis for all workspaces, including HIPAA-enabled workspaces, and are confined to non-PHI purposes such as authentication/session management, security, preferences, and aggregate analytics. Analytics event payloads are scrubbed to non-PHI scalar/enum tokens (a sanitiser strips free-form and potentially identifying content) before any event is recorded, and no analytics or advertising cookie is ever used to process PHI. You must not place PHI into any field, URL, or identifier that could be captured by cookies or analytics. See the HIPAA section of our Privacy Policy and the in-product BAA at /baa.