Cookie Policy
Cookies and browser storage
Cookies are small text files a website stores in your browser. Websites can also keep information in your browser's local storage. This policy covers both, on peerx.ai and in the PeerX app.
Essential
These are needed for the site and the app to work: to keep you signed in, remember your choices, and take payments safely. They do not need your consent.
Cookies
| Name | Where | Purpose | Expiry |
|---|---|---|---|
i18next | PeerX app and API | Remembers the language you chose in your account. | 1 year |
__Host-peerx_handoff | PeerX app | Set when you sign up with Google or Apple on peerx.ai, so that the sign-in carried over to the PeerX app works only in this browser. Removed when you arrive in the app. | 2 minutes |
__stripe_mid | PeerX app, payment screens | Set by Stripe when you enter a card, to prevent payment fraud. | 1 year |
__stripe_sid | PeerX app, payment screens | Set by Stripe when you enter a card, to prevent payment fraud. | 30 minutes |
Browser storage
| Name | Where | Purpose | Expiry |
|---|---|---|---|
cookie-consent | peerx.ai | Remembers your cookie choice. | Until you clear it |
auth-storage | PeerX app | Keeps you signed in to the app and remembers your account details. | Until you sign out or clear it |
auth-signed-out:<id> | PeerX app | Tells your other open PeerX tabs in this browser that you signed out of an account, so they stop using it too. <id> identifies the account and organisation. | Until you clear it |
auth-refreshing:<id> | PeerX app | While one tab renews your sign-in, tells your other open PeerX tabs not to use the sign-in being renewed. Removed when the renewal finishes; left behind only if a tab closes part-way through. | Until the renewal finishes |
announcement_<id>_dismissed | peerx.ai | Remembers that you closed an announcement. | Until you clear it |
peerx-legal-acceptance-postponed | PeerX app | Remembers, for this browser session, that you chose to be reminded later about updated Terms and Privacy Policy. | When you close the browser tab |
peerx.checkout.pendingConfirm | PeerX app | On the payment screen you return to from Stripe after paying for a plan, holds the Stripe checkout reference and which account started the payment until PeerX has answered about it, so reloading the page still finishes the payment you started. Only the account that started the payment reads it. | When PeerX answers about the payment (confirmed, refused, or not found on this account), or when you close the browser tab |
peerx.workspace.v1.<id>.conversation.<id> | PeerX app | Remembers which conversation you last had open with an agent, and the project linked to it, so the Agent Workspace reopens it. The conversation itself is kept by PeerX, not here. The first <id> identifies your account and organisation, the second the agent. | Until you clear it |
peerx.workspace.v1.<id>.notes.session.<id> | PeerX app | Your scratch notes for one conversation in the Agent Workspace. They stay in this browser: they are not sent to PeerX and the agent does not see them. The first <id> identifies your account and organisation, the second the conversation. | Until you empty the notes or clear it |
peerx.workspace.v1.<id>.notes.new.<id> | PeerX app | Scratch notes you type before your first question to an agent. They move to that conversation once it starts. The first <id> identifies your account and organisation, the second the agent. | When the conversation starts, or when you empty the notes or clear it |
Earlier versions of peerx.ai stored two more keys after you signed in, signed up or paid here: peerx_access_token and peerx_refresh_token. The site no longer stores them. On your next visit it deletes both keys and tries to sign that stored session out. If that cannot finish, for example because you leave the page first, no browser holds the session any more, and PeerX ends it within 7 days. You now sign in to the PeerX app itself, which keeps its own sign-in (auth-storage, above).
Cloudflare, which carries traffic to our websites, may also set its own security cookies (for example __cf_bm) when it needs to tell people from automated traffic.
Analytics
Cloudflare Web Analytics, which Cloudflare adds to every page of peerx.ai, counts page views and visits without setting cookies or using browser storage, so it has no row on this page and runs without asking for your choice (see section 2 of our Privacy Policy).
Our website can also use Google Analytics, which sets the cookies below, but we do not use it today (see our list of subprocessors), so peerx.ai shows no cookie banner. Whenever it is used, none of these cookies is set, and no request is made to Google, until you choose “Accept All” in the cookie banner. If you later choose “Essential Only”, we stop Google Analytics and remove its cookies.
Google Analytics cookies
| Name | Where | Purpose | Expiry |
|---|---|---|---|
_ga | peerx.ai | Google Analytics: distinguishes visitors. | 2 years |
_ga_<container-id> | peerx.ai | Google Analytics: keeps the state of a visit. | 2 years |
We do not use advertising or cross-site tracking cookies.
Changing your choice
Today peerx.ai sets nothing that needs your consent, so there is no choice to make or change. If we start using Google Analytics, the cookie banner will ask you first, and you will be able to change your choice here at any time. You can clear cookies and site data in your browser settings whenever you like.
Changes to this policy
If we add or change a cookie, we update this page and its date.
Contact us
Questions about cookies: [email protected]. See also our Privacy Policy and Terms of Service.