Orbiton

Cookie & Browser Storage Policy

What the Orbiton investor relations chat stores in your browser, what each item is for, how long it is kept, and the consent required for each.

Effective date
November 13, 2026

Orbiton Financial, Inc. ("Orbiton", "we", "us") provides an AI-powered investor relations chat that public companies embed on their own websites, plus chat pages on our own domain. This page explains, in plain language, everything the chat and our own pages can store in your browser, what each item is for, how long it lasts, and what consent is required before it appears. It supplements our Privacy Policy.

First, what we do not do

  • The chat sets no HTTP cookies. It uses browser storage (localStorage and sessionStorage) only. EU ePrivacy rules treat browser storage the same as cookies, so we apply the same consent standards to it. The only cookies on our own pages are the sign-in cookies listed below, set if you sign in to an Orbiton account.
  • No advertising or cross-site tracking. There are no advertising cookies, no data sale, and no tracking of you across unrelated websites. Identifiers below are scoped to the specific company site and chat you use. The advertising tag on our own homepage is described below; it stores nothing.

Consent tiers

Storage is gated by a three-tier consent model. The chat itself works at every tier: consent controls what is stored, not whether you can use the chat.

  • Tier 0, Minimal: no consent given. Nothing is stored; any state lives in page memory and disappears when you leave.
  • Tier 1, Session: you engage with the chat. Session-scoped items only (cleared when the browser tab session ends); your conversation works, but no persistent identifier and no analytics.
  • Tier 2, Full: you explicitly consent (pre-chat card, the site's cookie banner, or its consent management platform). A persistent identifier enables cross-visit chat history and first-party analytics for the company whose site you are visiting.

Storage on the company's website (the embedded widget)

These keys can be set by the chat widget on the investor-relations site you are visiting:

Key Type Purpose Duration Appears at
profileIdentifier localStorage Random anonymous visitor identifier. Links your page visits and chat history for the company whose site you are on; contains no personal details itself. Until consent is withdrawn or you erase your data Tier 2
orbiton_consent_<company> localStorage Your consent decision itself: tier, policy version, timestamp, and how it was given. Written only when you make an explicit choice. Until changed or withdrawn Any explicit decision
orbiton_tc_consent_<company> localStorage Legacy terms-banner decision from older embeds; migrated into orbiton_consent_* on first read. Until migrated or withdrawn Explicit banner decision (legacy)
orbiton_prechat_<company> sessionStorage Receipt that you accepted the pre-chat consent card, so the card is not shown again during the same browsing session. Browser session Card accept
orb_session_id, orb_last_activity_ms sessionStorage Groups your page views into one visit for the company's analytics (a new session starts after 30 minutes of inactivity). Browser session Tier 1+
hasExistingChats localStorage / sessionStorage A yes/no flag ("true") so the widget can offer to continue an earlier conversation. Stored persistently only at tier 2; session-only at tier 1; page memory below that. Follows its tier (persistent / session / none) Tier-routed
orbiton_chat_dismissed localStorage / sessionStorage Remembers that you closed the chat, so it does not automatically reopen. Tier-routed like the flag above. Follows its tier Tier-routed
orbiton_panel_geometry localStorage / sessionStorage If you move or resize the chat window on a desktop, where you left it and its size, so it opens there again on the next page. A position and a size only, nothing about you. Removed when you put the chat back on the right edge. Tier-routed like the flags above. Follows its tier Tier-routed
orbiton_lang sessionStorage / localStorage The language you chose in the chat (a two letter code such as "fr"), so the chat button and the next chat window use it too. It identifies no one. Where the site uses the consent tiers it is tier-routed like the flags above; on any other site it is kept for the browser session only. Browser session; persistent only at Tier 2 Choosing a language (tier-routed where the site uses the tiers)
__orbiton_storage_test__ localStorage Technical availability probe: written and immediately removed to detect blocked storage. Never holds data. Milliseconds Always (stores nothing)

Storage inside the chat window (chat.orbiton.app)

The chat itself runs in a frame on our domain. Browsers keep its storage separate from the host site's:

Key Type Purpose Duration Appears at
profileIdentifier localStorage The chat's copy of your anonymous visitor identifier, so your conversation history can be retrieved on later visits. It is only used at tier 2. Until withdrawn or erased Tier 2
profileIdentifier_<company> localStorage A copy of the same anonymous visitor identifier for each company's chat, which the chat reads first, so that one company's chat never uses another company's identifier. It is only used at tier 2. Until withdrawn or erased Tier 2
chatHistoryLinks localStorage The anonymous visitor identifier of a company's chat when you sign in from it, kept until your account is linked to that chat's history. Until linked or erased Signing in from the chat
chatId_<company> localStorage The id of your current conversation, so a page reload resumes the same thread instead of starting over. Until you start a new chat or erase data Using the chat
analyticsConsent_<company> localStorage Your answer to the in-chat analytics consent prompt ("granted"/"denied"), so you are not asked twice. Until changed or erased Explicit prompt answer
preferredLanguage localStorage The language you chose in the chat's language menu (a two letter code such as "fr"), so the chat keeps showing it on later visits. Written only when you choose a language; it identifies no one. Until you choose another language or clear your browser data Choosing a language
userEmail localStorage Stored only if you type your email into the chat (e.g. to receive a transcript or company updates, or to request a meeting). Never collected automatically. Until you erase your data Explicit submission

Our own pages: the homepage, setup pages and sign-in

These apply on Orbiton's own pages (the homepage and the pages a company uses to set up its chat), not in a company's widget:

KeyTypePurposeDurationAppears at
orbiton_ws_visitor localStorage Random anonymous identifier for this browser, used for our own first-party usage analytics of the setup pages: which steps of setting up a company's chat were reached. It carries no name, email or chat text. These events are also passed from our servers to our analytics provider, PostHog. Until you clear your browser data Visiting a setup page
orbiton_ws_session sessionStorage Groups those analytics events into one visit for the tab you have open. Browser session Visiting a setup page
__Secure-orbiton_access Cookie (.orbiton.app) Keeps you signed in to your Orbiton account on Orbiton's sites. Not readable by page scripts. Short-lived; renewed while you stay signed in, removed when you sign out Signing in
orbiton_session_expires Cookie (.orbiton.app) The time your sign-in expires, so a page can renew it in time. It holds a time only, nothing secret. Up to 30 days, or until you sign out Signing in
__Host-orbiton_refresh Cookie (auth.orbiton.app) Renews your sign-in between visits, so you are not asked for your password each time. Not readable by page scripts. Up to 30 days, or until you sign out Signing in
__Host-orbiton_oauth Cookie (auth.orbiton.app) Holds the state of a sign-in with Google or Microsoft while you complete it, so the answer can be matched to your browser. 10 minutes Starting a Google or Microsoft sign-in

The sign-in cookies are strictly necessary for an account you chose to sign in to, so they do not depend on the consent tiers. Signing in is never needed to use a company's chat.

Google's advertising tag on our homepage

Our homepage loads Google's advertising tag so we can count whether our own advertisements lead to visits and questions. We run it with every consent setting denied and never switch them on, and with Google's advertising data redaction turned on: it sets no cookies and reads none, and what Google receives are cookieless signals without advertising identifiers. If you arrive from one of our advertisements, the click identifier in the address is passed along so that the visit can be attributed to the advertisement. The tag is not loaded in a company's chat widget or on a company's website.

Third-party scheduler embeds (Calendly / cal.com)

Some companies let you book a meeting with their team directly inside the chat. When that option is enabled and you click "Load scheduler", the chat loads a scheduling widget from Calendly or cal.com in its own frame. That widget is operated by the third party and may set its own cookies under its own policy. See the Calendly cookie notice and the cal.com privacy policy. Before you click, no request is made to either provider: the scheduler is never loaded automatically, so simply opening or using the chat sends nothing to Calendly or cal.com.

Withdrawing consent and erasing data

  • Through the site's cookie tool: if the company's website runs a consent banner or CMP, rejecting or withdrawing analytics consent there tears down our storage automatically: the persistent identifier and every Orbiton key above are erased from the site, and tracking stops immediately. The chat stays available.
  • Through the chat: the chat's data controls let you withdraw consent and request deletion of your stored conversations, analytics, and contact details from our servers. Deletion requests are honored without needing an account.
  • Manually: clearing your browser's site data for the company's website and for chat.orbiton.app removes every key listed here; signing out removes the sign-in cookies.

Each consent grant and withdrawal is also recorded server-side (decision, policy version, timestamp) as an audit trail, as described in our Privacy Policy, which also covers retention periods for server-side data such as conversations and analytics.

Changes to this page

When we add, rename, or re-scope a storage key, we update this page and its effective date. Material changes to what consent covers are versioned: your stored decision records the policy version it was given under.

Contact

Questions about cookies can be sent to Orbiton Financial, Inc., 401-353 Water St, Vancouver, BC, Canada; 1250-100 Pine St, San Francisco, CA, United States; daniel@orbiton.app.