Privacy Policy
Effective date: 17 November 2026
This policy explains how Oxford Impulse ("we", "us", "our") collects, uses, and protects personal data when you use Orbit Insight (the "Service"), a platform for Shopify merchants, teams, and agencies to track and understand order attribution.
This policy covers five different kinds of personal data, because the Service plays two different roles depending on whose data it is:
- Data about you, as a Service user (your name, email, phone number, and account activity) — here, we are the data controller: we decide why and how this data is processed, and this policy is our direct commitment to you.
- Data about your customers, when your Shopify store is connected to the Service (order records, which can include a customer's name, email, and address) — here, we are a data processor acting only on your instructions, as your app. You remain the controller of your own customers' data, and your own privacy policy (the one your storefront shows) is what governs your relationship with them. Section 6 below describes what this means in practice.
- Data about you, if you join our waitlist (your email address) — here too, we are the data controller. Section 2A below describes what we collect and why.
- Data about you, if you arrive from one of our ads (the ad tags and click IDs of your visit, your IP address and browser type, and a random visitor ID): here too, we are the data controller. Sections 2B and 2D below describe what we record, what we tell advertising platforms, and why.
- Data about how you use our website and the app (data from Google Tag Manager, Google Analytics and, if you allow Advertising, Meta's measurement tools, with cookies and full measurement only as your cookie banner choice allows, and only limited information without cookies before you answer or after you reject non-essential): here too, we are the data controller. Section 2C below describes what we collect and why.
1. Who we are
Oxford Impulse operates the Service. If you have any question about this policy or how your data is handled, contact us at support@orbitignition.com.
2. Data we collect about you (Service users)
When you create an account or use the Service, we collect:
- Account information: your name, email address, the phone number you give us when you sign up (kept encrypted, see section 2D), and (if you sign in with a password) a securely hashed password — we never store your password in plain text.
- Authentication data: if you sign in with Google, we receive your Google account's name and email address from Google, not your Google password. If two-factor authentication is enabled, we store a securely hashed verification secret, not a copy of your authenticator app.
- Organization and role data: which organization(s) you belong to, your role within them, and any invitations sent to or from you.
- Usage and activity data: an audit log of significant actions taken on your account or organization (e.g. sign-ins, role changes, connections made), used for security and for you to review your own organization's activity.
2A. If you join the early-access waitlist
You don't need an account to join our early-access waitlist. If you enter your email address in the waitlist form on our website, we collect:
- Your email address, which you give us.
- The page you signed up on and your language: which page of our website you used the form on, and whether you were viewing it in English or Turkish.
- The date and time you signed up.
We use this only to send you a confirmation email and to tell you when early access to Orbit Insight opens. For this data we are the data controller. We rely on your consent: you give it by submitting the form, and you can withdraw it at any time by emailing us, without affecting anything we did before you withdrew it. Giving us your email address is voluntary.
If you also allowed Advertising on our cookie banner before you joined, section 2B explains how your signup can be linked to the ad that brought you. Section 2D explains what we then tell the advertising platforms about that signup. If your browser also carries the visitor cookie that section 2B describes, we keep the IP address and browser type of your signup request as well, as section 2D describes.
We keep waitlist details until we have told you that early access is open and for up to 12 months after that. If early access has not opened within 24 months of you joining, we delete your details at that point. We also delete them earlier if you ask us to. To stop hearing from us or to have your details deleted, email support@orbitignition.com. We will act on your request within one month.
Who receives this data and where it is processed is described in section 5, and your rights, including the right to complain to the Information Commissioner's Office, are described in section 7.
2B. If you arrive from one of our ads
If you arrive from one of our ads and you have allowed Advertising on the cookie banner, we record the ad tags and click IDs in the address (for example utm_campaign and gclid), the time, the page you landed on (its address without the tags), the name of the website you came from, the advertising platform we work out from the tags, the version of the banner you answered, and a random visitor ID kept in a cookie (oi_vid) that lasts up to 12 months. A visit without ad tags or a click ID records nothing. We also record your IP address and browser type (the "user agent", which can also show your device and operating system), encrypted, and keep them for the same 12 months as the rest of the record, so that they are available to help match a later step to your visit (see section 2D). If you later join the waitlist or sign up in the same browser, we keep the IP address and browser type of that request too, on the record that links your browser to your waitlist entry or account (see section 2D). We do not record any browser fingerprint in these records.
We use these records for two purposes: to measure which of our own advertising brings people to the Service and to the waitlist, so that we can judge and improve it, and, as section 2D describes, to tell the advertising platforms we use what your visit led to. For this data we are the data controller. Our legal basis is your consent, which you give by allowing Advertising on the cookie banner (Accept all, or Customise with Advertising ticked). It covers both the visitor cookie and the records, and you can withdraw it at any time.
If you later join the waitlist or create an account in the same browser, we link these records to that waitlist entry or account, and we note the date of up to four moments: you joining the waitlist, your account's email being verified, your trial starting and your first payment. For each moment we keep a short copy of the first and the last campaign that brought you (platform, source, medium and campaign name) for as long as that waitlist entry or account exists. For merchants who pay through Shopify, the first-payment date is the date Shopify reports the first real charge for the plan; a free or $0 plan is never counted. Whether or not you allowed Advertising, we keep the date of these moments as an ordinary business record; if you did not allow Advertising, it carries no campaign details.
Each recorded visit, and the link between your browser and your waitlist entry or account, is deleted automatically after 12 months. 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 records are held in our own database, hosted as described in section 5, and are seen in our admin panel only by Oxford Impulse staff who have been given access to it. We do not sell them. Apart from what section 2D describes, we do not send them to advertising platforms or to anyone else. If we ever start sending anything more to an advertising platform, we will update this policy first.
To withdraw your consent, choose Reject non-essential, or Analytics only, under "Cookie settings" in the footer of our public pages. Recording stops, the visitor cookie is removed, the records linked to it are deleted and the campaign details copied onto your waitlist or account records are cleared (the date of the moment itself stays as a business record). You can also email support@orbitignition.com to ask for a copy of these records or for them to be deleted; the personal data export in your account includes them. When your account is deleted, we also delete the ad records linked to it. If you ask us to delete your waitlist entry, we also delete the records linked to it, unless the same browser is also linked to another waitlist entry or to an account, in which case they stay until that entry or account is also deleted. Your other rights are described in section 7.
2C. Analytics and advertising measurement
If you allow Analytics on the cookie banner, we use Google Tag Manager and Google Analytics to count visits and to see how our website and the app are used. If you allow Advertising, we also use Google's advertising tags to see whether our own Google ads led to a waitlist signup, an account or a payment. For this data we are the data controller. Our legal basis is your consent, which you give with the cookie banner and can withdraw at any time with "Cookie settings" in the footer of our public pages.
Before you answer, and after you choose Reject non-essential, Google's tags run on our public pages and on the sign-in, sign-up and forgot-password pages in a limited mode without cookies. Google then receives limited information about your visit, as described in our Cookie Notice. We deliberately load nothing from Google on the page where you set a new password or on sign-in links that carry a store or an invitation. The signed-in app uses Google Analytics in a separate account, only if you allowed Analytics, and the only page information it sends is the name of the screen you are on (for example "/dashboard/orders"), never an order number, store, email address or search text. Google Analytics also receives what it collects automatically, such as your browser type and IP address.
Google acts as our service provider for Analytics. For advertising measurement, Google also uses the data for its own purposes under its own terms. Google may process this data outside the United Kingdom and the European Economic Area under its own safeguards. We keep detailed Analytics data for 14 months. Data that identifies a returning browser or device is kept for 14 months after its last visit, so it can be kept longer for someone who keeps visiting. Summary reports built from totals are not limited to that period.
If you allow Advertising, we may also use Google signals and audiences. Where you are signed in to a Google account with personalised ads switched on, Google can link your visit to that account to recognise you across your devices, to give us aggregated reports by age group and interests, and to place you in audiences that we use to show you our ads on Google's services and partner sites (remarketing). Google also uses this data for its own purposes under its own terms. You can switch personalised ads off in your Google account's ad settings at any time, and take back your permission with "Cookie settings" in the footer of our public pages.
If you allow Advertising and give us your email address, phone number or name on our site (for example when you join the waitlist or create an account), we may send Google a scrambled (hashed) version of each instead of the plain text. Google compares each with the details it holds on its own accounts, so that it can tell whether one of our ads led to that signup. We do this only if you allowed Advertising. The signed-in app's Google Analytics does not use Google signals, audiences or hashed contact details. Section 2D describes what our own server sends to Google Ads.
If you allow Advertising, we also use Meta's tools 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. The recipient is Meta Platforms Ireland Limited for visitors in the UK and the European Economic Area. Meta's tag runs in your browser and sends Meta the pages you look at and the steps you take on our site (viewing the pricing page, joining the waitlist, signing up). Meta also receives your email address in a scrambled (hashed) form when you join the waitlist; your email address, phone number and name in a scrambled (hashed) form when you sign up; 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 (hashed) form, because Meta's automatic matching is switched on; your browser type and IP address as with any request to a website; and Meta's two cookies (_fbp and _fbc). 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. Our server sends Meta the later steps, as section 2D describes, through our own address, gtm.orbitignition.com, on a server that Google hosts for us. The measurements of Google's tags on our pages pass through the same address on their way to Google and, if you allowed Advertising, to Meta. For this data we are the data controller, and Meta also uses it for its own purposes under its own terms. Meta may process this data in the United States and other countries under its own safeguards. Our legal basis is your consent, which you give with the cookie banner. If you do not allow Advertising, no Meta tool loads and nothing is sent to Meta. You can take back your permission at any time with "Cookie settings" in the footer of our public pages, which also deletes the two Meta cookies and the copies we keep of them.
See our Cookie Notice for the cookie names and how withdrawal works.
2D. Telling advertising platforms what your visit led to
If you allowed Advertising on the cookie banner and your visit to our site carried ad tags or a click ID, we tell the advertising platforms we use (currently Google Ads and Meta) when you take a step on our site: joining the waitlist, verifying your account, starting a trial, or your first payment. This lets us see which ads work, and lets those platforms show our ads to people more likely to sign up. We do this only if you allowed Advertising.
What we send to Google: if your visit came from a Google ad, its click identifier (Google's gclid, or the gbraid or wbraid identifier that Google adds to some ad clicks, for example on iPhones; we send at most one of the three); the time of the step and a reference number for it (for a first payment, its payment reference); and for a first payment the amount you paid and its currency. We also send scrambled versions (a one-way hash, SHA-256) of your email address and, where we hold it, your phone number. We send these even if your visit did not come from a Google ad, so that Google can match the step to its own accounts. In plain form, we also send Google, where we hold them, the IP address and browser type of the request on which you joined the waitlist or signed up, and the IP address and browser type of the visit on which you arrived from a Google ad. The visit we mean is that of the newest Google ad click recorded in a browser linked to the step: for an organisation's trial start or first payment that can be a click recorded in another owner's browser, and on a browser that several people use it can be another person's click. With a trial start or a first payment we also send your first name and last name, scrambled the same way, together with the country and postal code of your payment address (described below), which we send as they are; we send these four together or not at all.
What we send to Meta: the time of the step and, for a first payment, the amount you paid, its currency and its payment reference; the same scrambled email address and, where we hold it, phone number, and also your name and an internal identifier of your waitlist entry or account, both scrambled the same way, the values of Meta's two cookies (_fbp and _fbc) if we hold them, and, in plain form, the IP address and browser type we stored with your ad click or, if you joined the waitlist or signed up, with that request, so that Meta can match the step. When we use an ad click for this, it is the newest one recorded under the wording of 4 November 2026 or later in a browser linked to the step: for an organisation's trial start or first payment that can be a click recorded in another owner's browser, and on a browser that several people use it can be another person's click. With a trial start or a first payment we also send Meta the country, postal code, city and state of your payment address (described below), scrambled the same way, as far as we hold them. These go to Meta through our own address, gtm.orbitignition.com, as section 2C describes.
Our own server sends your IP address and browser type to Google and to Meta, as described above. Google's own tags and Analytics on our pages are separate: Google also receives your IP address and browser type from your browser, as section 2C explains. A scrambled value cannot be turned back into your details by us, but a platform that already knows them can recognise it, so we treat it as personal data.
The payment address: with a trial start or a first payment, the only steps that can have a payment record, we read the address that Stripe, our payment provider, holds for your organisation. Checkout asks for your full billing address, so this is usually your country, postal code, city and, where your country has one, state; we read only those four fields and never the street (if there is none on your organisation, we use the billing address of your latest successful payment). We read it from Stripe at the moment we send the step, read-only, and we store nothing from it. If Stripe has no address for you or does not answer in time, the step is sent without one.
Our own server sends data to Meta only for people who agreed to the Advertising wording of 4 November 2026 or later; this is why the banner asks everyone again. For Meta, only your own waitlist or sign-up request can record that you agreed to this wording, so if you joined the waitlist or signed up under an earlier wording, nothing about your later steps is sent to Meta, even if you allow Advertising again later. For Google, the IP address and browser type of your waitlist or sign-up request, your name and your payment address are sent only if that request was made under the wording of 4 November 2026 or later. The IP address and browser type of an ad click are sent to Google only if the click itself was recorded under that wording; a click can be recorded after you allow Advertising again, even if you signed up earlier. If you joined the waitlist or signed up under the wording of 2 November 2026 or later, Google still receives the scrambled email address, phone number and click identifier described above.
What we keep: with each ad click we keep your IP address and browser type, encrypted, for 12 months with the rest of the click record, so that they are available to help match a later step to your visit. If your browser has the visitor cookie that section 2B describes and you join the waitlist or sign up with Advertising allowed, we keep the IP address and browser type of that request too, encrypted, on the record that links your visit to your waitlist entry or account, for 12 months with the rest of that record, so that a later step (your trial, your first payment) can be matched even when the visit on which you joined or signed up carried no ad tags or click ID. We keep a log of what we sent, with no contact details in it. It is kept for as long as we keep the record of the step it belongs to. We keep no copy of the payment address; it is read when the step is sent and used only for that step. The platforms keep what they receive under their own policies.
Phone number: we ask for it when you sign up and keep it encrypted for as long as your account exists, whatever you chose on the cookie banner, so that it is available if you allow Advertising later. We use it for ad matching only if you allowed Advertising. It goes to one other place, whatever you chose on the cookie banner: when your organisation first starts a trial or a paid plan, we create its billing account at Stripe, our payment provider, with your name and this phone number as the contact details on it, so that Stripe's records and receipts show who the customer is. A copy we have already given to Stripe stays on its billing account until we update or delete it there; ask us and we will. You can ask us to delete it at any time, as section 7 explains.
If you reject Advertising, or switch it off later in Cookie settings, we stop sending for visits from this browser and delete this browser's click record and the record that links it to your waitlist entry or account, including the IP address and browser type kept with either. For Meta, we also delete the copies we keep of its two cookie values. What a platform already received stays with it; its own privacy controls apply.
3. Data we access on your behalf (your Shopify store's data)
When you connect a Shopify store, the Service reads order, refund, and (where the order includes it) customer data from that store — via Shopify's webhooks for new activity, and via a one-time historical import when you first connect. This can include, for each order: order value and currency, the landing page and referring URL that led to the order, UTM parameters, and — where present on the order — the customer's name, email address, and billing/shipping address.
We use this data for one purpose: to attribute your orders to the marketing channel that drove them, and to show you that attribution in your dashboard. We do not sell this data, use it to build advertising profiles, or use it for any purpose other than providing the Service to you.
3A. Data we access on your behalf (your Google Ads data)
If you connect Google Ads, you sign in with Google and approve a permission that lets the Service read data from the Google Ads accounts you choose. Google describes this permission as "See, edit, create, and delete your Google Ads accounts and data". It is the only permission Google offers for the Google Ads API, and it is broader than what we do: the Service only reads. It never creates, edits, pauses or deletes anything in your Google Ads account.
We read and keep:
- The email address and ID of the Google account you connected.
- For each Google Ads account that login can reach: its ID, name, currency, time zone, status, and where it sits under a manager account.
- For each campaign and each day: the campaign's ID and name, spend, impressions, clicks, conversions, and conversion value.
- A Google access token (a "refresh token") that lets the Service keep syncing without asking you to sign in again. It is encrypted at rest.
We also read the following. We do not keep all of it; what we keep is stated for each item:
- For each Google Ads account you link to a store: its total conversions, conversion value and view-through conversions for a date range. We use them to compare what Google reports with your store's orders. We keep the totals and the difference we calculate.
- The tracking settings of your ads that are not removed: the IDs and names of the campaign, ad group and ad, and the tracking templates, final URLs and URL parameters. We use them to find ads whose UTM tags are missing or broken. For an ad where we find a problem, we keep its IDs and names, a description of the problem and its tracking template. We keep nothing for ads that are fine.
- The names of your campaigns that are not removed, when you open the campaign list in our UTM Builder. We show them and do not keep them separately.
We use this data for one purpose: to show you your ad spend and results next to your Shopify orders, to explain differences between what Google reports and what your store recorded, and to check your tracking setup. We do not sell it, use it for advertising or to build advertising profiles, or use it to train artificial-intelligence or machine-learning models that serve other customers. We do not share it with anyone else, except where you ask us to (for example, when you schedule a report to be emailed to someone you choose), the service providers that help us run the Service (section 5), and where the law requires. If we ever use it in a new way, for example to give you AI-based recommendations for your own ads, we will update this policy before we do.
AI assistants you connect. A member of your organization can connect an AI assistant, such as Claude or ChatGPT, on the AI connectors page in Settings. The assistant can then read what that member can read in Orbit Insight. That includes your Google Ads data: campaign names, spend, the conversion value Google reports, the comparison with your store's orders, and the results of our tracking checks. It can only read; it cannot change anything in your Google Ads account. We send it data only when the member asks it a question, and nothing otherwise. The assistant's provider receives what the assistant reads and handles it under its own terms and privacy policy, not ours, so check them before you connect. The connection can be revoked at any time on the same page, and the assistant can then no longer read your data.
Orbit Insight's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Campaign data and Discrepancy Explainer results older than 24 months are deleted automatically. When you remove a store's Google Ads link, we delete that link and the daily campaign results we imported for it. When you remove the Google login in Settings, we delete the saved token, the saved list of accounts and every store link made with that login, together with the campaign results imported for them, and we ask Google to revoke the permission. Results we already calculated from that data (Discrepancy Explainer snapshots, report snapshots and tracking-check findings) are not deleted by Remove; they stay while your account exists, apart from the 24-month rule above. You can also revoke the permission yourself at myaccount.google.com/permissions. If you close your account, section 4 applies.
4. How long we keep data
Order data (including any customer name, email, and address it contains) is retained for up to 24 months on a rolling basis, matching the reporting history the Service shows you. Account data is retained for as long as your account is active. If you close your account or your organization stops using the Service, we delete or anonymize account and order data within a reasonable period, except where we're required to keep it longer (for example, financial or legal record-keeping obligations). Waitlist details are covered in section 2A above. Ad-measurement records are covered in section 2B above. Analytics and advertising measurement is covered in section 2C above. What we tell advertising platforms is covered in section 2D above. Google Ads data is covered in section 3A above.
If you uninstall the Service from your Shopify store, we stop syncing new data immediately and mark the connection as disconnected; existing order data is retained under the same 24-month policy unless you request earlier deletion (Section 6).
5. Who we share data with
We don't sell personal data. We share it only with service providers who help us run the Service, each acting under contract and only for the purpose we specify:
- Shopify — the source of your store's order data, and the platform through which the Service is installed.
- Resend — sends transactional email on our behalf (sign-up verification, password reset, invitations, two-factor codes, and the waitlist confirmation email). Resend does not use this data for its own purposes.
- Cloudflare — provides bot/spam protection (Turnstile) on our sign-up, sign-in and waitlist forms. To run this check, Cloudflare processes technical information about your visit, such as your IP address.
- Render — hosts the Service, including the databases that hold your data. Our hosting is in the EU (Frankfurt).
- Google — if you choose to sign in with Google, to verify your identity, and if you connect Google Ads, as the source of your Google Ads data (section 3A).
- Google (Tag Manager and Analytics): to measure how our website and the app are used and how our own ads perform, as described in section 2C. If you allowed Advertising, we also tell Google Ads what your visit led to, as described in section 2D.
- Meta (Pixel and Conversions API): to see whether our own Meta ads led to a waitlist signup, an account or a payment, as described in sections 2C and 2D.
- Stripe: processes payments for organisations that pay us directly, holds the billing address entered at checkout or in the company settings, and holds the name and phone number you gave us at sign-up as the contact details on your organisation's billing account (section 2D). With your Advertising consent we read the country, postal code, city and state from Stripe at the moment we send a trial start or first payment (section 2D), read-only and without storing them.
Some of these providers process data outside the UK/EEA. Where that happens, we rely on the UK's International Data Transfer Addendum, Standard Contractual Clauses, or an equivalent recognized safeguard with each provider.
If a member of your organization connects an AI assistant (section 3A), what the assistant reads goes to its provider at that member's request. That provider is not our service provider and acts under its own terms.
We may also disclose data if required by law, or to protect the rights, property, or safety of Oxford Impulse, our users, or others.
6. If you're a Shopify merchant: your customers' data
The Service processes your customers' order data strictly as your instructed processor, for the sole purpose of showing you order attribution. We do not contact your customers, market to them, or share their data with anyone except the service providers listed in Section 5, to the extent needed to run the Service.
You (or your customer, through you) can ask us to:
- Export a customer's order data held by the Service — we fulfil this within Shopify's required 30-day window.
- Redact a customer's personal data — we remove their name, email, and address from their order records. The order's amounts, dates, and marketing attribution are kept (with the personal fields removed) so your own reporting history stays intact.
- Delete everything for your store — if you uninstall the Service and request it, or if Shopify itself instructs us to (its "shop redact" process), we permanently delete all data associated with your store.
These are the same three data-handling requests Shopify requires every app to support, and the Service implements all three.
7. Your rights
If you're in the UK or EEA, UK GDPR / GDPR gives you the right to: access the personal data we hold about you; correct it if it's inaccurate; ask us to delete it; restrict or object to certain processing; and receive a copy of it in a portable format. To exercise any of these rights, contact us at support@orbitignition.com. If you're not satisfied with our response, you have the right to complain to the UK Information Commissioner's Office (ico.org.uk) or your local data protection authority.
8. Security
We use industry-standard measures to protect the data we hold, including encrypting all data in transit (HTTPS/TLS), encrypting your Shopify access token, your Google access token, and your customers' personal data (name, email, address) at rest, and restricting access to your organization's data to authenticated members of that organization only. We are actively working toward additional safeguards, including a formal security incident response process, ahead of general availability — this policy will be updated once those are in place.
9. Children
The Service is a business tool intended for merchants, teams, and agencies. It is not directed at children, and we do not knowingly collect personal data from anyone under 16.
10. Changes to this policy
We may update this policy as the Service changes. If we make a material change, we'll notify account holders by email or through the Service before it takes effect.
11. Contact us
Questions, requests, or complaints about this policy or your data: support@orbitignition.com.