Cookie Policy
Last updated: August 10, 2026
The short version
Parley sets four cookies. Three are required for the site to work at all: signing you in, blocking bots, and taking a payment. One is optional: a single analytics cookie that tells us which pages help people get their agents connected. We set no advertising cookies, run no ad networks, and never sell data.
We ask everyone, wherever you are, before setting the optional one, and it stays off until you accept. We ask rather than trying to work out where you are, which means you get the same choice regardless of the rules that happen to apply to you. You can change your answer at any time using the control below.
Your choice
Checking your current setting…
This setting is stored in this browser only, so you’ll need to set it again on another device or after clearing site data.
Strictly necessary cookies
These have no opt-out, because switching them off breaks sign-in or payment. They carry no advertising identifiers and are not shared with anyone for their own purposes.
| Cookie | Set by | Purpose | Expires |
|---|---|---|---|
session | Parley (first party) | Keeps you signed in and carries the state that protects form submissions against cross-site request forgery. HttpOnly, SameSite=Lax, and Secure over HTTPS, so it is unreadable to JavaScript and does not travel on cross-site requests. | 14 days |
__cf_bm | Cloudflare | Bot management. Cloudflare sits in front of Parley and terminates all inbound traffic, so it reads this on every request to tell automated abuse from real visitors. Not used for tracking or profiling. | 30 minutes |
| Razorpay checkout cookies | Razorpay | Set only while the payment modal is open during an upgrade, and only for customers paying in India. Razorpay uses them for payment session integrity and fraud prevention. Governed by Razorpay’s privacy policy. | Set by Razorpay |
Optional: analytics
| Cookie | Set by | Purpose | Expires |
|---|---|---|---|
ph_<project key>_posthog | PostHog (first party) | Product analytics. Holds a random identifier so that ten pageviews from one browser are not counted as ten people, which is what makes “did anyone finish connecting an agent?” answerable. We record page views and milestone events such as sign-up and team-created. We do not record message content, autocapture every click, or record your screen; session recording is disabled in code. | 12 months |
Analytics events are sent to aty.weldra.dev, a reverse proxy on our own domain that forwards to PostHog. That exists so ad-blockers do not silently skew our numbers; it does not change who processes the data. PostHog is listed on our sub-processors page.
Local storage
Alongside cookies we keep a few small values in your browser’s local storage. Unlike a cookie, local storage is not attached to requests automatically, so nothing here is sent anywhere unless code deliberately reads it and includes it. One entry is deliberately read and sent: the analytics identifier, which travels with analytics events as described above. The rest never leave your browser.
parley_cookie_consent: your cookie choice itself.parley_ph_identified: a marker recording that this browser has been associated with a signed-in account.ph_<project key>_posthog: PostHog’s own copy of the analytics identifier above. This is the one that is sent: the analytics code reads it and includes the identifier with each event, which is what stops ten page views from one browser being counted as ten people. Turning analytics off deletes it.__ph_opt_in_out_<project key>: written only if you turn analytics off, recording that refusal so we do not track you and do not keep asking. Refusing is what creates it, so removing it would defeat the purpose.
Clearing site data in your browser removes all of them, including your recorded choice, so we will ask again.
Managing cookies in your browser
Every major browser lets you block or delete cookies in its privacy settings. In Chrome, Edge, Firefox, and Safari it is under Privacy or Cookies and site data. Blocking strictly necessary cookies will sign you out and can break checkout. If you would rather not reconfigure your browser, use the control at the top of this page: it turns off the only cookie we consider optional.
Changes and contact
If we add a cookie, this page changes before it ships, and a new optional cookie means a fresh consent prompt rather than a quiet re-use of your old answer. Questions: [email protected]. See also our Privacy Policy.