Data Processing Addendum: Roles, Transfers and Annexes Explained
A data processing addendum (DPA) is the contract layer that sits under a main services agreement and governs how one party handles personal data on behalf of another.
It answers four practical questions: who decides why data is processed, what the processor may do with it, how cross-border transfers are protected, and what happens when the relationship ends. The archived version referenced below was effective from November 2023 and was superseded in December 2025; it is kept for historical reference and is not the current agreement.
Who is responsible for what
The core split is straightforward. The customer is the data controller; the service provider is the data processor. The customer must comply with applicable data protection law for the personal data it supplies, and the processor may act only on documented instructions. Those instructions cover providing the service, enabling user-initiated actions, following the agreement and order documents, and any further written directions the customer gives. If the processor becomes aware that an instruction may breach data protection law, it must tell the customer promptly.
The DPA also defines its own vocabulary. "Data Protection Legislation" is a broad umbrella that can include EU and UK data protection law, the CCPA as amended by the CPRA, and Brazil's LGPD. "Customer Personal Data" means data that qualifies as personal data or personal information under whichever of those regimes applies. Capitalized terms not defined in the DPA take their meaning from the main agreement. The archived addendum ties itself to the terms of use posted at the publisher's own terms URL; a new publisher must supply its own terms URL (OWNER_TERMS_URL) rather than inherit the archived one.
What the processor commits to
The processor's commitments fall into a handful of recurring duties. It must process personal data only on documented instructions, apply technical and organizational security measures appropriate to the risk, and remain responsible for any sub-processors it engages. Sub-processors may use the data only to deliver the service, must sign written terms no less protective than the DPA, and can be added to a published list. A customer who wants advance notice of new sub-processors can request it in writing; the processor then updates the list within thirty days unless the customer raises a legitimate, documented objection.
Assistance duties are conditional. The processor helps with data-subject requests and with the customer's obligations under GDPR Articles 32 to 36, but only at the customer's request and cost, and only so far as is possible. If a data subject contacts the processor directly, the processor should redirect them to the customer where the law allows. At the end of the service term, the processor securely destroys or returns personal data on request, subject to standard backup and archival practices; the request must be made within thirty days of termination.
Audits and breach response
Audit rights are tiered rather than open-ended. The processor first makes available a confidential summary report prepared by third-party security professionals at its own selection and expense. If the customer can show it needs more, and the law requires it, an on-site audit or inspection may follow — no more than once every twelve months, at the customer's expense, with at least forty-five days' prior written notice, during business hours, and capped at 48 hours. Auditors must protect confidentiality, may need to sign an enhanced nondisclosure agreement, and must follow the processor's security policies on site. No access to IT systems, hosting sites or infrastructure is granted, and the audit cannot reach information about other clients, proprietary technology or trade secrets.
On a personal data breach, the processor must take reasonable steps to limit harm and notify the customer in writing without undue delay once the breach is confirmed. Notice can be delayed where law enforcement asks or where investigation and remediation genuinely require it. Each notice should describe what happened, when it was discovered, the known scope, what data was or may have been accessed, and the response taken.
Cross-border transfer safeguards
For transfers out of the EEA to countries without an adequacy finding, the EU Standard Contractual Clauses are incorporated into the DPA. Module two (controller to processor) applies where the customer is a controller; module three (processor to processor) applies where the customer is itself a processor. Clause 9 Option 2 governs sub-processor engagement, the optional language in Clause 11 is deleted, audits follow the DPA's own audit paragraph, and Irish law and Irish courts govern disputes.
UK transfers use the International Data Transfer Addendum published by the UK Information Commissioner's Office on 21 March 2022, combined with the EU SCCs. The tables are populated from the DPA annexes, the first tick box in Table 2 is treated as ticked with the transfer commencement date, and England and Wales law and courts apply. Swiss transfers use the EU SCCs with modifications: references to the GDPR read as references to the Swiss Federal Data Protection Act, the FDPIC acts as supervisory authority where Swiss law applies, and Swiss-resident data subjects can bring proceedings in Switzerland. Where the SCCs conflict with the addendum on a transfer, the SCCs prevail to the extent of the conflict.
US state privacy and Brazilian law
Where the CCPA applies, the archived addendum records that the customer discloses personal data only for the limited purposes of receiving the service, and that the processor agrees not to sell or share that data, not to use it outside the direct business relationship, and not to combine it with data from other sources except for permitted business purposes. These are the archived processor's CCPA service-provider commitments; a new publisher's own CCPA terms must be supplied (OWNER_CCPA_TERMS) before this section describes current obligations. It may use another service provider as a subcontractor if that subcontractor meets CCPA requirements, and it may use the data internally to improve its services, to investigate security incidents, or for the purposes listed in California Civil Code section 1798.145. If a consumer sends a request to know or delete, the processor either acts for the customer or tells the consumer the request went to a service provider. This CCPA paragraph overrides conflicting terms elsewhere in the DPA.
For Brazil, if customer data includes personal data subject to the LGPD, that data is treated as Customer Personal Data under the DPA. The LGPD is listed among the laws that make up the DPA's Data Protection Legislation definition.
Customer duties, liability and term
The customer carries three specific responsibilities: it owns the customer data (subject to the processor's processing obligations), it gives any notices and collects any consents required by law from the people whose data appears in that data, and it ensures no special-category data under GDPR Article 9 or criminal-conviction data under Article 10 (or UK equivalents) is submitted for processing. The customer also must not let anyone outside its authorized users access the service, must not use it outside the ordering document, agreement and DPA, and must not use it for unlawful purposes.
Liability for the DPA, including under the SCCs, is aggregated across each party and its affiliates and is subject to the main agreement's limitation-of-liability clause — except where that would conflict with the SCCs or be limited by data protection law. The DPA terminates automatically when the main agreement terminates or expires, unless it has already been terminated earlier under its own terms.
How the annexes fit together
The annexes are where the DPA becomes specific. Annex 1A identifies the parties: the customer as exporter (controller and/or processor) and the data importer (processor), with contact details and a description of the activities; the archived addendum named a specific importer entity, address and compliance contact, so a new publisher must supply its own (OWNER_ENTITY_NAME, OWNER_COMPLIANCE_CONTACT). Annex 1B describes the transfer — categories of data subjects and personal data, sensitive-data status, frequency, nature of processing, purposes, and retention period; the archived addendum recorded sensitive data as not applicable, and a new publisher must confirm its own annex content (OWNER_ANNEX_1B). Annex 1C identifies the competent supervisory authority depending on where the exporter is established, following the archived addendum's three establishment scenarios. Annex 2 sets out technical and organizational measures, and Annex 3 lists sub-processors.
The archived addendum's Annex 2 security measures include unique logins with multi-factor authentication for cloud administrator access, individually assigned SSH keys for external engineers, need-to-know access limits, encrypted production credentials, a ban on storing customer data on portable devices, 128-bit AES in CBC mode with PKCS7 padding and SHA256 HMAC authentication, firewalls and network access controls, patch management, privileged-access monitoring, and reliance on AWS and Snowflake environmental controls. The archived addendum also records bug bounty programs and annual SOC 2 Type 2 audits by accredited third parties, while noting the processor was then in the process of being audited for SOC 2 Type II; a new publisher must confirm its own audit status (OWNER_SOC2_STATUS) and its own Annex 2 measures (OWNER_SECURITY_MEASURES). Business continuity, failover redundancy, employment verification and immediate access revocation on termination round out the annex.
| Entity Name | Purpose | Location |
|---|---|---|
| Elastic | A cloud service that stores our server logs and provides searching capabilities | USA |
| Amazon Web Services, Inc | Our servers and production infrastructure. These include (but not limited to) ECS, RDS, Redshift, Elasticsearch, and Elasticache. | USA |
| Sentry | Error monitoring tool | USA |
| Honeycomb | Observability tool for our production infrastructure | USA |
| Snowflake Inc. | Cloud based data warehouse | USA |
| CloudFlare | Serving user requests, caching, protecting against DOS attacks | USA |
This table reflects the archived addendum effective November 2023 to December 2025. Sub-processor lists change; check the current addendum for the live list.
Frequently asked questions
Is the customer the controller or the processor?
The customer is the data controller and the service provider is the data processor. Where the customer is itself a processor passing data through, module three of the EU SCCs applies instead of module two.
What counts as a legitimate objection to a new sub-processor?
An objection must be in writing and must give reasonable, documented grounds tied to the sub-processor's non-compliance with data protection law. A general preference for a different vendor is not enough. If the objection is legitimate and the service cannot be adjusted to avoid disclosing data to that sub-processor, the customer may terminate the agreement by written notice.
When must the customer request deletion of its data?
Within thirty days of termination. After that the processor may permanently delete the data from live systems. Standard backup and archival practices still apply to any copies held in backups.
Who pays for an audit?
The initial confidential summary report is prepared at the processor's selection and expense. Any further on-site audit or inspection is at the customer's expense and is limited to once every twelve months, with forty-five days' notice and a 48-hour cap.
Which terms win if the CCPA paragraph conflicts with the rest of the DPA?
The CCPA paragraph supersedes the other DPA terms for CCPA personal data. For transfer-related conflicts, the EU SCCs (including UK and Swiss amendments) prevail to the extent of the conflict.