Skip to content
All legal documents

DRAFT — NOT LEGAL ADVICEThis page is a template that has not been reviewed by a lawyer. The operator remains responsible for its content.

Cookie Notice

Console (app.<platform domain>)

  • sid - keeps you signed in (random session token; only its hash is stored server-side). Strictly necessary, HttpOnly, first party. Lifetime 30 days, sliding, at most 90 days from sign-in.
  • ob_csrf - security token derived from your session; the console reads it and sends it back with every change to prove the request came from the console (cross-site request forgery protection). Strictly necessary, first party, SameSite=Strict, same lifetime as sid. Contains no personal data.
  • ob-console-try-draft (browser storage, not a cookie) - only if you use the editor at /new before signing in: the terminal name, web address, template, colors, markets and fee you chose, so they survive a reload. It stays in your browser and is sent to the platform only when you sign in and create the terminal, after which it is deleted. Use "Clear this draft" in the editor, or clear the site's data in your browser, to remove it sooner. Not used for tracking.
  • Reload guard (browser session storage, not a cookie) - after a new console version is released, a page that fails to load an updated file reloads itself once; a single timestamp is kept for the length of the tab so this can happen at most once a minute and never loops. Strictly necessary, never sent anywhere, not used for tracking.
  • ob_via - only if you arrived through a platform referral link (an address ending in ?via=<code>): the referral code, nothing else. First party, SameSite=Lax, 60 days, never overwritten by a later link. It is read once, when you create a terminal, so the platform can credit the person who referred you (they earn a share of what you pay the platform for 12 months; your price does not change). It is not used for advertising, analytics or to follow you on other sites. Delete it by clearing the site's cookies.

No analytics, advertising or third-party cookies. No third-party scripts are loaded. sid and ob_csrf are strictly necessary; ob_via exists only after you followed a referral link and does nothing but credit the referrer, so no consent banner is shown.

Tenant sites

Tenant sites set no cookies for visitors. The only exception is an operator previewing an unpublished draft: a short-lived (up to 15 minutes), signed, HttpOnly preview cookie is set on the tenant host, and only when the operator opens a preview link issued from the console.

The trading interface stores settings on the visitor's device in browser storage (not cookies). This stays on the device and is not sent to the platform, with one exception: a random id for the current browser tab (ob.funnel.sid, session storage, gone when the tab closes) is sent with anonymous counts of visit steps (visited, accepted terms, connected, enabled trading, funded, traded) so that one visit is counted once. The platform never stores this id, and it is not linked to a wallet or an IP address. Error reports and page-speed numbers are sent without any id.

Optional marketing measurement (only where the operator turns it on, and only with the visitor's consent). An operator on a paid plan may add Google Analytics, a Meta Pixel and/or a TikTok Pixel to its site. Nothing from these vendors is loaded and none of their cookies is set until the visitor clicks "Accept" in the cookie banner; "Decline" loads nothing. The choice itself is kept in browser storage on the device (ob.consent.v1, strictly necessary to remember the answer, never sent anywhere) and can be changed at any time with "Cookie settings" in the site footer. After acceptance the vendor sets its own cookies (for example _ga, _fbp, _ttp) under its own terms; the operator describes them in its privacy notice.

Optional chat widget. If the operator turned on Crisp or Intercom, the vendor's script loads only when the visitor clicks "Chat with us"; the vendor may then set its own cookies to keep the conversation.

This inventory is enforced by an automated test (consent-inventory.test.ts) that fails when new cookie, storage or third-party script usage appears in the console or the edge.

Looking for a different document? See the full list