Skip to content
AppDues
Log in
Contact salesSign up

Data Processing Addendum (Archived)

This page preserves the data processing addendum that was effective from December 2025 until it was superseded in June 2026.

It is a historical reference only and is not the agreement currently in force. Readers who need the operative terms should consult the current addendum rather than rely on this archived text. The sections below walk through the parties, the processor duties, the sub-processor and transfer mechanics, the California service-provider terms, the customer's own responsibilities, and each annex, so the archived document can be read as a whole.

How the addendum fit into the customer agreement

The addendum formed part of the customer agreement, SaaS services agreement, terms of use, or another agreement under which a customer accessed the provider's products and services. Those products and services are referred to in the document as the Application Services. Capitalized terms not defined in the addendum took their meaning from the underlying agreement. The subject matter of the processing was the Application Services ordered by the customer, either through the provider's website or through an order, and provided to the customer via the provider's site or as otherwise described in the agreement or the addendum.

Key definitions

The document defined Data Protection Legislation broadly, covering applicable EU Data Protection Law, UK Data Protection Law, the California Consumer Privacy Act as amended by the CPRA, and the Brazilian LGPD. EU Data Protection Law included the GDPR, and UK Data Protection Law included the Data Protection Act 2018 and the UK GDPR. Customer Personal Data meant data defined as personal data or personal information under applicable law and processed by the provider under the agreement. Where Customer Data comprised personal data subject to the LGPD (LGPD Covered Data), Customer Personal Data as used in the addendum was deemed to include that LGPD Covered Data.

Which definitions applied where

The addendum split its defined terms by paragraph. In Paragraphs 1 through 11, Data Controller, Data Processor, Data Subject, Personal Data, Processing, Supervisory Authority and appropriate technical and organizational measures took their meaning from applicable Data Protection Legislation, and Customer Personal Data was limited to personal data of data subjects located in the EEA or the UK. In Paragraph 12, Service Provider, business, Consumer, business purpose, sell (and its variants) and subcontractor carried the meanings given in section 1798.140 of the CCPA. That split matters when reading the transfer and California sections: the same words can carry different statutory anchors depending on which paragraph you are in. The CCPA terms sat in Paragraph 13 and, to the extent of any conflict, superseded the other terms of the addendum with respect to CCPA Personal Data.

Customer instructions, processing scope and liability

By entering into the addendum, the customer instructed the provider to process Customer Personal Data in four ways: to provide the Application Services according to their features and documentation; to enable authorized user-initiated actions; as set out in the agreement and applicable order; and as further documented in written customer instructions. The provider agreed to notify the customer promptly if it became aware that an instruction might violate applicable Data Protection Legislation. Each party's aggregate liability arising out of or related to the addendum, including under the EU SCCs (as amended by the UK Transfer Addendum or as needed for a Swiss restricted transfer), whether in contract, tort or any other theory, was subject to the limitation-of-liability provisions of the agreement, except where that liability conflicted with the SCCs or was limited under Data Protection Legislation.

ConfigureTargetTest

Processor obligations

The provider committed to a set of processing terms. It would process Customer Personal Data only on documented customer instructions, and would inform the customer before processing for any other legally required purpose unless important public-interest grounds prohibited that notice. It would maintain appropriate technical and organizational measures proportionate to the risks, and could update those measures as long as the overall level of protection did not materially decrease. The provider also agreed to provide information reasonably requested by the customer to demonstrate compliance with the addendum.

Sub-processors

The provider could engage third-party Sub-Processors to process Customer Personal Data for delivering the Application Services, including those listed in Annex 3. Sub-Processors could use the data only to deliver the services they were retained for and were barred from other uses. The provider remained responsible for their compliance and required written agreements with terms no less protective than the addendum. Customers could request prior notification of sub-processor updates in writing; the provider would update the list within thirty days if no legitimate objection was raised in that period. Legitimate objections had to be documented and grounded in the sub-processor's non-compliance with applicable law. If the objection was accepted and the services could not be modified to avoid disclosure, the customer could terminate the agreement by written notice. Under the CCPA terms, the provider could also retain and employ other Service Providers as subcontractors where the subcontractor met the CCPA's requirements for a Service Provider and applicable regulations.

Data subject requests and regulatory assistance

At the customer's request and cost, the provider would reasonably assist with technical and organizational measures needed to respond to data subject requests, including access, rectification, erasure and portability, where legally permitted and where the request was made under relevant law. The provider could seek reimbursement for reasonable time, expenditure or fees. If a data subject contacted the provider directly, the provider would, where legally permissible, direct the request to the customer, who remained responsible for responding, including through the Application Services' functionality. The customer agreed that the provider could confirm to a data subject that the request related to the customer. Separately, the provider would take reasonable steps at the customer's request and cost to help the customer meet its obligations under Articles 32 to 36 of the GDPR, again with a right to reimbursement for reasonable time, expenditure or fees. In the event of a Personal Data Breach as defined in Annex 2, the provider would follow the incident response procedure set out in that annex.

Restricted Transfers: EU, UK and Swiss safeguards

For transfers of Customer Personal Data from the EEA to a country not deemed adequate under EU Data Protection Law (a Restricted Transfer), the provider made the EU Standard Contractual Clauses available as a safeguard, as amended, superseded or replaced from time to time. The EU SCCs and the paragraph's terms applied to the legal entity that executed them as data exporter and its participating affiliates, all treated as data exporters. Where a Restricted Transfer was made, the EU SCCs were incorporated into the addendum from the start of the transfer, with these modifications: module two (Controller to Processor) applied where the customer was a controller and module three (Processor to Processor) applied where the customer was a processor; Clause 7 did not apply; Clause 9, Option 2 applied and the provider could engage Sub-Processors as described in the sub-processor paragraph; the optional language in Clause 11 was deleted; the audits in Clauses 8.3 and 8.9 were carried out under the audit paragraph; under Clauses 8.5 and 16(d), data was returned or destroyed per the deletion paragraph; Clause 17, Option 1 applied with Irish law; disputes under Clause 18(b) went to the courts of Ireland; and the SCC annexes were populated from the addendum's annexes. For UK transfers, the International Data Transfer Addendum to the EU SCCs published by the UK Information Commissioner's Office on March 21, 2022, together with the EU SCCs as amended by it (the UK IDTA SCCs), was incorporated from the start of the transfer. The UK IDTA tables were populated from the addendum's annexes; for Table 2 the first tick box was deemed ticked and the date was the transfer start date; the UK IDTA SCCs were governed by the laws of England and Wales with disputes before those courts; and both Importer and Exporter were selected in Table 4. For a Swiss Restricted Transfer, the parties entered into the EU SCCs with these amendments: references to the GDPR were read as references to the Swiss Federal Data Protection Act; Clause 1c extended protection to personal data of legal entities until the revised FADP took effect on September 1, 2023; under Clause 13 the Swiss Federal Data Protection and Information Commissioner acted as competent authority for FADP matters, and for GDPR matters the authority of the member state where the Swiss exporter's Article 27(1) representative was established; and under Clause 18c data subjects habitually resident in Switzerland could bring proceedings before the competent Swiss courts. Where the EU SCCs (including as amended by the UK Transfer Addendum or for a Swiss transfer) conflicted with the addendum on transfers, the SCCs prevailed to the extent of the conflict.

ConfigureTargetTest

Audit and deletion mechanics

The provider would make information available to the customer on request that was necessary to demonstrate compliance with the addendum, and would allow audits and inspections by the customer or another auditor on reasonable, legitimate grounds for suspecting a breach. It would first provide a confidential summary report (an Audit Report) prepared by third-party security professionals at the provider's selection and expense. If the customer could show it needed more than the Audit Report and Data Protection Legislation required it, the provider would allow the customer and its auditors or authorized agents to inspect the provider's procedures relevant to protecting Customer Personal Data, no more than once every twelve months and at the customer's expense, to verify compliance during the agreement term. The customer had to give at least forty-five days' prior written notice, and the inspection had to occur during reasonable business hours with minimal disruption and last no longer than forty-eight hours. It could be carried out by the customer or an inspection body mutually agreed by the parties, composed of independent members with the required professional qualifications and bound by confidentiality. Customer representatives performing an audit had to protect the confidentiality of all information obtained, could be required to sign an enhanced mutually agreeable nondisclosure agreement, and had to follow the provider's security policies on its premises. After an audit, the customer had to promptly furnish any written audit report, or if none was prepared, promptly notify the provider of any non-compliance found. Audit results were treated as the provider's confidential information. No access to any part of the provider's IT systems, data hosting sites or centers, or infrastructure was permitted, and audits could not include information that could compromise confidential information about other customers or suppliers, the provider's proprietary technology or trade secrets. At the end of the applicable term, on the customer's request, the provider would securely destroy or return Customer Personal Data in its possession or control, subject to its standard data backup and archival practices. The request had to be made within thirty days of termination; after that the provider could permanently delete the data from its live systems.

Annex 1A: List of parties

Annex 1A listed the parties to the transfer. The data exporter was whichever customer entity the agreement or an applicable Ordering Document named, located at the address shown on the Ordering Document, with the notification contact the customer had nominated as described in the addendum. The exporter's relevant activity was using the importer's services as a customer under the agreement, and its role was controller and/or processor. The data importer was the owner's legal entity, at the owner's legal address, with the owner's designated contact person. The importer's relevant activity was supplying certain services to the exporter as described in the agreement, and its role was processor.

Annex 1B: Description of the transfer

Annex 1B set out the transfer description. The data subjects covered were people whose information was uploaded into the Application Services by the data exporter, by its authorized users, or by subsidiaries and other participants that the exporter had allowed to use those services under the agreement. The personal data categories consisted of whatever was uploaded into the Application Services in that same way, and the transferred data could include those categories without being limited to them. For sensitive data transferred, if any, and any restrictions or safeguards applied, the annex stated Not Applicable. Transfers occurred at the data exporter's discretion as it used the Application Services, throughout the agreement term. On the nature of processing, Customer Personal Data was to be handled under the agreement and any Ordering Document, and the basic activities could include: processing only as far as needed to deliver the services in line with both the agreement and the exporter's instructions, with the importer acting solely on the exporter's behalf, and operations spanning the provision of the Application Services and therefore potentially all aspects of the personal data processed; technical support, issue diagnosis and error correction so that systems ran efficiently and properly and so that technical problems could be identified, analyzed and resolved, both in general service delivery and in response to a specific exporter query, which might touch all aspects of the data but was to be confined to metadata where feasible; URL scanning in support of targeted threat protection and comparable services that might be supplied under the agreement, covering attachments and links in emails and any personal data inside them, potentially across all data categories; and disclosures made under the agreement when Data Protection Legislation compelled them. The transfer and further processing served the purpose of delivering the Application Services under the agreement and any applicable Ordering Document. Retention ran until the agreement ended or expired, following the deletion paragraph of the addendum.

Annex 1C: Competent supervisory authority

Annex 1C addressed which supervisory authority had competence. If the data exporter was established in an EU Member State, competence lay with the supervisory authority that oversees that exporter's compliance with Regulation (EU) 2016/679 in relation to the transfer. If the exporter was established outside the EU but came within Regulation (EU) 2016/679's territorial reach under Article 3(2) and had designated a representative under Article 27(1), competence lay with the supervisory authority of the Member State where that representative was established. If the exporter was established outside the EU, came within Article 3(2) territorial scope, and did not have to designate a representative under Article 27(2), competence lay with the supervisory authority of a Member State in which were located the data subjects whose personal data was transferred under these Clauses, whether in connection with offering goods or services to them or with monitoring their behavior.

ConfigureTargetTest
Sub-processors listed in Annex 3
Entity NamePurposeLocation
ElasticA cloud service that stores our server logs and provides searching capabilitiesUSA
Amazon Web Services, IncOur servers and production infrastructure. These include (but not limited to) ECS, RDS, Redshift, Elasticsearch, and Elasticache.USA
SentryError monitoring toolUSA
HoneycombObservability tool for our production infrastructureUSA
Snowflake Inc.Cloud based data warehouseUSA
CloudFlareServing user requests, caching, protecting against DOS attacksUSA

This list reflects the sub-processors named in the archived December 2025 addendum. It is a historical reference and should not be treated as the current sub-processor list.

Frequently asked questions

Is this addendum currently in force?

No. It was effective from December 2025 until it was superseded in June 2026. The page is provided for historical reference only.

Who was the controller and who was the processor?

The customer was the Data Controller and the provider was the Data Processor for Customer Personal Data.

What transfer safeguards did the addendum use?

It incorporated the EU Standard Contractual Clauses for restricted transfers from the EEA, the UK International Data Transfer Addendum for UK transfers, and amended EU SCCs for Swiss restricted transfers.

Could a customer audit the provider?

Yes, on reasonable and legitimate grounds for suspecting a breach. The provider would first make available a confidential summary audit report prepared by third-party security professionals. If more was needed and required by law, the customer or its auditors could conduct an inspection 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 for no longer than forty-eight hours. No access to IT systems, data hosting sites or infrastructure was permitted.

What happened to Customer Personal Data at the end of the agreement?

On the customer's request within thirty days of termination, the provider would securely destroy or return Customer Personal Data in its possession or control, subject to standard backup and archival practices. After that, the provider could permanently delete the data from live systems.

Which EU SCC module applied, and what clause changes were made?

Module two (Controller to Processor) applied where the customer was a controller and module three (Processor to Processor) where the customer was a processor. Clause 7 did not apply; Clause 9, Option 2 applied; the Clause 11 optional language was deleted; audits under Clauses 8.3 and 8.9 followed the audit paragraph; Clause 17, Option 1 applied with Irish law; and Clause 18(b) disputes went to the courts of Ireland.

What did the CCPA terms require of the provider?

The provider could use CCPA Personal Data only for the limited and specified purposes of providing services under the agreement, had to give it the same level of privacy protection the CCPA requires, and could not sell or share it, use it outside the direct business relationship, or combine it except as permitted. It had to notify the customer if it could no longer meet its CCPA obligations, and the CCPA paragraph superseded other terms in case of conflict.

What data could the customer not submit for processing?

The customer was responsible for ensuring that no Special Categories of Personal Data (GDPR Article 9 or the UK equivalent), personal data relating to criminal convictions and offenses (GDPR Article 10 or the UK equivalent), or Sensitive Personal Information under the CCPA was submitted for processing by the Application Services.

What did Annex 1B say about sensitive data and retention?

Sensitive data transferred was marked Not Applicable. Personal data was to be retained until termination or expiry of the agreement, in accordance with the deletion paragraph of the addendum.

What did Annex 1B say about the nature of processing?

Annex 1B listed the basic processing activities as provision of the Application Services, technical support and error correction (limited to metadata where possible), URL scanning for targeted threat protection relating to attachments and links in emails, and disclosures in accordance with the agreement as compelled by Data Protection Legislation. Sensitive data transferred was marked Not Applicable, and personal data was retained until termination or expiry of the agreement.

How did Annex 1C determine the competent supervisory authority?

If the data exporter was established in an EU Member State, that state's supervisory authority was competent. If the exporter was outside the EU but within Article 3(2) scope with an Article 27(1) representative, the authority of the Member State where the representative was established was competent. If the exporter was within Article 3(2) scope without a representative, the authority of a Member State where the affected data subjects were located was competent.

What security measures did Annex 2 describe?

Annex 2 covered need-to-know access limits, multi-factor authentication for cloud administrator access, SSH keys for external engineers, 128-bit AES in CBC mode with PKCS7 padding and HMAC-SHA256 for encryption, firewalls and patch management, AWS and Snowflake hosting controls, bug bounty programs, annual SOC 2 Type II attestation, breach notification contents, business continuity and personnel screening. Current certification and audit status is maintained by the owner.