Legal

Data Processing Addendum

Last updated: November 17, 2026
Version date: November 17, 2026
This version applies only when expressly agreed under Section 17.1. Existing DPAs remain in effect until validly amended or replaced.

This Data Processing Addendum (the "DPA") applies between Axamy, Inc. ("Axamy") and a customer ("Customer") only when the parties expressly agree to it as described in Section 1. Once agreed, it forms part of the Axamy Terms of Service or other written services agreement between Axamy and Customer (the "Agreement"), for the processing covered by that agreement.

In the event of any conflict between this DPA and the Agreement regarding the processing of Personal Data, this DPA controls. The Standard Contractual Clauses and the UK Addendum incorporated under Section 12 control over this DPA to the extent of any conflict.

1. Introduction and Scope

This DPA applies only when Axamy and Customer expressly agree to it in a signed DPA, an Order Form, or another written agreement that specifically incorporates this DPA, including an electronic acceptance process expressly offered by Axamy for that purpose. Creating an account, accepting the standard Terms, using the Services, or being subject to a particular data-protection law does not by itself incorporate this DPA.

Once expressly agreed, this DPA governs Axamy's processing of Personal Data on Customer's behalf within the scope of the Agreement. References to the EU General Data Protection Regulation (Regulation (EU) 2016/679, the "EU GDPR"), the UK Data Protection Act 2018 and GDPR as it forms part of UK law (the "UK GDPR"), the Swiss Federal Act on Data Protection (the "Swiss FADP"), and the California Consumer Privacy Act, as amended by the California Privacy Rights Act (the "CCPA"), apply to the extent the relevant law applies to that processing. In a conflict concerning Personal Data, this DPA controls over the Agreement, and the Standard Contractual Clauses and UK Addendum incorporated under Section 12 control over this DPA.

Nothing in this DPA limits obligations imposed by applicable law. An existing DPA continues to govern according to its terms until validly amended or replaced; publishing this version does not itself withdraw existing contractual rights.

This DPA does not by itself authorize child-directed use, appoint Axamy as a FERPA school official, establish a regulated-sector compliance package, or commit Axamy to additional hosting locations. Those uses and commitments require the separate written arrangements described in Section 14.2.1 of the Terms.

2. Definitions

Capitalized terms used but not defined in this DPA have the meanings in the Agreement. For purposes of this DPA:

"Controller" means the natural or legal person, public authority, agency, or other body which, alone or jointly with others, determines the purposes and means of the processing of Personal Data; for the avoidance of doubt, Controller has the same meaning as "business" under the CCPA.

"Data Protection Law" means any law, regulation, or other binding requirement applicable to a party's processing of Personal Data, including the EU GDPR, the UK GDPR, the Swiss FADP, the CCPA, and other US state privacy laws of general application.

"Data Subject" means the identified or identifiable natural person to whom Personal Data relates; for the avoidance of doubt, Data Subject includes a "consumer" under the CCPA.

"Personal Data" means any information relating to an identified or identifiable natural person that is processed by Axamy in the course of providing the Services, as further described in Annex I; Personal Data has the meaning given by applicable Data Protection Law and, for the avoidance of doubt, includes "personal information" under the CCPA.

"Personal Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data transmitted, stored, or otherwise processed by Axamy.

"Processing" means any operation or set of operations performed on Personal Data, whether or not by automated means; "process," "processes," and "processed" have corresponding meanings.

"Processor" means a natural or legal person, public authority, agency, or other body which processes Personal Data on behalf of a Controller; for the avoidance of doubt, Processor has the same meaning as "service provider" under the CCPA.

"Standard Contractual Clauses" means the Standard Contractual Clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 approved by European Commission Implementing Decision (EU) 2021/914 of 4 June 2021, using Module Two (Controller to Processor) or Module Three (Processor to Processor), as specified in Section 12.1.

"Sub-processor" means any third party engaged by Axamy to process Personal Data in connection with the Services.

"UK Addendum" means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner, version B1.0, in force on 21 March 2022.

3. Roles of the Parties

The parties acknowledge that, for purposes of Data Protection Law and with respect to the Personal Data described in Annex I: (a) Customer is the Controller (or, where Customer is itself a processor acting on behalf of a third party, the relevant third party is the Controller and Customer is the processor) and (b) Axamy is the Processor.

Each party will comply with its obligations under applicable Data Protection Law. Customer is responsible for the lawfulness of its instructions to Axamy and for ensuring that the Personal Data it submits to the Services may lawfully be processed in the manner described in this DPA.

4. Subject Matter, Duration, Nature, and Purpose of Processing

The subject matter, duration, nature, and purpose of Axamy's processing of Personal Data, the types of Personal Data processed, and the categories of Data Subjects are set out in Annex I to this DPA.

5. Customer Instructions

Axamy will process Personal Data only on Customer's documented instructions, including with regard to transfers of Personal Data to a third country or an international organization, unless required to process Personal Data by applicable law. Where Axamy is required to process Personal Data by applicable law, Axamy will inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.

The Agreement, this DPA, and Customer's use of the Services constitute Customer's documented instructions to Axamy for the processing of Personal Data. Any additional or different instructions must be agreed in writing between the parties and may be subject to additional fees.

Axamy will inform Customer if, in Axamy's opinion, an instruction infringes applicable Data Protection Law.

6. Confidentiality of Personnel

Axamy will ensure that personnel authorized to process Personal Data are bound by appropriate confidentiality obligations (whether by contract or statute) and have received appropriate training in the protection of Personal Data. Axamy will limit access to Personal Data to personnel who need it to perform their roles.

7. Security Measures

Axamy will implement and maintain appropriate technical and organizational measures to protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access. The measures Axamy maintains as of the effective date of this DPA are set out in Annex II.

Axamy may update its technical and organizational measures from time to time, provided that any update does not materially diminish the overall level of protection of Personal Data.

8. Sub-processors

8.1 General authorization

Customer provides general written authorization for Axamy to engage the Sub-processors on the agreed, identifiable list described in Annex III, subject to this Section 8. That list must be completed and incorporated into the parties' written agreement before processing under this DPA begins. For Module Three transfers, the authorization must also satisfy the relevant controller's instructions and the applicable Standard Contractual Clauses.

8.2 Sub-processor obligations

Where Axamy engages a Sub-processor for processing activities on behalf of Customer, Axamy will enter into a written contract with the Sub-processor that imposes data-protection obligations no less protective than those in this DPA, to the extent applicable to the nature of the services provided by the Sub-processor.

8.3 Notice and objection

Axamy will give Customer written notice of an intended addition or replacement of a Sub-processor that will process Customer's Personal Data, including its identity, activities, and processing locations, at least fourteen (14) days before that processing begins. Axamy will send notice to Customer's designated privacy contact or account email and update the agreed list. Customer may object within that period on reasonable data-protection grounds by emailing privacy@axamy.com. The parties will work in good faith to resolve the objection. Axamy will not disclose the objecting Customer's Personal Data to the proposed Sub-processor while a timely objection remains unresolved. Axamy may continue using the existing arrangement or suspend the affected functionality where necessary. If the parties cannot reasonably resolve the objection, either party may terminate the affected portion of the Services by written notice, and Axamy will refund prepaid Fees for the unused terminated period. Any mandatory rights under applicable law or the transfer clauses remain in force.

8.4 Liability for Sub-processors

Axamy remains liable for the acts and omissions of its Sub-processors to the same extent Axamy is liable for its own acts and omissions under this DPA.

9. Data Subject Rights

Axamy will, taking into account the nature of the processing, assist Customer by appropriate technical and organizational measures, insofar as possible, in the fulfillment of Customer's obligations to respond to requests from Data Subjects to exercise their rights under Data Protection Law, including rights of access, rectification, erasure, restriction of processing, data portability, and objection.

If Axamy receives a request from a Data Subject relating to Personal Data processed under this DPA, Axamy will, without undue delay, forward the request to Customer and will not respond to the request directly except as required by law or on Customer's documented instructions.

10. Personal Data Breaches

Axamy will notify Customer without undue delay and no later than seventy-two (72) hours after becoming aware of a confirmed Personal Data Breach affecting Personal Data processed under this DPA, or earlier if applicable law requires. The seventy-two-hour ceiling is not a waiting period. The initial notice will, to the extent the relevant information is then known:

  • describe the nature of the Personal Data Breach, including, where possible, the categories and approximate number of Data Subjects and records concerned;
  • communicate the name and contact details of an Axamy contact from whom more information can be obtained;
  • describe the likely consequences of the Personal Data Breach; and
  • describe the measures taken or proposed to be taken by Axamy to address the Personal Data Breach and to mitigate its possible adverse effects.

Where Axamy cannot provide all of the above information at the time of initial notification, it will provide the information in phases without further undue delay.

Axamy will reasonably cooperate with Customer in connection with Customer's obligations under Data Protection Law to notify Personal Data Breaches to supervisory authorities and affected Data Subjects.

11. Data Protection Impact Assessments and Prior Consultation

Axamy will, taking into account the nature of the processing and the information available to Axamy, provide reasonable assistance to Customer with any Data Protection Impact Assessment Customer is required to conduct under applicable Data Protection Law and with any prior consultation with a supervisory authority that Customer is required to conduct as a result of such an assessment.

12. International Data Transfers

12.1 EU and EEA transfers

Where Axamy processes Personal Data subject to the EU GDPR in a country outside the European Economic Area that is not the subject of an adequacy decision by the European Commission, the parties incorporate by reference Module Two (Controller to Processor) where Customer acts as a controller, or Module Three (Processor to Processor) where Customer acts as a processor, of the Standard Contractual Clauses, to the extent those clauses are applicable to the transfer. Customer is the "data exporter," and Axamy is the "data importer," and the parties agree to comply with the Standard Contractual Clauses as if they were signatories.

For the purposes of the Standard Contractual Clauses: (a) Clause 7 (Docking) is not selected; (b) for Clause 9 (Use of sub-processors), Option 2 (general written authorization) is selected, with the time period for prior notice set out in Section 8.3 of this DPA; (c) for Clause 11 (Redress), the optional language requiring independent dispute resolution is not selected; (d) for Clause 17 (Governing law), the parties select the law of Ireland; (e) for Clause 18 (Choice of forum and jurisdiction), the parties select the courts of Ireland; (f) Annexes I, II, and III of the Standard Contractual Clauses are completed by the corresponding Annexes of this DPA.

Before a covered transfer begins, the parties must confirm the applicable module and complete the transfer details, including party contacts, signatures or other valid execution, the relevant controller for Module Three, the competent supervisory authority under Clause 13, and any supplementary safeguards required for the transfer. The applicable module's requirements remain in force in full.

12.2 UK transfers

Where Axamy processes Personal Data subject to the UK GDPR in a country outside the United Kingdom that is not the subject of UK adequacy regulations, the parties incorporate the UK Addendum and complete it by reference to the Standard Contractual Clauses as incorporated under Section 12.1. For the purposes of the UK Addendum: (a) Tables 1, 2, and 3 are completed by the corresponding sections of this DPA; (b) Table 4 specifies that neither party may end the UK Addendum as described in Section 19 of the UK Addendum.

12.3 Swiss transfers

Where Axamy processes Personal Data subject to the Swiss FADP, the Standard Contractual Clauses apply as adapted by the Federal Data Protection and Information Commissioner of Switzerland, with references to the EU GDPR construed as references to the Swiss FADP and references to EU Member States construed as references to Switzerland.

12.4 Other transfers

Where Personal Data subject to other Data Protection Law is transferred internationally, the parties will cooperate in good faith to implement any transfer mechanism required by that law.

13. CCPA-Specific Provisions

Where Customer is a "business" and Axamy is a "service provider" under the CCPA:

  • Axamy will process Personal Data only for the limited and specified purposes described in this DPA and in the Agreement;
  • Axamy will not retain, use, or disclose Personal Data for any purpose other than the specific purpose of performing the Services, including not retaining, using, or disclosing Personal Data outside of the direct business relationship between Axamy and Customer, except as permitted by the CCPA;
  • Axamy will not "sell" or "share" Personal Data within the meaning of the CCPA;
  • Axamy will not combine Personal Data received from Customer with Personal Data Axamy receives from or on behalf of another person or that Axamy collects from its own interaction with Data Subjects, except as expressly permitted by the CCPA;
  • Axamy will notify Customer if Axamy determines that it can no longer meet its obligations under the CCPA, and Customer may, upon notice, take reasonable and appropriate steps to stop and remediate Axamy's unauthorized use of Personal Data; and
  • Axamy grants Customer the right to take reasonable and appropriate steps to ensure that Axamy uses Personal Data in a manner consistent with Customer's obligations under the CCPA.

14. Deletion and Return of Personal Data

At Customer's choice, Axamy will delete or return Personal Data processed on Customer's behalf, and delete existing copies, without undue delay after the Services relating to that processing end, except to the extent applicable law requires storage. Customer should provide its return or deletion instructions before the Services end. If Customer gives no return instruction, deletion is the default. The parties may agree a reasonable handover and completion schedule in writing, subject to applicable law; the general export-request window and non-automatic-deletion provisions in Section 19.4 of the Terms do not displace this obligation.

Axamy will communicate applicable deletion or return instructions to its Sub-processors and require completion under their contracts. Residual backup copies may remain only until deletion through the applicable documented backup cycle to the extent permitted by law and the incorporated transfer clauses; while retained, they remain protected, isolated from ordinary use, and processed only for permitted disaster recovery or legally required storage. If restored, the deletion instruction will be reapplied. Debugging traces and active logs are not treated as backups merely to avoid a deletion obligation.

Axamy will confirm completion on Customer's reasonable written request, identify any legally required retention and its basis unless prohibited by law, and continue to protect any retained Personal Data. A shorter legal or expressly agreed deadline controls. This Section is independent of the general subscription-retention rule and does not authorize indefinite retention pending Customer instructions.

15. Audits

Axamy will make available information reasonably necessary to demonstrate compliance with this DPA and allow and contribute to audits to the extent required by applicable Data Protection Law or the incorporated transfer clauses. Routine requests should begin with a reasonable questionnaire and any relevant independent reports or summaries Axamy has available. Routine questionnaires and audits are ordinarily limited to once in twelve (12) months, unless there is good cause, an indication of noncompliance, a relevant Personal Data Breach, or a legal or supervisory-authority requirement.

Where the information reasonably available is insufficient, Customer may conduct an audit or appoint a qualified independent auditor under appropriate confidentiality and security obligations. Routine on-site audits require at least sixty (60) days' written notice and take place during regular business hours. For an incident, credible indication of noncompliance, or regulatory request requiring earlier access, that notice period does not apply; the parties will arrange access without undue delay on notice reasonable in the circumstances, subject to any mandatory deadline. These procedures do not limit supervisory-authority powers or rights under the Standard Contractual Clauses.

Audits must be proportionate, protect other customers' information, and avoid unreasonable disruption or unauthorized testing of production systems. Axamy may provide relevant security-testing results through confidential summaries, redactions, or independent reports where these supply sufficient evidence; it will not withhold information necessary to satisfy mandatory audit rights merely because it concerns internal testing. Customer bears its audit costs and Axamy's reasonable support costs, except where an audit establishes Axamy's material noncompliance, when Axamy bears its own support costs. Confidential commercial information unrelated to the audit is excluded.

16. Liability

The liability of each party arising out of or in connection with this DPA is subject to the limitations and exclusions of liability set out in the Agreement. For the avoidance of doubt, where the Standard Contractual Clauses apply, nothing in this DPA or the Agreement limits a Data Subject's rights under the Standard Contractual Clauses or limits Axamy's liability to Data Subjects under the Standard Contractual Clauses.

17. Term, Conflict, and Miscellaneous

17.1 Term

This DPA takes effect when the parties expressly agree to it under Section 1, or on another effective date specified in that agreement, and remains in effect for as long as Axamy processes Personal Data on Customer's behalf within its scope.

17.2 Order of precedence

In the event of a conflict between this DPA and the Agreement regarding Personal Data, this DPA controls. The Standard Contractual Clauses and the UK Addendum control over this DPA to the extent of any conflict.

17.3 Severability and survival

If any provision of this DPA is found unenforceable, the rest of the DPA remains in effect. Provisions that by their nature should survive termination will survive.

17.4 Governing law

This DPA is governed by the law specified in the Agreement, except as required by Data Protection Law (including the law specified in the Standard Contractual Clauses for matters governed by those clauses).

17.5 Notices

Privacy inquiries and requests may be sent to privacy@axamy.com or to Axamy, Inc., Attn: Privacy, 2030 Vallejo Street, San Francisco, California 94123, United States.

Notices under this DPA should be sent to privacy@axamy.com for Axamy and to the email address on Customer's account for Customer.

Annex I — List of Parties and Description of Processing

A. List of parties

Data exporter (Controller or Processor). Customer, as identified in the applicable order or account. Customer's contact for data-protection matters is the contact set out in Customer's account. Customer's role is Controller (or processor on behalf of a Controller, as applicable). Customer's activities relevant to the data transferred under the Standard Contractual Clauses are Customer's use of the Axamy Services as described in the Agreement.

Data importer (Processor). Axamy, Inc., 2030 Vallejo Street, San Francisco, California 94123, United States. Privacy contact: privacy@axamy.com. Axamy's role is Processor. Axamy's activities relevant to the data transferred under the Standard Contractual Clauses are processing of Personal Data on behalf of Customer in connection with the Services.

B. Description of processing

Categories of Data Subjects. Customer's Authorized Users; End Individuals about whom Customer chooses to process information through the Services, including, as applicable, Customer's employees, contractors, students, members, partners, and other people whose work Customer orchestrates through the Services; and individuals identified in Customer Data ingested from Connected Services.

Categories of Personal Data. As determined by Customer's use of the Services, which may include identifiers (names, email addresses, usernames, account IDs); contact information; professional information (titles, roles, reporting relationships); communications content (emails, messages, meeting notes); calendar and scheduling data; task, project, and work-tracking data; documents and other content submitted to or retrieved from Connected Services; capability and assessment data generated within the Services; profile and behavioral signals inferred from the foregoing; and technical identifiers (IP addresses, device identifiers, log data).

Sensitive Data. Customer will not submit Sensitive Data to the Services except as expressly permitted by the Agreement. Where Customer is permitted to submit categories of Sensitive Data, the parties will agree the applicable restrictions and safeguards in writing.

Frequency of transfer. Continuous, for the duration of Customer's use of the Services.

Nature and purpose of processing. Axamy will process Personal Data to provide, secure, maintain, and improve the Services for Customer; to enable AI Agents to plan, orchestrate, execute, and communicate work and to build or verify individual capabilities; to operate Connectors and process data flowing through them; to prevent and address technical, security, or abuse issues; to enforce the Agreement; and to comply with law.

Duration of processing. For the term of the relevant Services and the limited return, deletion, or legally required retention period described in Section 14 of this DPA.

C. Competent supervisory authority

For the purposes of Clause 13 of the Standard Contractual Clauses, the competent supervisory authority is the supervisory authority of the EU Member State in which Customer is established or, where Customer is not established in the European Union, the supervisory authority designated in accordance with Clause 13(a) of the Standard Contractual Clauses.

Annex II — Technical and Organizational Measures

Axamy maintains the following technical and organizational measures to protect Personal Data, as of the effective date of this DPA. Axamy may update these measures over time, provided that any update does not materially diminish the overall level of protection.

1. Pseudonymization and encryption

  • Data in transit between Users, Axamy, and Connected Services is encrypted with TLS 1.2 or above.
  • Personal Data stored in Axamy's AWS RDS databases is encrypted using AES-256 with AWS KMS. Other service providers use their own storage systems and encryption implementations. Their handling of Personal Data remains subject to the confidentiality, security, and data-protection requirements of this DPA and the Agreement; this AWS RDS statement does not describe every provider's stored copies.
  • Connector tokens and other secrets are encrypted at rest.

2. Confidentiality, integrity, availability, and resilience

  • Production systems are hosted with reputable cloud-infrastructure providers in the United States.
  • Customer data is separated by workspace in the application. Internal service routes require a secret key that is restricted to named staff and rotated when any of them leaves.
  • Production access is restricted to authorized Axamy personnel.
  • Axamy maintains backup procedures and supports recovery from common failure modes.

3. Regular testing, assessment, and evaluation

  • Axamy reviews the effectiveness of its technical and organizational measures from time to time and adjusts them based on the evolving risk landscape.
  • Axamy investigates suspected vulnerabilities reported to security@axamy.com or through the security reporting page.

4. Personnel and contractual controls

  • Axamy requires its personnel with access to Personal Data to be bound by appropriate confidentiality obligations.
  • Axamy provides personnel with appropriate training on data protection and information security.
  • Axamy contractually requires Sub-processors to handle Personal Data consistently with this DPA, to the extent applicable to the Sub-processor's services.

5. Incident response

  • Axamy maintains a process to detect, investigate, contain, and respond to security incidents.
  • Axamy notifies Customer of Personal Data Breaches following awareness as set out in Section 10.

6. Data minimization, accuracy, and retention

  • Axamy processes Personal Data only as needed to provide the Services to Customer and on Customer's documented instructions.
  • Axamy supports Customer's ability to correct or remove Personal Data through the Services or by request to privacy@axamy.com.
  • Axamy deletes or returns Personal Data at the end of the Services as described in Section 14.

Annex III — Sub-processors

The initial authorized Sub-processors must be identified in a dated or versioned schedule supplied to Customer and expressly incorporated into the signed DPA, Order Form, or other written acceptance of this DPA. Before processing under this DPA begins, that schedule must specify each relevant provider's legal identity, processing activities, categories of Personal Data, and processing locations. It must identify the providers used for Customer's enabled features and, for Module Three transfers, comply with the relevant controller's authorization.

The provider table in the Privacy Policy is a source of information for preparing that schedule. It also describes providers used for Axamy's own website, marketing, account, and billing purposes; it is not, by itself, the agreed list of Sub-processors for every Customer. A provider acting independently for Axamy's own purposes is not classified as Customer's Sub-processor merely because it appears in that table. A completed customer schedule is required rather than inferring authorization from provider categories.

The parties will retain the agreed schedule and identify later changes by written notice under Section 8.3. Axamy will provide the current applicable schedule on request to privacy@axamy.com. Primary Workspace hosting in the United States does not establish that every Sub-processor's processing or support access occurs exclusively there. The agreed schedule and any expressly agreed location restrictions govern those details.