Privacy
Luna reads your search data to tell you what to fix. This page says exactly what that means: what is collected, what is never collected, who else can see it, and how to get rid of it.
Last updated 21 November 2026
The short version
- Luna uses read-only access where possible. It writes only what you have asked for: the website changes you authorize, and, if you connect Jobber, a request for each new lead, on a new client when Jobber does not already have one.
- Luna holds your customers’ contact details only if you add lead capture to your website, and then only the enquiries your forms receive. The Shopify permissions Luna requests exclude orders and customers entirely.
- Your data is never sold, and is never used to train anyone’s models.
- Disconnecting deletes the stored access token rather than marking it unused.
- Analytics, and Luna’s own ad tags on its public pages, run only if you agree to them, and the choice is a real one — declining costs you nothing. No ad code ever runs once you are signed in.
What Luna collects
Only what running Luna needs. This is the whole list.
| What | Why | Where it comes from |
|---|---|---|
| Account details | To sign you in and to know which organization you belong to | Your name and email, from you or from Google sign-in |
| Your sites and their pages | To audit them and score technical health, content health and AI readiness | Luna's crawler, reading your site the way a search engine would |
| Search and analytics figures | To show impressions, clicks, position and traffic beside the findings | Google Search Console and Google Analytics, read-only, once you connect them |
| Your product catalogue | To audit product and collection pages for search and AI visibility | Shopify, read-only, once you install the app |
| Your website connection | To apply the page titles and meta descriptions you approve, and undo them | A key or application password you create in WordPress, Webflow, Wix or Squarespace, stored encrypted and deleted when you disconnect |
| Website enquiries, if you add lead capture | To show which sources and pages bring in work, and to hand each lead to Jobber if you connect it | The name, email, phone, service and message fields of the forms you mark on your site, with the page the visitor first landed on and where they came from |
| Jobber jobs and invoices, if you connect Jobber | To show what the leads Luna sent became: each job's status and value, and what has been invoiced | Jobber, for clients that came from your leads only: ones Luna created, and existing clients a lead's email or phone matched, from that enquiry on |
| People at the companies you prospect | Names, job titles and work email addresses, so you can contact the companies you approve in the GTM agent | A contact-data provider Gambix contracts with, only when you press Find contacts, and an address check before the first email to each person; held inside your organization and deleted with the prospect or campaign |
| Your mailbox connection | To send the outreach you launch from your own address, and to read the replies to it | An app password you create with your email provider, stored encrypted and deleted when you remove the mailbox. The password opens the whole mailbox; Luna reads only the sender, subject and threading headers of mail that arrives after you connect, downloads only replies to its own emails and delivery-failure notices, and keeps only those about its own emails |
| Replies to your outreach, and unsubscribes | To show you who answered, stop their emails, and keep anyone who unsubscribed from being emailed again | Your mailbox, when a prospect answers; kept inside your organization |
| Answer-engine replies | To measure whether AI assistants mention your brand | Questions Luna asks answer engines about your category — never about you personally |
| Billing records | To know which plan you are on and what you have been invoiced | Stripe, which holds your card details; Luna never sees them |
| Usage counts | To apply your plan's limits, and to give each website one free preview | Luna itself: how many audits and AI checks ran, and which website had a preview |
| Feedback you send | To answer it and fix what it reports | The Feedback button: what you type, the page you were on and your browser's name |
| Product analytics | To see which features are used and where people get stuck | Only if you accept analytics; never what your audits found or your traffic |
| Ad measurement | To learn whether Luna's own ads bring people to Luna, and to show those ads to people who have visited | Only if you accept, and only on Luna's public pages: the page address, the ad that brought you, and the fact that you started a free check — never the website you checked |
What Luna never collects
Luna is a search tool, so it has no use for the data most breaches are made of, and asks for none of it. The one exception is opt-in: if you add lead capture, the enquiries your own forms receive (see Leads from your website below).
- No customer records from your store. The Shopify permissions Luna requests are
read_products,read_content,read_themesandread_online_store_pages. Orders, customers and payment data are not among them, and Luna could not read them if it tried. - No card details. Payment is handled by Stripe. Luna never sees a card number.
- No change without you. Google and Shopify connections are read-only. If you connect your website, Luna changes a page title or meta description only when you approve that change, and keeps the old value so it can be put back. If you connect Jobber, Luna opens a request for each new lead your website captures, with the enquiry as its note. The request goes on the client Jobber already has with the same email or phone, or on a new client. Luna changes nothing else in your account.
- No ad code inside your account. Luna’s own Google and Meta tags (Google Analytics, Google Ads and the Meta Pixel) run only on its public pages, only if you accept them, and never on the sign-in page, inside the product, on a shared report or on a free-check result. Nothing from your sites, your Google data or your connected accounts is ever given to an ad network.
Who else sees it
Luna runs on other people’s infrastructure, and being specific about which is part of the answer. These are every third party that can hold your data.
| Who | What they hold | Why |
|---|---|---|
| Supabase | Your account, sites, audits and findings | The application database and sign-in |
| Vercel | Requests to the application, and its logs | Hosting |
| Nothing new — Luna reads what you already have | Search Console and Analytics figures | |
| Shopify | Nothing new — Luna reads your existing catalogue | Product and collection data |
| Jobber | Your leads' contact details and enquiries, to find or create the matching client and open a request — in your own Jobber account | Handing leads to your field-service software, if you connect it |
| Stripe | Your billing details | Subscriptions and payment |
| PostHog | Product analytics events, only if you accept analytics | Seeing which features are used |
| Google (Analytics and Ads) | Visits to Luna's public pages and free checks started there, only if you accept | Measuring which visits and ads bring customers, and showing Luna's own ads |
| Meta | Visits to Luna's public pages and free checks started there, only if you accept | Measuring and showing Luna's own ads on Facebook and Instagram |
| Zoho | Feedback you send, delivered to the Luna team by email | Answering it |
| A keyword data provider | The words you enter in Keyword Opportunities (what you sell, a city or region, a country) — nothing about you or your customers | Search volume, difficulty and cost per click for related searches |
| AI models, through one provider | The questions Luna asks about your category and your brand name; and, when you ask Luna to draft a change, the public text of the page it is drafting for | Measuring whether AI assistants mention you, and drafting the changes you review |
The answer engines are asked questions a customer might ask — “what is the best running shoe for flat feet” — together with the brand name Luna is looking for. They are not sent your analytics, your customers, or anything from your store.
Leads from your website
Lead capture is off until you add Luna’s snippet to your site. Once it is on, each enquiry your marked forms receive is sent to Luna: the person’s name, email, phone, the service they asked about and their message, with the page they first arrived on and the search engine, profile, assistant or ad that sent them. Passwords, payment fields and fields Luna does not recognise are never sent.
With each enquiry the snippet also sends the ad click id of the visitor’s latest ad click, if they arrived through one, and their choice about ad measurement: a browser sending Global Privacy Control counts as a refusal. Luna recognises two enquiries from the same person by one-way hashes of the email address and phone number, so your reports count people rather than form submissions. Luna sends nothing about your enquiries to any ad platform.
For that data you are the controller and Luna is your processor: Luna uses it only to show you where your work comes from and, if you connect Jobber, to open a request for it on the matching client in your Jobber account. It is never used to contact anyone, never sold, and never used to train models. Your own privacy notice should say that enquiries are shared with Luna. It is deleted with the site or the account; to delete a single enquiry, write to the address below.
Google user data
Luna’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
When you connect Google Search Console or Google Analytics, Luna asks for read-only access and uses what it reads only to show you search and traffic figures beside your site’s findings. Luna does not sell that data, use it for advertising, use it to train AI models, or let anyone read it, except with your permission, where it is needed for security, or where the law requires it. Disconnecting deletes the stored access token.
How it is protected
Access tokens for your connected accounts are encrypted before they are stored, with a key held in the application environment and never written to the database — so a copy of the database is not a copy of your Google account. Every table that belongs to a customer is isolated at the database level, not merely filtered by the application.
The longer version, including what an attacker would have to do, is on the security page.
Analytics, ads, and your choice about them
Luna uses product analytics to see which features are used and where people get stuck. It is loaded only if you accept it. If you decline, it is never loaded at all — not loaded and silenced, but never fetched.
The Feedback button is Luna's own and needs no consent: it sends only what you type, the page you were on and your browser's name, to the Luna team.
The same choice covers Google Analytics and Luna’s own ad tags, from Google Ads and Meta. They load only on the home page, pricing, how Luna works, the managed service page, resources and the free check form — never on the sign-in page, inside your account, on a shared report, or on a page whose address carries something you typed, such as a free-check result. They tell Google and Meta which of those pages you visited, which ad brought you, and that you started a free check, and they set those companies’ own cookies so the visit can be matched to the ad. Google and Meta handle that under their own privacy policies.
Analytics and ad tags never record what your audits found, what your traffic is, or anything from your connected accounts. You can change your mind at any time from the footer of any page; withdrawing removes the Google and Meta cookies Luna’s pages set.
How long it is kept, and how to delete it
Your data is kept while your account is open. Disconnecting an integration deletes the stored token immediately. You can delete your account yourself from Manage, then Settings: it deletes your login and every organization only you belonged to — sites, audits, findings, reports, answers and connections — straight away, apart from invoices Luna is required to keep for tax and accounting.
To ask for a copy of your data or its deletion, write to privacy@gambix.io. We answer within 30 days.
Your rights
Depending on where you live, you may have the right to see the data held about you, correct it, take it elsewhere, or have it deleted. Luna applies these to everyone rather than checking your address first. Use the address above, and say what you want — you do not need to cite a regulation to be taken seriously.
Changes
If this policy changes in a way that affects what is collected or who sees it, we will say so in the product before the change takes effect, not merely edit this page and update the date.