Legal
Data Processing Agreement
Last updated: 29 October 2026
This Data Processing Agreement (“DPA”) is part of the Terms of Service between New Map (“New Map”, “Processor”) and the customer (“Client”, “Controller”). It governs the processing of personal data that the Processor carries out on the Client's behalf in providing the Service, in accordance with Article 28 GDPR and, where applicable, the UK GDPR and the Swiss FADP. A countersigned copy is available on request at privacy@thenewmap.ai.
1. Roles and scope
2. Annex 1: details of the processing
| Subject matter | Provision of the New Map AI visibility platform, agents, deliverables and, where ordered, distribution services. |
| Duration | The term of the Service plus the deletion period in section 9. |
| Nature and purpose | Storage, analysis and generation of text; collection and analysis of public AI engine answers; sending service email; operating the account manager and agents; producing deliverables; reporting. |
| Types of personal data | Identity and contact data of the Client's users (name, work email, company, role); hashed credentials; usage and technical data (IP, device, browser, actions); content the Client uploads or pastes (documents, decks, repositories, contracts) which may name staff, partners or customers; conversation content with the account manager; names and statements of people appearing in public AI answers and public sources about the Client's category; Google Analytics identity and reports where connected. |
| Categories of data subjects | The Client's users and staff; people named in material the Client provides; people named in public AI answers and public sources about the Client's category. |
| Special categories | None intended. The Client must not submit special-category data. |
| Storage location | The client database and authentication are hosted by Supabase on AWS in Ireland (EU), so client data is stored in the EU. Vercel functions and the AI providers run outside the EU, so processing is not EU-only. |
3. Instructions
4. Processor obligations
5. Personal data breach
6. Sub-processors and Annex 3
| Vendor | Service | Role | Location | Transfer safeguard |
|---|---|---|---|---|
| Vercel Inc. | Hosting, serverless functions, logs | Processor | USA | DPF (listed as Vercel Inc., active for EU, Swiss and UK, HR and non-HR data); SCCs as fallback |
| Supabase Pte. Ltd (contracting entity) and Supabase Inc. | Database, authentication (including 2FA), file storage, backups | Processor | Singapore company with a US affiliate; database and authentication hosted on AWS in Ireland (EU) | Data stored in the EU; not DPF-certified (not on the list); EU SCCs (Decision 2021/914) with UK and Swiss addenda in the Supabase DPA for any access from outside the EU |
| Anthropic, PBC (EEA contracting entity: Anthropic Ireland, Limited) | Language models for the account manager, agents, verifier, PDF parsing, bookkeeping extraction | Processor | USA (contract with the Irish entity for EEA customers) | Not DPF-certified (not on the list); SCCs Module Two or Three in the Anthropic DPA; commercial terms: Anthropic may not train models on Customer Content |
| LLM Pulse SL | Weekly collection of AI engine answers and citations | Processor | Spain (EU) | None needed |
| OpenAI OpCo, LLC (EEA contracting entity: OpenAI Ireland Ltd) | ChatGPT answers for audits and first-party measurement (Responses API with web search) | Processor | USA (contract with the Irish entity for EEA customers) | Not DPF-certified (not on the list); SCCs or an EU adequacy decision for transfers out of the EEA under the OpenAI DPA; Services Agreement: OpenAI will not use Customer Content to develop or improve the Services unless the customer agrees |
| Perplexity AI, Inc. | Perplexity answers for audits and first-party measurement | Processor | USA | DPF (listed as Perplexity AI for EU and UK, HR and non-HR data, on the official list on 13 October 2026); EU SCCs Module Two in the Perplexity DPA; API terms: Customer Content is not used to train, retrain or fine-tune models |
| Google LLC (Google Ireland Ltd. for Google Analytics; Google Cloud EMEA Ltd. for paid Gemini API contracts in EMEA) | Gemini API answers for audits; Google Analytics authorisation and reports when the client connects them | Processor | USA / Ireland | DPF (listed as Google LLC, active for EU, Swiss and UK, HR and non-HR data; covers Google LLC and its wholly owned US subsidiaries); SCCs; Gemini API terms: on Paid Services Google does not use prompts or responses to improve its products, and for developers in the EEA, Switzerland or the UK those paid-tier data terms apply to all use including unpaid quota |
| SpaceXAI LLC, trading as SpaceXSI (the xAI API, formerly xAI Corp.) | Grok answers for first-party measurement | Processor | USA | Not DPF-certified (not on the list); EU SCCs Module Two or Three with UK Addendum in the SpaceXSI DPA; enterprise terms: no User Content is used to train models and User Content is deleted within 30 days; the DPA requires personal data to be sent only through the Zero Data Retention API |
| Serper (serper.dev) | Google search results for agent research and grounding | Processor | See the provider's privacy policy | SCCs (the Serper privacy policy says EEA transfers rest on an adequacy decision or the standard contractual clauses) |
| Resend (Plus Five Five, Inc.) | Transactional and report email | Processor | USA (primary processing in the United States) | DPF (listed as Resend, legal name Plus Five Five; active for EU and UK, non-HR data only; re-certification under review); EU SCCs in the Resend DPA |
| Upstash, Inc. | Rate limiting, caching | Processor | USA; Redis region chosen per database | DPF (listed as Upstash, Inc., active for EU, Swiss and UK, HR and non-HR data); DPA with SCCs available |
| Cloudflare, Inc. | Turnstile bot check on the login, signup and contact forms (when enabled) | Processor | USA (data centres in the USA and Europe) | DPF (listed as Cloudflare, Inc., active for EU, Swiss and UK, HR and non-HR data; re-certification under review); SCCs as fallback in the Cloudflare DPA |
| Telegram Messenger Inc. (controller) and Telegram FZ-LLC | Internal notifications to New Map staff (company name, account and task events, no end-user content) | Processor | British Virgin Islands and Dubai, UAE; data of users who signed up from the EEA is stored in the Netherlands | Not DPF-certified (not on the list); Telegram's privacy policy relies on SCCs between its group companies; data minimised to company names and event types |
| Calendly LLC | Discovery-call booking on Calendly's pages | Independent controller | USA | DPF (listed as Calendly LLC, active for EU, Swiss and UK, non-HR data only; re-certification under review); SCCs and UK Addendum in Calendly's notice |
| Animoca Brands, Minds platform | Composition of account manager replies, where enabled | Processor | Hong Kong | SCCs |
| Hunter.io | Business contact lookup for New Map's own outreach; not used on client data | Processor for New Map's own data only | France (EU) | None needed |
Prompts and content we send to AI providers are processed under their business API terms. Anthropic, OpenAI, Perplexity and xAI do not use API inputs or outputs to train their models, and Google applies its paid-tier data terms to the Gemini API for developers established in the EEA, under which prompts and responses are not used to improve Google's products. We do not permit any provider to train a public model on your data.
7. International transfers
8. Audits
9. Return and deletion
10. Annex 2: technical and organisational measures (Article 32)
- Confidentiality, access control: access to production systems only for named staff with individual accounts and multi-factor authentication; two-factor authentication required for every New Map admin and team login and available to every Client user; least privilege; access reviewed when roles change; secrets kept in the hosting provider's encrypted environment store, never in code.
- Confidentiality, data separation: row-level security in the database so that each Client's records are readable only by that Client's users and by the Service acting for them; per-client scoping in every agent tool.
- Confidentiality, pseudonymisation and encryption: TLS 1.2+ in transit; encryption at rest at the database and storage providers; integration tokens encrypted with AES-256-GCM under a key held only in the environment store; passwords stored as salted hashes by the authentication provider.
- Integrity: signed and rate-limited API routes; a bot check on the public login, signup and contact forms where enabled; audit fields (who, when) on records; agent actions logged; a security log of logins and sessions that each Client can see on its Security tab; automated verification of generated content against the Client's data before it is shown.
- Availability and resilience: managed infrastructure with redundancy; the database and authentication hosted on AWS in Ireland (EU); automated encrypted database backups with point-in-time recovery at the provider, rotated within 30 days; rate limiting against abuse; monitoring and alerting on failures.
- Incident management: documented response procedure, breach assessment, notice under section 5, post-incident review.
- Processes: a record of processing activities; data protection review of new features and providers; staff instructed in data protection; sub-processor contracts under Article 28(4).