Draft pending attorney review. This document has not been adopted and is not yet in force. Highlighted values are placeholders that must be completed before launch.

Cookie Policy

PeepMe · Cookies · Drafted August 2, 2026

This policy explains the cookies and similar storage PeepMe, operated by LEGAL ENTITY, uses. It is written to match what the Service actually stores today, which is little: what is needed to sign you in, keep you signed in, and remember your settings.

1. What we use, and why

We use browser storage — cookies, `localStorage` and `IndexedDB` — for the following, all of which are strictly necessary to provide the Service you asked for:

Authentication: keeping you signed in across pages and reloads. This is handled by our authentication provider and stored in your browser, not sent to third parties.
Security: a random per-browser identifier used only to recognise a device you have chosen to trust for two-factor authentication. It is not a fingerprint and is useless for tracking you across other sites — see how it is described on the Security settings screen.
Preferences: your settings, such as notification and privacy choices, so the Service behaves the way you left it.

2. What we do not use

We do not use advertising cookies, third-party ad networks, or cross-site tracking pixels. We do not sell or share the contents of this storage. Because the storage we set is strictly necessary to operate the Service, we do not show a consent banner for optional tracking — there is none to consent to.

If we ever introduce analytics or any non-essential storage, this policy will be updated and, where the law requires it, we will ask for your consent before setting it. ANALYTICS PROVIDER — IF ADOPTED

3. Managing storage

You can clear this storage at any time through your browser’s settings. Clearing it signs you out and resets your trusted-device status and any preferences held only in the browser — which is the intended trade-off, not a fault. Blocking strictly necessary storage entirely will prevent you from signing in.

1. What we use, and why

We use browser storage — cookies, `localStorage` and `IndexedDB` — for the following, all of which are strictly necessary to provide the Service you asked for:

Authentication: keeping you signed in across pages and reloads. This is handled by our authentication provider and stored in your browser, not sent to third parties.

Security: a random per-browser identifier used only to recognise a device you have chosen to trust for two-factor authentication. It is not a fingerprint and is useless for tracking you across other sites — see how it is described on the Security settings screen.

Preferences: your settings, such as notification and privacy choices, so the Service behaves the way you left it.

2. What we do not use

3. Managing storage