Essential authentication
The console uses __Host-scargo_session, a first-party cookie containing an opaque random session identifier. It is HttpOnly, Secure, SameSite=Strict, scoped to the host, and expires after seven days. It is set when you sign up, sign in or recover an account, and removed at sign-out. The server can revoke it earlier. Blocking it prevents account sign-in.
Browser storage
The console keeps API keys entered manually, newly created secrets and CSRF tokens in memory. It does not intentionally persist them in local storage. Pricing and the console use your device time zone locally to choose the currency: EUR in the EU, USD everywhere else. We do not request precise location or send your time zone to a geolocation service. The resulting region is sent when you submit checkout. A region choice saved by an earlier version under cyberpigeon-billing-region in local storage is deleted when you open Pricing or the console. Your chosen light or dark color theme is saved on this device under cyberpigeon-theme in first-party local storage. Choosing “Use device setting” removes that saved preference. The preference is not sent to the server and is not used for tracking. Downloaded keys, recovery codes or data exports remain under your control on your device. The site makes no advertising pixel or third-party font requests.
Analytics, with your consent
When product analytics is enabled, we ask once, on the first page you open, and your answer applies to the whole site: guides, the API reference, the console and the app connection screen. The API reference and the app connection screen do not ask themselves; they wait for an answer given elsewhere. Your answer is saved in cyberpigeon_consent, a first-party cookie (1 for accept, 0 for reject) that lasts twelve months from your answer and is needed to remember the choice. A second cookie, cyberpigeon_consent_until, records when it expires, so signing out of the console never extends it. Until you choose, nothing is sent to analytics.
If you accept, PostHog sets a first-party cookie named ph_ followed by our project token and _posthog, with matching local and session storage entries beginning with ph_. They hold a random visitor ID, a session ID and analytics settings for up to a year. PostHog then records page views, clicks, page performance, browser errors and session replays in which all text and form inputs are masked and images are not captured. When you are signed in, the visitor ID is linked to your workspace.
If you reject, no analytics cookie or storage entry is set, and any left from an earlier acceptance is removed (in another open tab, on its next page). Only visits are counted (page views and page exits), without cookies, using a privacy-preserving hash that PostHog rotates daily; clicks, performance, errors and replays are not recorded. If your browser sends Global Privacy Control or Do Not Track and you have not chosen, no browser analytics run at all.
Requests go to /ingest on this website, which forwards them to PostHog’s EU Cloud (servers in Frankfurt). Change your answer at any time with Privacy choices in the site footer, the console account menu, or here:
Signed-in actions, such as creating an agent, sending through the API or changing your plan, are reported from our server whatever the cookie choice, without cookies; the privacy notice explains this processing and how to object.
External services
Links to documentation, email providers or attachment downloads open external services with their own privacy and cookie practices. Remote images, scripts, forms and clickable links are removed from email HTML previews. This preview is simplified for privacy; it may differ from the original email.
Questions: see the operator and contact details in our privacy notice.