1. About this agreement
This agreement ("Partner DPA") is between the agency that signs a partner order form with us ("the Agency", "you") and Scale It Up Media Ltd, trading as Namova, company number 15538327, 10a High Street, Chislehurst, Kent, BR7 5AN, United Kingdom ("Namova", "we", "us"). It forms part of our Agency partner terms and meets Article 28 of the UK GDPR and EU GDPR.
For the partner service it takes priority over our standard Data processing agreement. Anything it does not cover is governed by the standard one. If you need a signed copy, email [email protected].
2. Roles
- You are the controller of Client Data: personal data of your clients ("Clients") and their people that you put into the service or that the service collects for you (for example a Client's login). You decide how it is used. We are your processor: we use it only on your instructions.
- If you act for a Client as its processor, we are your sub-processor, and you confirm your contract with that Client allows you to use us.
- We are the controller only for data we need to run our relationship with you (your staff accounts, billing, security logs and abuse prevention).
3. Subject matter and duration
- Subject matter: measuring your Clients' brands, the reports and written changes you share with Clients, the client portal and its sign-in and service emails sent in your name, and the assistant shown to Clients.
- Duration: from the day the partner service starts until we have deleted or returned all Client Data under section 9.
4. Nature and purpose
We store, display, analyse and send Client Data only to provide the partner service: AI visibility measurement for your Clients' brands, reports, written changes, the client portal, client logins and invites, weekly and monthly emails, the assistant, connected Google data where a Client connects it, and support.
5. Data subjects and types of data
| Data subjects | Types of personal data |
|---|---|
| Your Clients' people who get a portal login | Name (if given), email address, role, which brands they can see, approvals and requests they make, messages they type to the assistant, and sign-in records, including internet address in security logs (kept up to 90 days); rate limits use a one-way scrambled code |
| Your own staff, for what they do in Client workspaces | Name and email address as shown to Clients, and what they do in Client workspaces (for example approvals and changes) |
| People named in measurement data | Names and public statements in AI answers and cited web pages (for example business owners, reviewers, journalists) |
| People in a Client's connected Google data | Review authors' names and review text from Google Business Profile; totals of website and search figures (no records of individual visitors) |
No special category data or data about children is intended. You must not put it into the service.
6. Your instructions
- We process Client Data only on your documented instructions. These terms, your settings in the app, and the actions your staff and Clients take in it are your instructions. If we think an instruction breaks data protection law, we tell you.
- If the law makes us process Client Data in another way, we tell you first, unless the law forbids it.
- Everyone at Namova and every contractor who can access Client Data is bound by confidentiality and has access only to what their job needs.
7. Security and sub-processors
- Security. We keep the measures in Annex 2 in place. We may change them only if the overall protection does not go down.
- Sub-processors. You give general authorisation for our sub-processors. The types we use are on our Sub-processors page. The named list (Annex 3) is sent to you when the partner service starts and again on request at [email protected]. You agree to keep it confidential, except to your advisers, auditors, regulators, your Clients where the law requires it, or a data subject using their rights.
- Changes. We email you at least 30 days before adding or replacing a sub-processor that handles Client Data. You may object within 14 days on reasonable data protection grounds, as section 7 of our standard data processing agreement describes. Each sub-processor is bound by written data protection terms at least as protective as this Partner DPA, and we stay responsible to you for it.
8. Helping you, and breaches
- Requests from people. If one of your Clients' people asks us directly to use a data protection right, we pass the request to you without undue delay and do not answer it ourselves, except to tell the person to contact you. We help you answer requests through the app's features and, where needed, by hand.
- Breach notice. We tell you about a personal data breach affecting Client Data without undue delay and in any case within 48 hours of becoming aware of it, with what we know: what happened, the kinds and rough number of people and records affected, the likely effects, what we have done or plan to do, and a contact. We send more detail as we learn it, help you meet your own duty to notify the regulator (within 72 hours) and the people affected, and take reasonable steps to contain the breach.
- Contacting your Clients. Because the service carries your brand, we do not contact your Clients about a breach ourselves unless you ask us to or the law requires it.
- Impact assessments. We give you the information you reasonably need for a data protection impact assessment or a consultation with a regulator about the partner service.
9. Deletion and return
- When the partner service ends, your portal addresses stop serving at once.
- For 30 days after the end you can export Client Data in a common machine-readable format (such as CSV or JSON) and download reports. You can also ask us to delete it sooner.
- After that, or straight away if you ask, we delete Client Data and all copies from the live service, including logos and other brand files in storage and Client logins, within 90 days of the end. Backup copies are overwritten within a further 30 days. We confirm deletion in writing on request.
- The exception is support concerns (a request for help or a complaint sent through the app, including by a Client in the portal). We keep these for 2 years after the conversation ends, as our Privacy policy sets out for support messages, so we can show how each was handled.
- We keep Client Data longer only where the law requires it, keep it confidential, and use it for nothing else.
10. Audits and information
- We make available the information you reasonably need to show we meet Article 28 of the UK GDPR and EU GDPR, including this Partner DPA, our security measures, the named sub-processor list and any independent security reports we hold.
- If that is not enough, or a regulator requires it, you (or an independent auditor bound by confidentiality who is not our competitor) may audit us once in any 12 months, with at least 30 days' written notice, during business hours and without unreasonable disruption. Audits are at your cost unless they show we have materially broken this Partner DPA. Audits of sub-processors are done through their own reports and certifications.
11. International transfers
- Client Data is processed in the United States (main database) and the other places the named sub-processor list shows.
- Transfers out of the UK or the European Economic Area are covered by the EU Standard Contractual Clauses (Module 2 where you are a controller, Module 3 where you are a processor) and, for UK transfers, the UK International Data Transfer Addendum, exactly as section 13 of our standard Data processing agreement sets out. That section applies to this Partner DPA too.
12. Liability and order of precedence
- Liability is limited as in our Terms of service, except where data protection law does not allow liability to people to be limited.
- If this Partner DPA and the EU Standard Contractual Clauses or the UK Addendum conflict, the Clauses and the Addendum win.
Annex 1: Details of processing
| Item | Details |
|---|---|
| Data exporter | The Agency, as named in the partner order form. Role: controller (or processor for its Clients). Contact: the agency account owner's email |
| Data importer | Scale It Up Media Ltd, trading as Namova (address above). Role: processor (or sub-processor). Contact: [email protected] |
| Data subjects and types | Section 5 |
| Special category data | None intended |
| Nature and purpose | Section 4 |
| Frequency | Continuous while the partner service runs |
| Retention | Section 9 |
| Sub-processors | Annex 3 |
| Supervisory authority | As Annex 1 of our standard data processing agreement (the ICO for UK transfers) |
Annex 2: Technical and organisational measures
The measures in Annex 2 of our standard data processing agreement, plus these for the partner service:
- Agency separation. Each agency's data is separated by row-level security in the database. A Client login sees only the brands it has been given in its own agency's workspace. A portal address shows only its own agency's data, and a login from another agency is signed out and refused.
- Portal addresses. Agencies' own (custom) addresses are not switched on yet. When they are, a custom address goes live only after proof of control by a DNS record unique to that address, and is checked again every day. An address whose proof lapses stops serving within 48 hours. Staff and operations screens are never served on a portal address.
- Sign-in emails. Signed requests only. Portal sign-in codes are sent from a neutral domain. Password-reset links always point at our own app address, never at a portal address, so a reset token cannot be captured on an address outside our control.
- Files. Logos and reports live in private storage. Links to them are signed and expire: links in emails within 30 days, links in the app within 10 minutes. Logos use random file names that reveal no internal identifiers.
- No tracking of Clients. Product analytics never runs on a portal address.
- Deletion. Removing an agency or workspace deletes its rows and queues its stored files for deletion. We monitor the queue and are alerted when deletions fall behind.
Annex 3: Sub-processors
The named list of sub-processors that handle Client Data, with each one's role, location and transfer safeguard, together with the types on our Sub-processors page, forms this Annex. We send it to you under section 7 and keep it up to date.