In short
- None of them sets advertising cookies or third-party cookies.
- The website stores the Orbit Pixel's visitor ID and little else, the app stores what keeps you signed in, and on our customers' websites the pixel keeps its visitor ID on their own domain.
- A website can have the pixel's visitor ID wait for consent: until the visitor says yes, it stores nothing in the browser and counts the visit without it.
This policy lists what goorbit.io, the Orbit app and the Orbit Pixel store in your browser, and why. None of them sets advertising cookies or third-party cookies.
You can see and delete what a website stores in your browser's settings. Deleting the app's storage signs you out.
goorbit.io
The website measures its own visits with the Orbit Pixel, which stores the visitor ID and the visit described under The Orbit Pixel, below. It sets no advertising cookies.
| Name | Type | How long | What it does |
|---|---|---|---|
| orbit:announcement-closed | Session storage | Until you close the tab | Remembers that you closed the announcement bar |
| orbit:ask | Session storage | Until you close the tab | Keeps your Ask Orbit conversation as you move between pages |
| orbit_access | Cookie | 30 days | Only while the website is in preview: lets invited people past the preview page |
| __prerender_bypass | Cookie | Until you close the browser | Only for our editors: shows changes that are not published yet |
A film on the website plays in Mux's player, which loads only when you press play and sets no cookies.
The Orbit app
The app at app.goorbit.io stores what keeps you signed in, remembers your settings, and groups your use of the app into sessions for the usage data described in the Privacy Policy.
| Name | Type | How long | What it does |
|---|---|---|---|
| sb-…-auth-token | Local storage | Until you sign out | Keeps you signed in |
| orbit_signed_in | Cookie | 30 days after you last opened the app, or until you sign out | Tells goorbit.io that you are signed in, so the website's header shows Open app; holds no account details |
| sidebar:state | Cookie | 7 days | Remembers whether the sidebar is open |
| Interface settings (theme, the site you had open, sidebar, sort and view choices) | Local storage | Until you clear it | Remembers your settings |
| orbit-session-id, orbit-session-last | Session storage | Until you close the tab; a new session starts after 30 minutes without activity | Groups your use of the app into sessions |
| Other view state (open tabs and panels) | Session storage | Until you close the tab | Remembers what you were looking at |
The app loads its font and site icons from Google, and the photos its image picker suggests from Unsplash. When they load, your browser sends your IP address and browser details to them.
The Orbit Pixel, on goorbit.io and our customers' websites
goorbit.io measures its own visits with the Orbit Pixel. Customers can add it to their own websites too; on those websites, the customer decides whether the pixel runs and how it asks for consent, and is responsible for informing visitors and asking for their consent where that is required.
The pixel stores data only on the website's own domain:
| Name | Type | How long | What it does |
|---|---|---|---|
| _orbit_v | Cookie and local storage | Cookie: 365 days from the last visit. Local storage: until you clear it | A random visitor ID, to recognise a return visit |
| _orbit_visit | Local storage and session storage | Until you clear it; a visit ends after 30 minutes without activity | The current visit |
| _orbit_s | Local storage | Until you clear it | A copy of the current visit, which a shop's order tracking reads |
| _orbit_t | Cookie | Removed straight away | Finds the domain the cookie can be set on |
| _orbit_off | Local storage | Until you clear it | Only if you opted out of being counted: tells the pixel to send nothing |
The pixel sets no third-party cookies, does not store IP addresses, and never records what is typed into forms. Where a browser blocks storage, it uses a visitor ID that changes every day instead, made with a secret key from the IP address and browser details, which are not stored.
When a website asks for consent
A website can have the pixel's visitor ID wait for consent. Until the visitor says yes to statistics in the website's cookie banner, which tells the pixel through Google Consent Mode or from the website's own code, the pixel reads and stores nothing in the browser and counts the visit with a visitor ID that changes every day, as it does where a browser blocks storage. A yes stores the visitor ID, so a return visit is recognised. A no, or a yes taken back later, removes the visitor ID and the current visit from the browser, and counting goes on without them. Without that setting, the pixel stores its visitor ID from the first page. A website can also offer a link to opt out of being counted at all: the pixel then keeps only the note that you opted out, and sends nothing more from that browser.
