Two analytics tools sit behind a single switch: a session-recording tool and cookieless page counts. Analytics ships on by arrival with an off switch in Settings — an opt-out posture, not ask-first consent. A browser broadcasting Global Privacy Control is treated as a refusal, with no banner and no override.
Two tools, one switch
One tool records sessions and sets first-party cookies. The other counts page views without cookies at all, deriving a short-lived identity from request properties and discarding it within a day.
The cookieless one is deliberately held to the same consent predicate as the other, even though it could arguably run without consent. Two privacy switches that mean subtly different things is a design that guarantees somebody is eventually surprised.
The shipped mode, stated plainly
Analytics is on when you arrive, and switched off in Settings. That is an opt-out posture. It is recorded in configuration as a deliberate, reversible operator decision rather than being presented as consent.
This documentation does not describe it as ask-first, because it is not. A product that claimed ask-first consent while shipping opt-out would be making exactly the kind of privacy claim that is worth nothing and costs everything when discovered.
The two hard overrides
A browser broadcasting Global Privacy Control is treated as denied. It outranks any stored grant, the banner is never shown, and there is no interface path to override it. GPC is a valid opt-out signal under some privacy regimes and is committed to in the privacy policy, so it is honoured as a refusal rather than as a preference.
A stored refusal also survives any change to the default. If the shipped posture were ever flipped, someone who had already said no stays no — a default change must never be able to re-consent a person who declined.
Withdrawing consent removes the recording tool's cookies rather than merely stopping new collection.
The desk is masked
The entire authenticated desk carries a masking attribute, so session analytics cannot capture what is on it: your symbols, your positions, your account size, your journal.
The reasoning is that consent to analytics is not consent to have your trading record recorded. Those are different things, and the mask is what keeps them different.
Frequently asked
- Does ORIN ask for analytics consent before recording?
- No. The shipped mode is on-by-arrival with an off switch in Settings — an opt-out posture recorded as a deliberate operator decision. The exception is a browser broadcasting Global Privacy Control, which is treated as a refusal before any default applies.
- Can session analytics see my trades and account size?
- No. The entire authenticated desk carries a masking attribute, so the recording tool cannot capture it. Consent to analytics is not consent to have your trading record recorded, and the mask is what keeps those separate.
Updated Sep 1, 2026