Data Processing Addendum
This page explains, in plain structure, how customer personal data is handled when a customer uses application services: who controls it, who processes it, which safeguards apply to international transfers, how sub-processors and security are managed, and what happens when the service ends.
The version described is stated as effective June 2026, with the prior version available separately. Owner-specific legal identity, contact and address details are shown as configuration variables for the publishing owner to confirm.
What this DPA covers and how instructions work
The DPA sits inside the main customer agreement rather than standing alone. It applies when the customer accesses application services under that agreement, an order, or another document that incorporates the DPA by reference. Capitalised terms not defined in the DPA take their meaning from the main agreement.
Data Protection Legislation is defined broadly to cover EU and UK data protection law, California privacy law including the CCPA and CPRA, and Brazil's LGPD, as applicable to each party's performance. Customer Personal Data means data that counts as personal data or personal information under that legislation and that the processor handles under the agreement.
The customer instructs the processor to handle that data only to deliver the application services, to support authorised user actions, as the agreement and order describe, and as the customer further instructs in writing. If the processor believes an instruction may breach data protection law, it must tell the customer promptly.
Roles, scope and customer responsibilities
The customer is controller and the processor is its processor for customer personal data. The customer must comply with data protection law for all personal data it supplies. Processing covers the application services ordered through the website or an order and delivered via the service, as further described in the agreement and annexes, and lasts for the agreement term or until the ordering of the services ends.
In practice this split matters: the customer decides why data is processed and must give lawful instructions, notices and consents; the processor may only act on documented instructions. If the processor must process data for another purpose because applicable law requires it, it must inform the customer first unless that law prohibits notice on important public-interest grounds.
The customer remains solely responsible for the data it submits, for giving any required notices and obtaining consents from data subjects, and for not submitting special-category data, criminal-offence data, or CCPA sensitive personal information for processing through the services. It also must not let unauthorised people access the services or use them unlawfully or outside the order and agreement.
Security, assistance and audits
The processor must put in place and maintain suitable technical and organisational measures, proportionate to the state of the art, cost, nature, scope, context and risks of processing, to guard customer personal data against unauthorised or unlawful processing and against accidental loss, destruction, damage, theft, alteration or disclosure. Measures may be updated over time, but not in a way that materially lowers overall protection.
Help with data-subject requests is provided at the customer's request and cost where possible: the processor should reasonably assist with information, access, rectification, erasure and portability requests, and may seek reimbursement for reasonable time, expenditure or fees. If a data subject contacts the processor directly, the processor should, where legally allowed, direct that person to the customer, who answers the request, and the processor may confirm to the data subject that the request relates to the customer.
The processor also assists, at the customer's request and cost, with the customer's duties under GDPR Articles 32 to 36, again with reimbursement reserved. Compliance can be demonstrated through information and audits: the customer may review a confidential summary audit report prepared by third-party security professionals chosen and paid for by the processor. If more is needed and data protection law requires it, the customer may, at most once every 12 months and at its own expense, audit relevant procedures on at least 45 days' written notice during business hours with minimal disruption, for no more than 48 hours, using the customer or a mutually agreed independent inspection body bound by confidentiality. Auditors must protect confidentiality, may need an enhanced NDA, must follow site security policies, and must promptly report any non-compliance found. No audit gives access to IT systems, hosting sites, infrastructure, other customers' information, proprietary technology or trade secrets.
Sub-processors: notice, objection and exit
Other companies may be engaged to process customer personal data in order to provide the services, as listed in the sub-processor annex. They may use the data only for the retained service and for no other purpose. The processor remains responsible for their compliance, and each sub-processor must sign written terms at least as protective as the DPA.
To receive advance notice of additions, the customer can ask in writing using the owner contact variable {{OWNER_CONTACT_EMAIL}}. The list is updated within 30 days if no legitimate objection is raised in that window. A legitimate objection needs reasonable, documented grounds tied to non-compliance with data protection law. If the processor reasonably agrees the objection is legitimate and cannot modify the services to prevent disclosure, the customer may terminate the agreement by written notice.
Breach response in practice
If unauthorised access to or disclosure of customer data under the processor's control is discovered, the processor must take reasonable steps to limit harm and prevent further access or disclosure. Once the breach is confirmed, it must notify the customer in writing without undue delay, unless law prohibits notice or law enforcement asks for delay, or the processor needs time to investigate or remediate.
A useful breach notice therefore answers five questions: what data was used, accessed, acquired or disclosed; what happened, including breach and discovery dates if known; how far the breach reached; and what the processor did to respond and reduce harm. The annex also describes access controls, encryption, network and physical controls, independent security assessments, business continuity, and personnel checks as the security baseline behind that response.
International transfers: EU, UK and Switzerland
For EEA transfers to a country without an adequacy finding, EU Standard Contractual Clauses are incorporated from the start of the transfer. Module two applies where the customer is controller; module three applies where the customer is processor. Clause 7 does not apply, Clause 9 Option 2 applies so sub-processors may be engaged as described above, optional language in Clause 11 is removed, audits follow the DPA's audit paragraph, return or destruction on termination follows the DPA's end-of-term paragraph, Irish law governs under Clause 17 Option 1, and Irish courts handle disputes under Clause 18(b). The SCC annexes are filled from the DPA annexes.
For UK transfers, the UK International Data Transfer Addendum to the EU SCCs is incorporated and the combined UK IDTA SCCs apply from the start of the transfer. Their tables are populated from the DPA annexes, the first Table 2 box is treated as ticked with the transfer start date, England and Wales law governs, and both Importer and Exporter are selected in Table 4 of the UK addendum.
For Swiss transfers, the EU SCCs are amended so GDPR references read as the Swiss Federal Data Protection Act, legal-entity data is covered until the revised FADP takes effect on 1 September 2023, the FDPIC is competent for FADP transfers while the representative's member-state authority is competent for GDPR transfers, and Swiss data subjects may also sue in Switzerland. If the SCCs conflict with the DPA on a transfer, the SCCs prevail to that extent.
The competent supervisory authority depends on where the exporter is established and whether it has an EU representative; the annex sets out the three cases for exporters inside the EU, exporters with a representative, and exporters without one.
California and Brazil terms
Where LGPD-covered data is involved, it is treated as part of customer personal data under the DPA. For CCPA-covered data, the customer discloses it only for the limited, specified purpose of providing services under the agreement. Both parties must meet CCPA obligations and give CCPA personal data the same level of privacy protection the CCPA requires. The customer may take reasonable steps to check that the processor uses the data consistently with those obligations, and the processor must notify the customer if it can no longer meet them, after which it may take reasonable steps to stop and remedy unauthorised use.
The processor must not retain, use or disclose CCPA personal data for any purpose other than the business purposes in the agreement, must not sell or share it, must not use it outside the direct business relationship, and must not combine it with data from other sources except as the CCPA regulations allow for a business purpose. Narrow exceptions cover internal use to build or improve the quality of services for that customer, preventing or investigating security incidents or malicious, deceptive, fraudulent or illegal activity, and purposes listed in California Civil Code section 1798.145(a)(1)-(7). Other service providers may be used as subcontractors only if they meet CCPA service-provider requirements. If the processor receives a consumer privacy request, it must notify the customer and tell the consumer it cannot act on it. This CCPA paragraph overrides other DPA terms for CCPA data if they conflict.
Liability, term and a signing checklist
Liability under the DPA, including under the SCCs as amended, is subject to the main agreement's liability limits, except where that would conflict with the SCCs or be limited by data protection law. The DPA ends automatically when the main agreement ends or expires, unless it is terminated earlier under its own terms.
Before signing, run this checklist: confirm the controller/processor split for each data flow; check that no special-category, criminal-offence or sensitive data will be submitted; decide whether you need sub-processor advance notice and diary the 30-day objection window; map each transfer to EU, UK or Swiss clauses and the right SCC module; confirm audit notice, frequency and cost arrangements; and set a 30-day post-termination deadline for requesting return or destruction of data.
| Entity | Purpose | Location |
|---|---|---|
| Elastic | Logging and search service used to store server logs and enable searching and analysis to support monitoring and troubleshooting of our systems. | USA |
| Amazon Web Services, Inc | Cloud infrastructure provider used to host systems, run production systems, and store and process data required to operate our services. | USA |
| Sentry | Error monitoring service used to track, alert, and diagnose application errors to support system reliability and issue resolution. | USA |
| Honeycomb | Observability platform used to monitor and analyze system performance and behavior to support troubleshooting and performance optimization. | USA |
| Snowflake Inc. | Cloud data warehouse used to store and analyze data to support reporting, analytics, and business insights. | USA |
| CloudFlare | Content delivery and security service used to serve user requests, cache content, and protect our services from network attacks. | USA |
| Google LLC | Cloud infrastructure and analytics platform used to host production systems and provide internal dashboards for monitoring performance and business metrics. | USA |
| ScyllaDB, Inc. | Managed database service used to store and retrieve application data required for operating our services. | USA |
| Fastly, Inc. | Content delivery and security service used to serve user requests, cache content, and protect against network attacks. | USA |
| Hex | Data analytics and business intelligence platform used for internal reporting, analytics, and dashboard generation to support business operations. | USA |
| ClickHouse, Inc. | Cloud data warehouse used to store and analyze product and operational data to support reporting and analytics. | USA |
| OpenAI OpCo, LLC | AI service provider used to power product features that require automated analysis or content generation. | USA |
| Anthropic, PBC | AI service provider used to power product features that require automated analysis or content generation. | USA |
Sub-processor list as captured in Annex 3 of the source; owner must confirm the current list before publication.
Frequently asked questions
Who is controller and who is processor?
The customer acts as controller and the service provider acts as processor for customer personal data, except where a specific transfer module treats the customer as processor. That allocation determines who gives instructions, who answers data-subject requests, and who remains accountable for notices and consents.
How are new sub-processors handled?
Additional sub-processors can be added after written notification is requested. The list is updated within 30 days if the customer does not raise a legitimate, documented objection in that period. If an objection is legitimate and the service cannot be changed to avoid disclosure, the customer may terminate the agreement by written notice.
Which transfer safeguards apply by region?
For EEA transfers, EU Standard Contractual Clauses are incorporated, with module two for controller-to-processor and module three for processor-to-processor as applicable. UK transfers use the UK IDTA SCCs, and Swiss transfers use the EU SCCs with Swiss amendments. Where those clauses conflict with the DPA on the transfer itself, the clauses prevail to the extent of the conflict.
What must a breach notice contain?
After a confirmed breach, the processor must notify the customer in writing without undue delay, subject to legal prohibitions or a law-enforcement delay. The notice should describe what happened, when it happened and was discovered, the scope, what data was affected, and the response and mitigation steps taken.
What happens to data at the end of the term?
At the end of the service term, on request made within 30 days, the processor must securely return or destroy customer personal data in its possession or control, subject to standard backup and archival practices. After that request window, the data may be permanently deleted from live systems.