1. Who we are
Namova is a trading name of Scale It Up Media Ltd, registered in England and Wales, company number 15538327, registered office 10a High Street, Chislehurst, Kent, BR7 5AN, United Kingdom ("Namova", "we", "us"). We are registered with the UK Information Commissioner's Office (ICO) under registration number ZC158065 (Scale It Up Media Limited).
This policy covers namova.ai, the website snapshot tool, the Namova app, the in-app assistant, the API, the MCP server (including the Claude and ChatGPT connection), and how we deal with customers, prospects and suppliers. The in-app assistant, Google connections and the API are coming soon and are not available yet. Where this policy describes them, it explains how we will handle personal data once they are available.
In this policy, "AI Apps" means AI assistants and AI search features, such as ChatGPT (OpenAI), Claude (Anthropic), Gemini (Google), Perplexity and Grok (xAI), in any form, including their consumer apps and websites. Namova measures AI Apps only through each provider's own API, directly or through an AI routing service, with web search turned on where we use it, and not through their consumer apps.
Contact. Email [email protected] or write to our registered office. We have not appointed a data protection officer because the law does not require one for our activities. The person responsible for privacy at Namova is Mo Buhariwala, Founder.
EU representative. We have not appointed a representative in the EU. Our processing of personal data of people in the EU is occasional and is not likely to result in a risk to their rights, so we rely on the exemption in Article 27(2) of the EU GDPR. People and authorities in the EU can contact us directly at [email protected].
2. Our role: controller or processor
- We are the controller for: your account and login details, billing, the website snapshot and the contact details you give with it, our website, our marketing, support messages, security logs and product analytics. This policy explains how we use that data.
- We are a processor for data our customers put into their Namova workspaces, such as their competitors, questions, reports, assistant chats and connected Google data. For that data our customer (the business or agency using Namova) is the controller and decides how it is used. Our Data processing agreement governs it.
- Agencies. When an agency uses Namova for its own clients, the agency is our customer and decides what client data goes into Namova. If you are an agency's client, please contact the agency first. If you contact us, we will pass your request to the agency and help it answer.
3. What we collect and why
| Data | Where it comes from | Why we use it | Lawful basis (UK and EU GDPR) |
|---|---|---|---|
| Account data: name, work email, company, role, workspace membership, password (stored only as a secure hash by our login provider), sign-in records | You, or a colleague who invites you | To create and secure your account and control access | Contract; legitimate interests (security) |
| Website snapshot: the business details you confirm (name, category, town, country, website), the text of that business's home page, the questions we ask and the AI answers | You, the business's public website, Google Places, AI Apps | To run the snapshot you asked for and show you the result | Legitimate interests (giving you the snapshot you asked for) |
| Snapshot contact details: your work email, the consent wording you agreed to, the language it was shown in, and when. You give these before you see any snapshot result. We check that the email's domain can receive email, but we do not send anything to confirm it | You | To show you the snapshot result and follow up about that snapshot and Namova | Legitimate interests (responding to your request); consent where we send marketing |
| Bot and abuse checks: signals a bot-check service reads from your browser, and a one-way scrambled code made from your internet address and the date (your internet address itself is not stored in our database) | Your browser and device | To check you are a person and limit snapshots and business searches per connection per day | Legitimate interests (security, preventing abuse) |
| Measurement data: questions, full AI answers, brands named, sources cited, provider, model and date | AI Apps, at our customers' request | To provide the Service | Contract (as processor for customers) |
| Workspace content: brands, competitors, fixes, approvals, reports, comments | You and your team | To provide the Service | Contract (as processor for customers) |
| Assistant chats: what you type to Ask Namova, the in-app assistant, its replies, and any thumbs up or down you give | You | To answer you inside the app and to check the quality of its answers | Contract (as processor for customers) |
| Google data you connect: see section 5 | Google, with your permission | To show your Google figures next to your AI results | Contract (as processor for customers) |
| API and MCP usage: key or token identifier, endpoint, time, internet address, client name, errors | Your systems and AI tools | To run, secure and rate-limit the API | Legitimate interests (security, running the Service) |
| Billing data: plan, billing contact and address, VAT number, invoices, payment status, and your acceptance of our terms (date, time, internet address, terms version). Our payment provider collects card details and, for US bank payments, bank account details, which it checks through its own bank connection service; we never see or store full card or bank account numbers | You, our payment provider | To take payment and keep tax records | Contract; legal obligation |
| Support and email: what you write to us, and delivery status of emails we send | You, our email provider | To answer you and send service emails | Legitimate interests; contract |
| Marketing preferences | You | To send news about Namova if you asked for it, and to honour opt-outs | Consent, or legitimate interests for existing customers where the law allows, always with an easy opt-out |
| Website and product analytics: pages viewed, the snapshot steps you reach (not what you type), device and browser type, approximate country, and a random ID kept in a cookie. On namova.ai we use PostHog (EU cloud) and Google Analytics. Our settings do not store your internet address, and we record no sessions on namova.ai. In the app, PostHog knows you by your account user ID, never your name or email, typed text is masked, and session recordings run only after you agree where the law requires consent. People who sign in to an agency's client portal get no analytics | Your browser | To see which pages help and find what is confusing or broken | Consent in the UK, the EEA and Switzerland (you choose on the site and can change it on every page); legitimate interests elsewhere, and you can turn it off on every page |
| Advertising cookies (website only, when we run ads): that you arrived from one of our ads, and that you finished a snapshot, clicked a sign-up button or asked to talk to us, with a random ID in a cookie. Google Ads and Meta (Facebook and Instagram) receive this with the page address, without its query or the private part of a snapshot link. Never what you type, never your name or email. When you finish a snapshot, our server also sends Meta that step with your internet address and browser type, so it is counted once. For visitors in the US, Google Analytics may also be used to show Namova ads to people who visited | Your browser | To see which ads bring customers, and to show Namova ads to people who visited | Consent in the UK, the EEA, Switzerland and Quebec (a separate choice from analytics); elsewhere on unless you turn it off on the cookie page. A Global Privacy Control or Do Not Track signal keeps it off |
| Security logs: sign-ins, admin actions, errors, internet addresses | Our systems | To keep the Service secure and investigate problems | Legitimate interests (security) |
People named in AI answers. Measurement data is mostly about businesses. An AI answer can still name a person, such as a sole trader, founder or reviewer. We keep those answers as the AI App gave them, as part of the measurement record for our customer. We do not build profiles of individuals and do not use Namova to measure private individuals (our Acceptable use policy forbids it).
Data we get from other sources. Some personal data reaches us without coming from the person it is about: names in AI answers, on public web pages and in Google Places or Business Profile results (such as a sole trader's name or a reviewer's name). For data we process for customers, the customer is the controller. Where we are the controller (for example the website snapshot), it would be impossible or take disproportionate effort to contact each person named, so under Article 14(5)(b) of the UK and EU GDPR we publish this notice instead, keep only what the measurement needs, do not use it to profile people, and delete it on the short timelines in section 9. You can still use your rights in section 11.
Required data. You need to give account and billing data to use paid plans, and an email to see any snapshot result. Everything else is optional.
Legitimate interests. Where we rely on legitimate interests, they are: providing what you asked for, keeping Namova secure, preventing abuse, and growing our business in ways you would reasonably expect. You can object (see section 11).
What we never do. We never send your email address to AI Apps. Questions are built from business details, not from your account or contact details. We do not make decisions about you with legal or similarly significant effects using only automated means.
4. AI processing
Namova sends questions, business details, public web page text and (for the assistant) your messages and the workspace data needed to answer them to AI providers through their business APIs, either directly or through a routing service that sends them to the chosen provider.
- We use AI providers' business APIs, not their consumer apps.
- In our routing service account, the setting that allows providers that train on request data is off, and prompt publishing is off. Under their current published API terms, the providers behind the AI Apps we use (OpenAI, Anthropic, Perplexity, Google (Gemini API, paid tier) and xAI) do not use API data to train their models by default. We do not claim zero data retention.
- For some answers, web search results come from a search provider whose privacy policy says it may use search queries to improve its services, including training models. Those queries are the buyer questions and business names, never your email address or connected Google data.
- Providers may keep requests for a short time for abuse monitoring under their own terms. Email [email protected] for the periods each provider publishes.
- Ask Namova, the in-app assistant: your questions, its answers and the workspace data needed to answer them are processed by our AI providers through an AI routing service. We keep the questions and answers for 30 days to check answer quality, then delete them.
- Namova never sends your email address or your connected Google data to AI providers. If you choose to send Google data to your own AI tool through our API or MCP server, see section 5.
5. Google user data
Google connections are coming soon and are not available yet. This section explains how they will work. You will be able to connect Google Search Console, Google Analytics and Google Business Profile. You choose which ones on Google's own consent screen, and you can disconnect at any time.
What we access
- Search Console (read-only): search performance for the sites you choose: queries, clicks, impressions, average position and pages.
- Analytics (read-only): reports for the properties you choose, such as sessions, traffic sources (including visits referred by AI assistants), landing pages and conversions. These are totals, not records of individual visitors.
- Business Profile (read only): the details of the listings you choose, such as name, address, categories, hours, reviews and performance figures. Google offers only one permission for Business Profile, and it technically allows changes. We tell you this on our connection screen before you consent. Namova only reads this data: our servers call only Google's read functions, and we do not post, reply to reviews or edit listings through Google's API.
How we use it
- Only to provide and improve features you can see in Namova: showing your Google figures next to your AI visibility results, comparing before and after a fix, and including them in reports you or your agency ask for.
- Not for advertising, including retargeting, personalised or interest-based ads.
- Not sold, and not transferred to advertising platforms, data brokers or information resellers.
- Not used to decide creditworthiness or for lending.
- Not used to train AI or machine learning models, and not included in any benchmarks or research we publish.
- Not sent by Namova to AI model providers, and not read by the in-app assistant. If we ever want to offer either, we will ask for your permission in the app first and update this policy.
- Sent to your own AI tools through the Namova API or MCP server only if you turn this on (see below).
Sending your Google data to your own AI tools
You can choose to let your own AI tools (such as Claude, ChatGPT, Cursor or another MCP client) read your connected Google data through the Namova API or MCP server. This is a feature you start, and it works like this:
- It is off by default, and you turn it on separately for each Google connection.
- Before it turns on, you choose the API key or tool that may receive it, and we show you which Google data will be sent and ask for your explicit consent. We record when you consented, who turned it on and which key or tool you chose.
- When it is on, we send only the Google data needed for each request, and only to the key or tool you chose.
- We never use this data to train or improve AI models and never sell it, and our staff do not read it unless you give us specific permission for particular data, it is needed for security or to investigate abuse, or the law requires it.
- You can turn it off at any time, and we stop sending data straight away.
- Once the data reaches your tool, it is under your control and that tool's provider's terms, including whether the provider uses it to train its models. Check those terms before you turn this on.
Who can see it
- Members of your workspace, and, if an agency runs your workspace, the agency users you allow.
- Our staff do not read your Google data unless you give us your specific permission for particular data (for example in a support request), it is needed for security (for example to investigate abuse), or it is needed to follow the law.
We transfer Google user data only to provide or improve the features above, for security, to follow the law, or as part of a merger, acquisition or sale of assets, and in that last case only after getting your explicit consent first. Our staff, contractors and processors must follow these rules.
Storage and deletion
- Google access tokens are stored encrypted and used only by our servers.
- You can disconnect in Namova's settings or at myaccount.google.com/connections. When you disconnect, we delete the tokens straight away and the Google data stored for that connection within 30 days.
- If you close your workspace, its Google data is deleted on the same timeline as other workspace data (see section 9).
Namova'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.
6. API, MCP server and your own AI tools
You can connect Namova to your own systems and AI tools (such as Claude, ChatGPT, Cursor or other MCP clients) through our API or MCP server.
- When you do, the data you pull goes to that tool under your control and that tool's own terms and privacy policy. The tool is not our processor or sub-processor, and we are not responsible for how it stores, uses or shares the data.
- You decide what to connect and can revoke a key or token at any time in your settings.
- Google user data is only included if you turn that on for a Google connection (see section 5).
- We log API and MCP requests (see the table in section 3) to run and secure the Service.
The Claude and ChatGPT connection
The Claude and ChatGPT connection lets you ask Claude or ChatGPT about your own Namova results. It only reads. You sign in with your Namova login and choose which Namova account the AI app may read. Client logins that an agency gives its clients cannot use it.
When you ask, the AI app receives only what that question needs from the account you chose: brand names and websites; how often AI apps mentioned the business, overall and for each AI app; the names of other businesses and websites that appeared in AI answers; your fixes (title, reason, who does it and status); totals from analytics reports you uploaded to Namova; and the month, date and app link of your latest monthly report. It never receives your email address, anyone's login details or figures from a connected Google account. Once the AI app has the data, it handles it under its own terms and privacy policy, as described above.
What we keep for the connection:
- The sign-in tokens we give the AI app, stored only in scrambled (hashed) form. They stop working when they expire (1 hour for access, at most 30 days in total) or when you disconnect, and are deleted within a day of expiring.
- A log of each request: which tool was used, which brand, how big the answer was, whether it worked and the time. We keep it for 90 days. We do not see or keep your conversation with the AI app.
- A scrambled, keyed copy of the internet address a connection request came from, used only to limit how many requests can be made. It is deleted after 1 day.
- The name the AI app gave itself when it connected (for example "Claude"). It is deleted 30 days after the AI app registered if it never started a sign-in, or 90 days after it was last used, unless a connection is still live.
- A record of each connection (which AI app, which Namova account, when it was made, last used and disconnected), kept while your account is open.
You can disconnect at any time in the Namova app (Account, then Claude and ChatGPT), or by removing Namova in Claude or ChatGPT. It stops working on the next question.
7. Who we share data with
- Service providers (sub-processors) who host, run and support Namova for us, under contracts that require them to protect the data and use it only on our instructions. The types we use, with what each does and where, are on our Sub-processors page; you can ask us for the names of the providers that receive your data.
- Your workspace and agency. People in your workspace, and the agency that runs it if there is one.
- Professional advisers such as lawyers and accountants, under confidentiality duties.
- Payment providers and card issuers, if a charge is disputed: transaction records, your acceptance of our terms and records of your use of the Service, so the dispute can be decided (legitimate interests: defending legal claims and recovering money owed).
- Authorities, where the law requires it or to protect rights, safety or security.
- A buyer of all or part of our business, who would have to honour this policy.
We do not sell personal data. When we run ads and advertising cookies are on for your browser, Google and Meta receive the advertising data described in section 3 (for US visitors this includes Google Analytics data used to show Namova ads), which some US state laws call "sharing" for cross-context behavioural advertising. You can turn this off at any time (see section 11, United States, and section 12).
8. International transfers
We are based in the UK. Our main database is hosted in the United States, and several sub-processors are in the United States, so personal data from the UK and the EU is transferred to the United States. Where personal data leaves the UK or the EEA, we protect it with one of these:
- a UK or EU adequacy decision, including the EU-US Data Privacy Framework and its UK Extension where the recipient is certified;
- the EU Standard Contractual Clauses, with the UK International Data Transfer Addendum (or the UK International Data Transfer Agreement) for UK data.
The safeguards used for each type of sub-processor are on our sub-processor page. Email [email protected] for a copy of the relevant safeguard.
For Australia: we may disclose personal information to recipients in the United States, the United Kingdom and the European Union. For Canada: your information may be processed outside Canada and may be accessible to courts and authorities there.
9. How long we keep data
| Data | How long |
|---|---|
| Website snapshot results (business details, questions, answers, the scrambled connection code) | 30 days, then deleted, unless you become a customer and add it to your workspace |
| Snapshot email and consent record | 30 days, then deleted, unless you become a customer or ticked a separate box to hear news about Namova (then see marketing preferences below). If you unsubscribe, we keep only your email on a suppression list so we do not contact you again |
| Business search abuse checks (the scrambled connection code) | 2 days, then deleted |
| Ask Namova questions, answers and feedback | 30 days, to check answer quality, then deleted. Deleted when you close your account (within a day at most) |
| Account data and workspace content (including measurement data and reports) | While your account is open. You can export it for 30 days after closing. Deleted 30 days after closing (a daily job), with backup copies overwritten within a further 30 days |
| Google user data | While connected. Deleted within 30 days of disconnecting, or with the workspace if you close it |
| API and MCP request logs, security logs | Up to 90 days, longer only if needed to investigate a specific incident |
| Claude and ChatGPT connection: request log (tool, brand, answer size, result, time) | 90 days |
| Claude and ChatGPT connection: scrambled internet address for rate limits | 1 day |
| Claude and ChatGPT connection: scrambled sign-in tokens | Until they expire or you disconnect, then deleted within a day |
| Claude and ChatGPT connection: AI app names | 30 days if never used, otherwise 90 days after last use, unless a connection is still live |
| Support emails | 2 years after the conversation ends |
| Billing and tax records | 6 years after the end of the financial year they relate to, as UK tax law requires |
| Product analytics | PostHog: 12 months, then deleted. Google Analytics: up to 14 months. Session recordings: 30 days |
| Billing evidence: your acceptance of the terms (date, time, internet address, terms version) and records of your use of the Service | 6 years after the charge they relate to, because they are part of our tax and billing records and answer billing disputes and chargebacks |
| Marketing preferences and opt-outs | Until you withdraw consent; opt-outs are kept so we can honour them |
We may keep data longer where the law requires it or to deal with a legal claim. After these periods we delete or anonymise data.
10. Security
- Data is encrypted in transit (TLS) and at rest.
- Each workspace can only see its own data, enforced in the database itself with row-level security.
- Secrets and Google tokens are kept in an encrypted store, separate from other data.
- Staff access is limited to what is needed to run and support the Service, and is protected by strong, unique passwords.
- We use bot checks, rate limits and spending caps to prevent abuse.
- If a breach puts your personal data at risk, we will tell you and the regulator as the law requires.
No system is completely secure, so we cannot promise that data will never be accessed without permission.
11. Your rights
Depending on where you live, you can ask us to:
- tell you whether we hold personal data about you and give you a copy;
- correct it;
- delete it;
- limit how we use it;
- give it to you or another company in a common machine-readable format;
- stop using it where we rely on legitimate interests (you can always stop marketing);
- withdraw consent at any time (this does not affect anything done before).
Email [email protected]. We may need to check your identity. We answer within one month (UK and EU), 45 days (US states) or 30 days (Canada and Australia), and will tell you if we need longer as the law allows. Using your rights is at no charge, unless a request is clearly unfounded or excessive.
If your data is in a customer's or agency's workspace, we are acting for them. We will pass your request to them and help them answer.
UK and EU
If you are unhappy with how we handled your data, you can complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint, or to the data protection authority in the EU country where you live or work. Please contact us first so we can try to help.
United States (California and other states)
This section applies where the California Consumer Privacy Act, as amended by the CPRA, or a similar state law applies to us.
- Notice at collection. The categories of personal information we collect are: identifiers (name, email, internet address); commercial information (plans, purchases); internet or network activity (usage, logs); approximate geolocation (from internet address); professional information (company, role); and the content of messages you send us. We collect them from the sources and for the purposes in section 3, and keep them for the periods in section 9.
- Sensitive personal information. We do not collect it for the purpose of inferring characteristics about you. Account passwords are used only to sign you in.
- Disclosure. We disclose these categories to service providers and contractors for business purposes (hosting, AI processing, email, payments, security, analytics), as listed on our Sub-processors page.
- No sale. Sharing only through advertising cookies. We do not sell personal information. When we run ads and advertising cookies are on for your browser, Google Ads and Meta receive internet or network activity on namova.ai (that you came from an ad, finished a snapshot, clicked sign-up or asked to talk to us) and a cookie ID, Meta also receives your internet address and browser type when you finish a snapshot, and for visitors in the US Google may use the Google Analytics data above to show Namova ads, which may count as "sharing" for cross-context behavioural advertising. To opt out, choose "Turn off advertising" on our Cookie notice page or use Global Privacy Control. We do not knowingly collect personal information from anyone under 16.
- Your rights. You can ask to know, access, correct and delete your personal information, and to opt out of sale, sharing, targeted advertising and profiling. We do not sell or profile; sharing and targeted advertising happen only through the advertising choice above (advertising cookies, and for US visitors Google Analytics ad personalisation), which you can turn off. We will not treat you differently for using your rights.
- Global Privacy Control. We treat a Global Privacy Control signal from your browser as a valid request to opt out of sale and sharing for that browser. It also turns website analytics and advertising cookies off for that browser.
- Authorised agents. You can use an authorised agent. We may ask for proof that you gave them permission and ask you to verify your identity with us directly.
- Appeals. If we decline your request, you can appeal by replying to our decision or emailing [email protected] with "Appeal" in the subject. We will answer within 45 days. If you are not satisfied, you can contact your state Attorney General.
Canada
We handle personal information under PIPEDA and applicable provincial laws. You can access and correct your information and withdraw consent, subject to legal and contractual limits. If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada or your provincial commissioner.
Australia
We handle personal information under the Australian Privacy Principles. You can access and correct your information. If you have a complaint, email us and we will answer within 30 days. If you are not satisfied, you can complain to the Office of the Australian Information Commissioner (OAIC).
Everywhere else
If you live outside the UK, the EU, the US, Canada and Australia, you can still ask to see, correct or delete the personal data we hold about you. Email [email protected] and tell us what you would like us to do. We answer within 30 days.
12. Cookies
Some strictly necessary technologies are used for sign-in and bot checks. Our website also uses analytics cookies from PostHog and Google Analytics, and, when we run ads, advertising cookies from Google Ads and Meta as a separate choice. Both are used in the UK, the EEA and Switzerland only after you accept them, and elsewhere unless you turn them off. The app uses no advertising cookies. See our Cookie notice.
13. Children
Namova is a business service for people aged 18 and over. We do not knowingly collect personal data from children. If you think a child has given us data, email us and we will delete it.
14. Changes
If we change this policy, we will update the date at the top. If a change materially affects how we use personal data you have already given us, including Google user data, we will tell you before it applies and ask for your consent where the law or Google's policy requires it.
15. Contact
[email protected], or Scale It Up Media Ltd (Namova), 10a High Street, Chislehurst, Kent, BR7 5AN, United Kingdom.