LEGAL · COOKIES
Cookie and Browser Storage Policy
Effective 15 November 2026
1. What this notice covers
Cookies store small pieces of information in your browser. OperatorRank uses cookies for sign-in, authentication security, fraud prevention, referral attribution and your theme preference. It also uses browser storage for preferences and recovery of interface state. The main production cookie and storage families are described below; cookies set by Google, GitHub or Cloudflare on their own services follow their own policies.
2. Cookie and browser-storage inventory
| Cookie or storage | Purpose | Browser duration |
|---|---|---|
| __Host-operatorrank_session | Sign-in session | Idle window up to 30 days, refreshed on use within an absolute session limit of 90 days; may end earlier on revocation |
| __Host-operatorrank_session_present | Lets the interface detect session presence; not itself a sign-in credential | Same issued lifetime as the session cookie |
| __Host-operatorrank_auth_google / __Host-operatorrank_auth_github | Binds the sign-in redirect to the browser | Short-lived, until the authentication transaction’s expiry; cleared on completion or failure |
| __Host-or_provider_admission | Completes account registration after provider sign-in, including age attestation and acceptance of Terms | Up to 30 minutes; cleared on successful admission |
| __Host-operatorrank_password_bootstrap | Binds the human-verification challenge | 5 minutes |
| __Host-operatorrank_password_preauth | Carries the completed pre-authentication gate | 15 minutes |
| __Host-operatorrank_password_mailbox | Carries email-link verification to the password form | 15 minutes |
__Host-operatorrank_handoff_start_<scope> / __Host-operatorrank_handoff_state_<scope> |
Binds the Accounts-to-App handoff to the browser | Up to 60 seconds; cleared when consumed or ended |
| __Host-operatorrank_device | First-party device identifier for security and abuse prevention | Up to 365 days; this is distinct from the 12-calendar-month security-event record schedule |
| operatorrank_referral | Referral attribution during the browser session | Session cookie, without a fixed Max-Age; browser session-restore behavior may preserve it |
| operatorrank_theme | Remembers light/dark theme | Up to 365 days |
| operatorrank.analytics.consent.v1 in first-party local storage | Necessary record of analytics choice, purpose, policy revision, time and source; saved even for Necessary only | Choice valid for up to 180 days; the stored record may remain until replaced or cleared; no account ID |
| _ga (only when GA4 is configured and you consent) | Distinguishes analytics visitors using a random identifier | Google default: 2 years; actual browser/site settings can shorten or renew it; cleared on withdrawal |
_ga_<container-id> (only when GA4 is configured and you consent) |
Maintains analytics session state | Google default: 2 years; actual browser/site settings can shorten or renew it; cleared on withdrawal |
| operatorrank.ui.locale in local storage | Remembers your language choice | Until changed or browser storage is cleared |
operatorrank.p4.local-draft.v1:*, including :recovery:* and logout-epoch suffixes |
Unsaved workspace text and recovery snapshots bound to account/attempt | Recovery validity up to 24 hours; supported stale records are removed when checked, not by an unconditional storage timer |
operatorrank:company-new:locale:<identity> with epoch suffix |
Unsaved organisation forms across language changes or reauthentication; session storage | Normal language handoff 10 minutes; reauthentication recovery up to 24 hours; cleared on use or supported authoring cleanup |
operatorrank.draft-owner.v1 / operatorrank.draft-logout-epoch.v1 |
Account ID and logout-generation fence in local storage | No timed expiry; cleared, replaced or fenced by supported sign-out/account changes |
operatorrank.approval-mode.v1:<scope> |
Workspace approval preference | Until changed or cleared |
operatorrank.signin-return.v1 |
Tab-local return destination after sign-in | Valid for 30 minutes, consumed on return |
operatorrank.join-token |
Tab-local continuation of a class/group join | No independent expiry clock in this storage; removed by supported cleanup |
operatorrank:deletion-intent:<accountId> |
Tab-local identity for an idempotent deletion request | Tab-local storage, not proof that deletion finished or Terms were accepted |
operatorrank.last-submitted-attempt.v1 |
Account/attempt/logout-epoch pointer to a submitted result | Local storage with no timed expiry in its reader |
operatorrank.credit-return.<locale> |
Tab-local account-bound return destination | Valid for 30 minutes |
operatorrank.ui.table.<id>.columns |
Table-column preference | Until reset or site data is cleared |
operatorrank.ui-preview.company.compare-tray.v3.<account>.<org> |
Selected person IDs for company comparison, scoped to account/organisation | Cleared on scope switch; no timed expiry; used by the live product despite the name |
operatorrank.ui-preview.company-review-list |
Tab-local review-navigation list | Session storage |
operatorrank.ops.pages.<scope> |
Staff tab-local page cursors | Session storage |
operatorrank.ops.approval-roll.v1 |
Staff local proposal handoff references/digests, not an authority or credential | Valid for 15 minutes; validity is not a physical-deletion timer |
Browser recovery storage can contain unsaved workspace text or organisation forms and account/attempt identifiers. operatorrank.p4.local-draft.v1:* and organisation locale drafts support recovery for up to 24 hours; account-binding records and other preferences may remain until cleared or replaced. Signing out or changing accounts clears or fences supported private records, but cannot erase downloads or all other tabs. Clear site data on a shared device.
Browser expiry does not immediately delete server authentication records. Eligible completed or expired authentication material is cleaned up after its 7-day grace period; expired/revoked session records have a 30-day grace period. Unresolved work, dependencies and lawful holds may require longer retention.
3. Your optional analytics choice
Where Google Analytics 4 (GA4) is configured, Accept all enables optional analytics; Necessary only is equally accessible and keeps GA4 off. We use basic consent mode: before analytics consent there is no Google tag load, GA4 request or cookieless ping. Advertising storage/user data/personalization stay denied and Google signals remain off. Cookie settings lets you withdraw on the current page, stop future GA4 collection and clear this site’s GA4 cookies. The GA4 property retention period shown there is separate from cookie lifetime and does not govern all aggregate reports. We send only the restricted analytics categories in the Privacy Policy. Google’s GA4 cookie documentation describes the default cookie durations.
We use your saved choice for up to 180 days and ask again after expiry or a policy revision change. The browser record can remain until you replace it or clear site data; expiry does not itself delete the record. The record is specific to this browser/site; a different host, browser, private window or cleared storage can need a new choice. If storage cannot be saved, the choice applies only on that page. With no valid analytics configuration the controller is inactive and no GA4 request is sent. Necessary only is not a refusal of the service. Withdrawal does not delete Google’s earlier lawful records; ask support about a supported data request.
The current helper sends public page views with only the limited fields described in the Privacy Notice. It does not send workspace content, Defense, individual results or account IDs. The production configuration displays a 2-month GA4 user/event retention setting, unless another valid setting is configured; the actual Google property must match. That is separate from the default 2-year analytics cookie lifetime and from aggregate reports.
4. Necessary, preference and third-party processing
Sign-in, authentication binding, device/security and choice records support the requested service and its protection. Referral attribution and theme/locale storage serve the specific attribution or preference purpose; they are not permission to track you across unrelated sites. Depending on applicable law, these purposes rely on the relevant contract, legitimate interests or the choice you make, rather than optional GA4 consent. The device identifier/fingerprint is a security signal, not anonymous analytics or proof of cheating. You may object or ask for review through the privacy channel; we will explain an applicable lawful reason to retain it.
The free beta has no active payment provider. If paid plans launch later, that provider and any payment-related cookie or storage use will be disclosed before the relevant checkout is enabled; these clauses do not assert that payment cookies exist today.
Your GA4 choice controls GA4 only. Sign-in security processing, the device security identifier and Turnstile can operate before that choice. Where enabled by our edge configuration, Cloudflare Web Analytics on authentication pages also operates separately from the GA4 choice. We use these for the security or performance purposes described here; their applicable basis and retention are separate.
Cloudflare Turnstile helps prevent bots and processes browser/security signals under its Privacy Addendum. Cloudflare Web Analytics is supported on authentication documents to measure page performance; Cloudflare describes that analytics product as cookie-free. Cookie-free analytics does not mean the site has no analytics or network processing. See Cloudflare Web Analytics and our Privacy Policy for security records and service providers.
5. Browser controls and contact
You can delete or block cookies and clear local/session storage in your browser’s site-data settings. Blocking essential sign-in or security storage can stop sign-in and related features from working. Clearing a device cookie does not delete existing server-side security records; use the privacy-request process for those records. Preference storage follows the choice you make in the interface. If we introduce optional advertising or tracking cookies requiring consent, we will ask before setting them. For questions or a storage-related objection, contact support@operatorrank.com.
This notice supplements the Privacy Notice. The operator and privacy contact are identified there; storage questions can be sent to support@operatorrank.com. Changes are published with a new revision and applicable effective date. A new optional purpose requiring consent needs a separate valid choice; changing a notice alone does not authorise it.
Contact us
For questions, personal-data requests or to report a problem, email support at support@operatorrank.com