Cookie Policy
The cookies we set, why, and how to turn them off.
Effective ·
What's set right now
Want the full policy? See the policy below ↓
This Cookie Policy explains how Peerlify, Inc. ("Peerlify," "we," "us") uses cookies and similar technologies on peerlify.com, login.peerlify.com, and web.peerlify.com. It supplements our Privacy Policy.
We keep the cookie set small. The marketing site uses strictly necessary cookies plus optional analytics and optional advertising measurement. The authenticated console relies on first-party session cookies only.
1. What cookies are
A cookie is a small text file that a website stores in your browser so that it can recognize you on subsequent requests. Similar technologies include local storage, the Fetch metadata sent by your browser, and pixel tags. For the purposes of this policy, "cookies" includes those similar technologies where they serve the same purpose.
2. Categories we use
- Strictly necessary. Required for the site or product to function — keeping you signed in, protecting forms, remembering your consent choice. You cannot opt out of these without losing functionality.
- Preferences. Remember non-essential choices such as theme.
- Analytics. Help us understand which features are useful and where we have rough edges. Optional and set only after you accept.
- Advertising measurement. Tells us whether a visit from one of our Google Ads led to a download or an account, so we stop paying for ads that don't work. Optional, set only after you accept, never used for remarketing or personalised ads.
We do not use cookies for remarketing, personalised advertising, or cross-site behavioural profiling.
3. Cookies we set
| Name | Purpose | Category | Duration |
|---|---|---|---|
pl_session | Keeps you signed in to the Peerlify console after authentication. | Strictly necessary | Session |
pl_csrf | Cross-site request forgery token used to protect form submissions. | Strictly necessary | Session |
pl_consent | Remembers your cookie-consent choice so we do not ask again on every visit. | Strictly necessary | 12 months |
pl_theme | Stores your theme preference (dark only today, future light support). | Preferences | 12 months |
__stripe_mid | Stripe fraud-prevention machine identifier. Set by Stripe.js on the billing and checkout pages of the console (our payment processor) so payments can be taken securely. | Strictly necessary | 1 year |
__stripe_sid | Stripe fraud-prevention session identifier. Set by Stripe.js during checkout. | Strictly necessary | 30 minutes |
ph_* | PostHog product analytics — pseudonymous user and event identifiers, set only if you accept analytics. | Analytics | Up to 12 months |
_ga | Google Analytics — pseudonymous identifier used to distinguish one browser from another. Set only if you accept analytics. | Analytics | 2 years |
_ga_E3SCDRPHR0 | Google Analytics — keeps session state for this property. Set only if you accept analytics. | Analytics | 2 years |
pl_adclk | Remembers the ad click identifier (Google Ads or OpenAI Ads) from the ad that brought you here, so an account you create can be reported to that platform. Set by Peerlify on peerlify.com and sent to Peerlify's own subdomains (only the sign-in service at login.peerlify.com reads it), deleted when you sign up or withdraw consent. | Advertising | 90 days |
_gcl_* | Google Ads conversion linker: ad-click identifier and conversion measurement. Set only if you accept advertising. | Advertising | 90 days |
__oppref | OpenAI Ads: the click identifier from the OpenAI ad that brought you here. Set only if you accept advertising. | Advertising | 30 days |
__obref | OpenAI Ads: a random browser reference used to measure conversions from our OpenAI ads. Set only if you accept advertising. | Advertising | 365 days |
__oaiq_consent | OpenAI Ads: records that you accepted advertising measurement for the OpenAI pixel. | Advertising | Until withdrawn |
oaiq_consent (local storage) | The OpenAI Ads SDK's own memory of your consent choice, so the pixel stays off after you withdraw. | Strictly necessary | Until cleared |
Names prefixed with pl_ are set by Peerlify directly (first-party). The __stripe_* cookies are set by Stripe, our payment processor, but only on the console's billing and checkout pages — they are required to take a payment safely and are not used for advertising. The ph_* and _ga* families are set by our analytics providers when you accept analytics, the _gcl_* family by Google Ads and the __oppref, __obref and __oaiq_consent cookies by OpenAI Ads when you accept advertising — see the next section.
4. Third-party cookies
Five third parties may set cookies, in different contexts:
- Stripe — our payment processor. When you open the billing or checkout pages of the console, we load Stripe.js, which sets the
__stripe_midand__stripe_sidcookies to detect and prevent payment fraud. These are strictly necessary to take a payment securely and are set without a consent prompt because you cannot complete a purchase without them; they are never used for advertising. See Stripe's cookie notice and privacy policy. - PostHog — product analytics, set only after you accept analytics. We use the EU-hosted instance and disable session recording on authenticated pages. See PostHog's privacy notice.
- Google Analytics — audience measurement on this marketing site (which pages get read, which entry points work). The tag is not requested at all until you accept analytics, and we run it with Google signals and ad personalisation turned off, so Google Analytics never uses ad personalisation. We do not use it for advertising or remarketing, and we do not link it to your Peerlify account. See how Google uses data from sites that use its services.
- Google Ads — conversion measurement on this marketing site, set only after you accept advertising. It tells us whether a visit that started from one of our ads led to a client download or a new account. We run it with Google Consent Mode so ad personalisation stays denied in every case; it is never used for remarketing or personalised ads. See how Google uses data from sites that use its services.
- OpenAI Ads — conversion measurement on this marketing site, set only after you accept advertising. It tells us whether a visit that started from one of our OpenAI ads led to a client download or a new account. The pixel is not requested until you accept, it is never used for remarketing or personalised ads, and we send it no name, email address or device data. See OpenAI's privacy policy.
We do not embed remarketing or audience tags. If we add a new third-party cookie in future, we will update this page and re-prompt for consent where required.
Conversion reporting after sign-up
If you accepted advertising and then create a Peerlify account, we store the ad click identifier (gclid, gbraid or wbraid from Google Ads, or oppref from OpenAI Ads) with your account for at most 90 days from the click, and report the following events to Google Ads or OpenAI Ads (whichever ad brought you here) using that identifier only: account created, first device online, second device online in the same network, and first paid subscription invoice (its amount before tax, and its currency). We never send your name, email address or any device data. The identifier is deleted within 97 days of the click. If your browser sends Global Privacy Control, nothing is captured. To stop reporting for an existing account, email privacy@peerlify.com.
5. The product application
The Peerlify console at web.peerlify.com uses strictly necessary first-party cookies — a session cookie issued via OpenID Connect and a CSRF token. It loads no analytics or advertising tags: no Google Analytics, no Google Ads, no OpenAI Ads, and no other measurement script. On the billing and checkout pages, Stripe.js additionally sets the strictly-necessary __stripe_mid and __stripe_sid fraud-prevention cookies described in Section 4; card details are entered inside Stripe's own iframe and never reach Peerlify's servers. The Peerlify client application (daemon and CLI) does not use cookies to communicate with the control plane; it uses OIDC-issued tokens and short-lived membership certificates.
6. Your choices
You can:
- Decline analytics cookies the first time you visit, or change your choice later from the cookie banner footer.
- Decline advertising measurement in the cookie banner (Customize → Advertising), or withdraw it later from the cookie settings on this page. Withdrawing deletes the
pl_adclk,_gcl_*,__oppref,__obrefand__oaiq_consentcookies in this browser. - Block or delete all cookies in your browser settings. If you block strictly necessary cookies, you will not be able to sign in to the console.
- Send a Global Privacy Control (GPC) signal — we honor it as an opt-out of analytics and as a hard opt-out of advertising measurement.
Browser-specific instructions: Chrome, Firefox, Safari, Edge.
7. Changes
We may update this Cookie Policy from time to time. Material changes — for example, adding a new analytics provider — will be announced in the cookie banner and on the site at least 15 days before they take effect.
8. Contact
Cookie questions: privacy@peerlify.com.