1. About this agreement
This data processing agreement ("DPA") forms part of the contract between Scale It Up Media Ltd, trading as Namova, company number 15538327 ("Namova", "we", the processor) and the customer that agreed to our Terms of service or an order form ("Customer", "you"). It applies when we process Customer Personal Data on your behalf. It applies automatically; you do not need to sign it. If you need a signed copy, email [email protected].
If this DPA conflicts with the terms of service on a data protection matter, this DPA wins. If the Standard Contractual Clauses conflict with this DPA, the Standard Contractual Clauses win.
2. Definitions
- Data Protection Law means all laws on personal data that apply to the processing, including the UK GDPR and the Data Protection Act 2018, the EU GDPR (Regulation 2016/679), the Swiss Federal Act on Data Protection, the California Consumer Privacy Act as amended (CCPA) and other US state privacy laws, PIPEDA and the Australian Privacy Act 1988, in each case as they apply.
- Customer Personal Data means personal data in Customer Data (as defined in the terms of service) that we process for you as a processor.
- Controller, processor, data subject, personal data, personal data breach, processing and supervisory authority have the meanings in the GDPR. "Service provider" and "contractor" have the meanings in the CCPA.
- Sub-processor means another processor we engage to process Customer Personal Data.
- "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.
- EU SCCs means the standard contractual clauses approved by the European Commission in Decision 2021/914. UK Addendum means the International Data Transfer Addendum to the EU SCCs issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018.
3. Roles
- You are the controller of Customer Personal Data, and we are your processor.
- If you are an agency acting for your own clients, you may be a processor for them. In that case we are your sub-processor, you confirm your clients have authorised our use, and you pass on our commitments to them as needed. You remain our only point of contact.
- We are a separate controller for account, billing, security and website data, as our Privacy policy describes. This DPA does not apply to that data.
4. Your instructions
- We will process Customer Personal Data only on your documented instructions, including with regard to international transfers, unless the law requires otherwise. If it does, we will tell you before processing unless the law forbids that.
- Your instructions are: the terms of service, this DPA, your configuration and use of the Service (including connecting accounts, running measurements, using the assistant and using the API or MCP server), and any further written instructions we agree.
- We will tell you if we think an instruction breaks Data Protection Law. We may then pause the instruction until it is confirmed or changed.
- You are responsible for the lawfulness of the processing you instruct, for giving the notices and getting the consents your data subjects need, and for the accuracy of Customer Personal Data.
5. Our people
We make sure that everyone we authorise to process Customer Personal Data is bound by a duty of confidentiality and only accesses it as needed to provide and support the Service.
6. Security
We will keep in place appropriate technical and organisational measures to protect Customer Personal Data, taking into account the state of the art, cost, and the nature, scope, context and purposes of the processing and the risks to people. Our current measures are in Annex 2. We may update them, as long as the overall level of protection does not go down.
7. Sub-processors
- You give us general authorisation to use sub-processors. The types of sub-processor we use are on our Sub-processors page. The named list is in Annex 3. We send it to the owner of every paid account when this DPA starts, and again on request at [email protected]. You agree to keep the named list confidential, except to your advisers, auditors, regulators, or a data subject exercising their rights.
- Before we add or replace a sub-processor, we will update the named list and email the owner of every paid account, naming the new sub-processor, what it will do and where, (and any extra contact you give us for this at [email protected]) at least 30 days before the new sub-processor processes Customer Personal Data. Only if we must urgently replace a supplier that has failed, to keep the Service running, may the notice be shorter; we will then tell you as soon as we can, explain why, and the objection right below still applies.
- You may object on reasonable data protection grounds by emailing us within 14 days of the notice. We will discuss it in good faith and try to offer a reasonable alternative. If we cannot, you may end the affected part of the Service with no further charges, effective immediately.
- We put a written contract in place with each sub-processor with data protection obligations that are at least as protective as this DPA. We remain responsible to you for each sub-processor's performance.
8. Third-party AI tools you connect
When you connect a third-party AI tool, MCP client or other system to Namova through our API or MCP server, you choose that tool and control what data it retrieves. That tool is your recipient, not our sub-processor. Data you pull through it is transferred at your instruction and is governed by your agreement with that tool's provider. We are not responsible for that tool's processing, security or outputs.
Google user data. Data from your connected Google accounts is only available through the API or MCP server if you turn it on for that Google connection. It is off by default and needs your explicit consent. We record when and by whom it was turned on or off. When it is on, we send only the Google data needed for each request, only to the key or tool you selected on the consent screen. We record which key or tool that is. We never use it 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. Our use of Google user data follows the Google API Services User Data Policy, including the Limited Use requirements.
9. Helping you
- Data subject requests. Taking into account the nature of the processing, we will help you, by appropriate technical and organisational measures, to answer requests from data subjects to exercise their rights. If we receive a request directly about Customer Personal Data, we will pass it to you without undue delay and not answer it ourselves, except to tell the person to contact you.
- Security, breaches, impact assessments and consultation. Taking into account the nature of the processing and the information available to us, we will help you meet your obligations under Articles 32 to 36 of the GDPR: keeping processing secure, assessing and notifying personal data breaches, data protection impact assessments, and prior consultation with a supervisory authority.
- Cost. Help beyond what the Service's features provide may be charged at our reasonable rates, unless the request arises from our breach.
10. Personal data breaches
- We will notify you of a personal data breach affecting Customer Personal Data without undue delay, and in any case within 48 hours of becoming aware of it.
- Our notice will include, as far as we know at the time: what happened, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact for more information. We will send further details as they become available.
- We will take reasonable steps to contain the breach and limit harm, and help you meet your own obligations to notify regulators and data subjects.
- Our notice is not an admission of fault or liability.
11. Deletion and return
- At your choice, when the Service ends we will either return Customer Personal Data to you (as an export in a common machine-readable format, such as CSV or JSON) or delete it. You can make your choice, and download the export, at any time up to 30 days after the Service ends. If you ask for deletion sooner, we will delete it sooner.
- After return, or if you make no choice, we will delete Customer Personal Data and all copies within 90 days of the end of the Service, and backup copies will be overwritten within a further 30 days. We will confirm deletion in writing on request.
- We may keep Customer Personal Data longer only where the law requires it. We will keep it confidential and process it only for that purpose.
12. Audits and information
- We will make available the information reasonably needed to show that we meet Article 28 of the GDPR, including this DPA, our security measures, our sub-processor list and, when we have them, independent security reports or certifications.
- If that information is not enough to show compliance, or a supervisory authority requires it, you may audit us (or appoint an independent auditor bound by confidentiality who is not our competitor) no more than once in any 12 months, with at least 30 days' written notice, during normal business hours, without unreasonably disrupting our business. Audits are at your cost unless they show we have materially broken this DPA. Audits of our sub-processors are carried out through their own audit reports and certifications.
13. International transfers
- We may transfer Customer Personal Data outside the UK, the EEA or Switzerland, including to the United States, where our main database and several sub-processors are. We will only do so with a valid safeguard under Data Protection Law.
- EU SCCs. To the extent a transfer from you to us is a restricted transfer under the EU GDPR and no other safeguard applies, the EU SCCs are incorporated into this DPA by reference: Module 2 (controller to processor) where you are a controller, and Module 3 (processor to processor) where you are a processor. For those clauses: clause 7 (docking) applies; under clause 9 option 2 (general authorisation) applies with the notice period in section 7 of this DPA; the optional wording in clause 11 does not apply; under clause 17 and 18 the law and courts are those of Ireland; Annex I is completed by Annex 1, Annex II by Annex 2, and Annex III by Annex 3.
- UK Addendum. To the extent a transfer is a restricted transfer under the UK GDPR, the UK Addendum is incorporated by reference. Table 1 is completed with the parties' details in this DPA and the terms; Tables 2 and 3 by the EU SCC selections and annexes above; and in Table 4 either party may end the Addendum as its section 19 allows.
- Switzerland. For transfers from Switzerland, the EU SCCs apply with references to the GDPR read as references to the Swiss Federal Act on Data Protection, and the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority.
- If we are the data importer, we act as importer under these clauses. If the transfer rules change, we may switch to a valid alternative safeguard by updating this DPA.
14. United States privacy laws
Where the CCPA or another US state privacy law applies, we act as your service provider or processor. We will not: sell or share Customer Personal Data; keep, use or disclose it for any purpose other than providing the Service and the business purposes in the contract, or outside our direct business relationship with you; or combine it with personal data from other sources except as the law allows. We will tell you if we can no longer meet our obligations, and you may take reasonable steps to stop and remedy unauthorised use. We will comply with the obligations that apply to service providers under the CCPA and give the same level of privacy protection the CCPA requires of you. We will help you, by appropriate technical and organisational measures, to respond to consumer requests. We will bind any sub-processor that handles this data to the same restrictions by written contract. You may take reasonable and appropriate steps to make sure we use the data in line with your obligations, and to stop and remedy any unauthorised use. We certify that we understand these restrictions and will comply with them.
15. Liability and term
- Each party's liability under this DPA is subject to the limits in the terms of service, except where Data Protection Law does not allow liability to data subjects to be limited.
- This DPA lasts as long as we process Customer Personal Data for you.
Annex 1: Details of processing
| Item | Details |
|---|---|
| Data exporter | The Customer, as identified in its account or order form. Role: controller (or processor, for agencies acting for their clients). Contact: the account owner's email |
| Data importer | Scale It Up Media Ltd, trading as Namova, 10a High Street, Chislehurst, Kent, BR7 5AN, United Kingdom. Role: processor. Contact: [email protected] |
| Data subjects | Customer's users and staff; the agency's clients and their staff; people named in answers from AI Apps, web pages or connected data (such as business owners, founders, reviewers and journalists); people who contact the Customer through Customer-branded pages |
| Categories of personal data | Names, business contact details, job titles; user content and assistant chats; names and public statements appearing in AI answers and cited sources; review authors' names and review text from Google Business Profile; aggregated website and search metrics (not individual visitor records); API usage records |
| Special category data | None intended. The Customer must not upload special category data, and the Service is not designed for it. AI answers may occasionally contain it by chance; it is kept only as part of the measurement record |
| Nature and purpose | Hosting, storing, analysing and displaying data to provide the Service: AI visibility measurement, reports, drafted fixes, the in-app assistant, Google data connections, API and MCP access, and support |
| Frequency | Continuous, for as long as the Customer uses the Service |
| Duration and retention | The term of the contract, then deletion as in section 11 |
| Sub-processor transfers | As listed in Annex 3, for the purposes stated there, for the duration of the contract |
| Competent supervisory authority | For EU SCCs: the authority of the EU member state where the Customer is established or, if the Customer is not established in the EU and has no EU representative, the authority of the member state where the data subjects concerned are. For the UK: the Information Commissioner's Office |
Annex 2: Technical and organisational measures
- Encryption: TLS for data in transit; encryption at rest for databases, storage and backups provided by our hosting provider.
- Tenant isolation: every workspace's data is separated by row-level security policies in the database; access is checked on the server for each request.
- Secrets: API keys, OAuth tokens and other secrets are stored in an encrypted vault, separately from other data, and are never shown in the browser.
- Access control: staff access to production data is limited to what is needed, protected by strong, unique passwords, and reviewed when access changes.
- Least privilege: database roles are limited to the functions they need; public access to internal functions is revoked.
- Abuse prevention: bot checks, rate limits, per-connection limits and spending caps.
- Logging and monitoring: security and error logs, health checks and alerts for failures; logs kept up to 90 days.
- Backups and recovery: daily backups by our database provider, with restore procedures.
- Secure development: code review (including independent automated review) before release.
- Data minimisation: email addresses are never sent to AI providers; internet addresses are stored only as one-way scrambled codes for abuse limits; Google data is never sent to AI providers.
- Suppliers: sub-processors are chosen for their security and bound by data protection terms.
- Incident response: a documented process to contain, assess and notify within the times in section 10.
- Deletion: documented deletion procedures and scheduled clean-up of expired data.
Annex 3: Sub-processors
The named list of sub-processors, with each one's location and transfer safeguard, that we send you on request, together with the types listed on our Sub-processors page, forms this Annex. We keep the named list up to date under section 7.