Cookie Notice
Effective date: 4 November 2026
This notice explains the cookies and similar browser storage Orbit Insight actually uses. Cookies and storage that keep the website and the app working are essential and always on. Analytics (to study how the website and the app are used) and Advertising (to measure our own ads and to tell advertising platforms what they led to) are separate, and you choose them with our cookie banner. They are described under "Analytics and advertising measurement (Google and Meta)" and "Measuring our own advertising".
On this website
Browsing this website does not set any cookies of ours by itself. Our cookies are set when you make a choice and, once you have allowed Advertising, when you arrive on an address that carries campaign tags or a click ID. Google's tags and Meta's tag set their cookies only once you allow the matching permission. If you pick English or Türkçe with the language switch in the footer, we set the language cookie described under "When you use the app", which lasts one year. If you answer our cookie banner, we set the choice cookie described under "Measuring our own advertising".
Pages with a form that needs protection from bots (the waitlist form, and the sign-up, sign-in and password forms) load Cloudflare Turnstile, which tells real visitors apart from automated bots. Turnstile is run by Cloudflare. It stores data in your browser's local storage and may also use cookies, set from Cloudflare's own domain rather than ours. We don't use it to track you or to build a profile of you.
This website also keeps copies of its own static files (such as scripts, styles and fonts) in your browser's cache, using a service worker, so pages load faster. These copies contain no personal data, and you can clear them from your browser's site settings.
When you use the app
Once you sign in and use the Service, we set these cookies:
- Session cookie: set when you sign in, so the Service knows you're logged in on later page loads. Without it, you'd have to sign in on every page.
- Temporary sign-in cookies: set for a few minutes while you complete a sign-in step, such as signing in with Google or entering a two-factor code, so we can finish that step securely. They expire within minutes.
- Shopify connection cookies: set for up to 30 minutes when you connect a Shopify store or choose a plan, so the connection can be completed securely and you pick up where you left off.
- Language cookie: set if you choose a language, in the app or with the language switch in the footer of this website, so the Service remembers it. It lasts one year.
Display settings, such as table density and whether the sidebar is collapsed, are saved in your browser's local storage. They stay on your device.
Each of these is needed for the Service to work, to keep it secure, or to remember a choice you made, so we don't ask you to opt in to them. Analytics and ad measurement are different: they are off until you allow them on our cookie banner.
Analytics and advertising measurement (Google and Meta)
Our public pages and the sign-in, sign-up and forgot-password pages load Google Tag Manager, a tool run by Google that loads the measurement tags we set up in it. We deliberately load nothing from Google on the page where you set a new password, or on a sign-in link that carries a store or an invitation, because those addresses can hold private details. The signed-in app does not use Tag Manager. It uses Google Analytics, loaded directly, in a separate Google Analytics account used only to see how the app is used, and it loads no advertising tag.
Your cookie banner choice decides what is allowed. Accept all allows Analytics and Advertising. Reject non-essential allows neither. Customise lets you allow one without the other. In Customise, both choices start ticked: untick the one you do not want before you press Save choices. In the app, Google Analytics runs only if you have allowed Analytics on our public pages or sign-in pages.
- Analytics cookies (allowed by Analytics): _ga and _ga_ followed by an ID, set by Google Analytics to tell visits apart. Google sets how long they last, and we do not extend it.
- Advertising cookies (allowed by Advertising): _gcl_au, _gcl_aw and _gac_ followed by an ID, set by Google's advertising tags so that Google can tell whether one of our Google ads led to a signup or payment.
- Meta advertising cookies (allowed by Advertising): _fbp and _fbc, set by Meta's tag so that Meta can tell whether one of our Meta ads led to a signup or payment. Each lasts up to 90 days, and _fbc is only set when you arrive from a Meta ad.
Advertising also lets us use Google signals and audiences. If you are signed in to a Google account with personalised ads on, Google may link your visit to that account, and we may use that to show you our ads elsewhere (remarketing). Google's own tag on our pages can also receive a scrambled version of your email address when you join the waitlist, or of your email address, phone number and name when you sign up, if you allowed Advertising. The Privacy Policy explains this in section 2C, and you can switch personalised ads off in your Google account's ad settings.
Advertising also lets us tell the advertising platforms we use, such as Google and Meta, when you join the waitlist, sign up, verify your account, start a trial or pay after a visit that carried ad tags or a click ID. We send scrambled contact details and, if the visit came from a Google ad, its click identifier (gclid, or the gbraid or wbraid identifier that Google adds to some ad clicks). We send the scrambled details even if the visit did not come from a Google ad, so that Google can match them to its own accounts. We also send Google and Meta the IP address and browser type we stored with your ad click or your signup request, as they are. The ad click we mean is the newest one recorded in a browser linked to the step: for an organisation's trial start or first payment that can be another owner's click, and on a browser that several people use it can be another person's. With a trial start or a first payment we also send an address that we read from Stripe, our payment provider, and do not store: to Google its country and postal code as they are, together with your first and last name in scrambled form (all four together, or none of them), and to Meta its country, postal code, city and state in scrambled form, as far as Stripe holds them. The Privacy Policy explains what we send in section 2D.
If you allow Advertising, we also use Meta's tools on our public pages and sign-in pages to see whether our own Meta ads led to a waitlist signup, an account or a payment, and to show you our ads on Meta's services. Meta's tag runs in your browser and tells Meta which pages you look at and when you join the waitlist or sign up. It sends your email address in a scrambled form when you join the waitlist, and your email address, phone number and name in a scrambled form when you sign up. Meta's automatic matching is switched on, so the tag also sends the email address, phone number or name you type into any other form on our pages, such as the sign-in form, in the same scrambled form. If you allowed Advertising, the page views and signup steps that Google's tags measure on our pages are also passed on to Meta from our own address, gtm.orbitignition.com. The waitlist signup and later steps (your account's email being verified, your trial starting, your first payment) are sent by our server, with the same scrambled details, the IP address and browser type we stored with your ad click or, if you joined the waitlist or signed up, with that request, and the two Meta cookies below. With a trial start or a first payment, our server also sends the country, postal code, city and state of your payment address in scrambled form, as far as our payment provider, Stripe, holds them. We read them from Stripe when we send and do not store them. Our server sends these steps through our own address, gtm.orbitignition.com, a server that Google hosts for us, and Meta receives them from there. As with any request to a website, your IP address and browser type also reach Meta from your browser. If you do not allow Advertising, no Meta tool loads and nothing is sent to Meta. Take back your permission with "Cookie settings" in the footer of our public pages; that also deletes the two Meta cookies.
Before you answer, and after you choose Reject non-essential, Google's tags still load on the pages where we use Tag Manager, in a limited mode that Google calls Advanced Consent Mode. In that mode they do not use cookies, but Google still receives limited information about your visit: the time, your browser type, the page you came from, the address of the page, whether that address carried an ad click ID, your cookie choice and a random number. As with any request to a website, your IP address also reaches Google's servers. Google uses this to estimate results it cannot see. If you do not want even this, block Google's domains in your browser. The measurements from Google's tags on our public pages pass through our own address, gtm.orbitignition.com, a server that Google hosts for us, on their way to Google and, if you allowed Advertising, to Meta.
The cookie names above are the ones we know today. The list follows the tags set up in Tag Manager, and we update this notice when it changes. If you take a permission back with "Cookie settings" in the footer, we delete the matching Google and Meta cookies from your browser, and Google's tags and Meta's tag stop reading and writing them. The app reads your choice on every page, so its Analytics stops from the next page.
Measuring our own advertising
When you arrive from one of our ads, the address often carries tags we add (such as utm_source and utm_campaign) and a click ID that the ad platform adds (for example gclid from Google, fbclid from Meta or ttclid from TikTok). We ask you first, with a banner whose Accept all, Reject non-essential and Customise buttons are equally prominent. The banner appears on our public pages and on the sign-in, sign-up and password pages, not inside the app. We record these tags and click IDs only if you allow Advertising (Accept all, or Customise with Advertising ticked), and only to measure and improve our own advertising. If you reject non-essential cookies, allow only Analytics, or do not answer, no campaign tags or click IDs are recorded and we set no visitor cookie. The tags are read at the moment you allow Advertising and, once you have allowed it, when you arrive on an address that carries campaign tags or a click ID on one of those pages. If you move to another page before you answer, they are no longer in the address and no campaign tags or click IDs are recorded.
Both cookies below are ours, set by our own website and server and never by an advertising platform, and your browser may remove them sooner than their stated lifetime.
- Choice cookie (oi_consent): remembers your choice (everything, nothing, Analytics only or Advertising only), so we do not ask again. It is set when you make the choice and lasts up to 12 months. We ask again if what we ask you to agree to changes.
- Visitor cookie (oi_vid): a random ID that lets us connect your visit to a waitlist signup or an account if you later sign up. It is set only after you have allowed Advertising, on a visit that carries ad tags or a click ID, and lasts up to 12 months.
A visit without ad tags or a click ID records nothing. For each visit that carries them we record the time, the page you landed on (its address without the tags), the name of the website you came from, the ad tags and click IDs, the advertising platform we work out from them, the version of the banner you answered, and your random visitor ID. We also record your IP address and browser type (the "user agent", which can also show your device and operating system), encrypted, so that they are available to help match a later step to your visit. That includes sending them to Google and to Meta, as described above. If you later join the waitlist or sign up in this browser, we keep your IP address and browser type again, encrypted, on the record that links your visit to your signup, so that a later step can still be matched. We do not record any browser fingerprint in these records. We store the click IDs of Google, Meta, TikTok, Microsoft, X, LinkedIn, Pinterest and Snap if they appear in the address, including for platforms we do not advertise on yet.
These detailed records, and the record that links your visit to your waitlist signup or account, are deleted after 12 months. If you join the waitlist or create an account, we also keep a short summary (the first and the last campaign that brought you) for as long as that signup or account exists.
You can change your mind at any time with "Cookie settings" in the footer of our public pages. Taking Advertising away there (Reject non-essential, or Analytics only) stops the recording, removes the visitor cookie, deletes the records linked to it and clears the campaign details copied onto your waitlist or account records. Our Privacy Policy (section 2B) explains why we do this, the legal basis and your rights.
Managing cookies
You can block or delete cookies and local storage through your browser's settings. Because the session cookie is required for signing in to work, blocking it will prevent you from using the Service while signed in. Blocking Turnstile's storage may stop the bot check from completing, so the forms it protects may not submit. To stop Google's and Meta's tags altogether, block Google's domains and Meta's domains (Meta's tag loads from connect.facebook.net) in your browser.
Changes to this notice
If we ever start using additional cookies or tags, we will update this notice first.
Contact us
Questions about this notice: support@orbitignition.com.