Data Processing Addendum
Effective Date: October 8, 2026
This Data Processing Addendum ("DPA") is part of the Terms of Service or other written agreement for the Services (the "Agreement") between Emra Tech, Inc. ("Emra") and the Customer. It applies whenever Emra processes Customer Personal Data on the Customer's behalf that is subject to Data Protection Laws, and it takes effect when the Agreement does. No signature is needed. Capitalized terms that are not defined here have the meanings given in the Agreement.
1. Definitions
- "Customer Personal Data": personal data in Customer Data that Emra processes on the Customer's behalf.
- "Data Protection Laws": the laws that apply to the processing of Customer Personal Data under the Agreement, including the EU General Data Protection Regulation ("GDPR"), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and the California Consumer Privacy Act ("CCPA") and other U.S. state privacy laws.
- "Security Incident": a breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data held by Emra or its Sub-processors.
- "Standard Contractual Clauses": the clauses annexed to European Commission Implementing Decision (EU) 2021/914.
- "Sub-processor": a third party Emra engages to process Customer Personal Data.
- "UK Addendum": the International Data Transfer Addendum to the Standard Contractual Clauses issued by the UK Information Commissioner, version B1.0.
"Controller," "processor," "data subject," "personal data," "processing," and "supervisory authority" have the meanings given in the GDPR. "Business," "service provider," "sell," and "share" have the meanings given in the CCPA.
2. Roles and Scope
The Customer is the controller of Customer Personal Data, or a processor acting for another controller, and Emra is its processor. Annex 1 describes the processing. Each party will comply with the Data Protection Laws that apply to it. This DPA does not cover the personal data Emra handles as a controller, such as account and billing information, which the Privacy Policy describes.
3. Customer Instructions
Emra processes Customer Personal Data only on the Customer's documented instructions. The instructions are the Agreement, this DPA, the Customer's and its Members' use and configuration of the Services, including what they ask Agents to do, and any other written instructions the parties agree. Emra will tell the Customer if it believes an instruction infringes Data Protection Laws. If the law requires Emra to process Customer Personal Data in another way, Emra will tell the Customer first unless the law prohibits it.
The Customer is responsible for the lawfulness of the Customer Personal Data it submits and of its instructions, including giving the notices and obtaining the consents the law requires, and for not submitting data the Acceptable Use Policy prohibits.
4. Confidentiality and Security
Emra limits access to Customer Personal Data to personnel who need it to perform the Agreement and who are bound by confidentiality obligations. Emra maintains the technical and organizational measures in Annex 2. Emra may update those measures as its systems and the threats to them change, and it will not materially reduce the overall level of protection during the Customer's subscription.
5. Security Incidents
Emra will notify the Customer without undue delay after becoming aware of a Security Incident. The notice will describe, to the extent known, the nature of the incident, the kinds and approximate amount of data and number of people affected, its likely consequences, and the steps Emra has taken or plans to take. Emra will add to the notice as it learns more, take reasonable steps to contain and remediate the incident, and give the Customer the information it reasonably needs to meet its own notification obligations. A notice is not an admission of fault.
6. Assistance
A. Data subject requests
The Services let the Customer access, correct, and delete Customer Personal Data, and Emra will give reasonable further help with requests from data subjects where the Customer cannot act on its own. If a data subject sends a request about Customer Personal Data to Emra, Emra will refer them to the Customer and will not respond further without the Customer's instruction, unless the law requires it.
B. Assessments and consultations
Taking into account the nature of the processing and the information available to it, Emra will give the Customer reasonable help with data protection impact assessments and with consultations with supervisory authorities that Data Protection Laws require.
C. Government requests
If a government body asks Emra for Customer Personal Data, Emra will direct it to the Customer where it can, notify the Customer before disclosing unless the law prohibits it, challenge a request it reasonably believes is unlawful, and disclose only what the request legally requires.
7. Sub-processors
The Customer gives Emra general authorization to engage Sub-processors. The current list is on the Sub-processors page. Emra binds each Sub-processor by written agreement to data protection obligations that give at least the protection this DPA requires, and Emra remains responsible to the Customer for each Sub-processor's performance.
Emra will add a new Sub-processor to that page, and email Customers who have subscribed to updates, at least 30 days before the Sub-processor begins processing Customer Personal Data. The Customer may object in writing within those 30 days on reasonable data protection grounds. The parties will work in good faith to resolve the objection. If they cannot, the Customer may end the affected Services before the Sub-processor begins processing, and Emra will refund prepaid fees for the period after termination. If Emra must replace a Sub-processor urgently to keep the Services secure or running, it will give notice as soon as it reasonably can.
8. International Transfers
Emra processes Customer Personal Data in the United States and in the locations shown on the Sub-processors page. Where the Customer's transfer of Customer Personal Data to Emra is restricted by Data Protection Laws, the terms below apply.
A. European Economic Area
The Standard Contractual Clauses are incorporated into this DPA and apply as follows: Module Two applies where the Customer is a controller, and Module Three where it is a processor; the optional docking clause in Clause 7 does not apply; Option 2 of Clause 9(a) applies, with the notice period in Section 7; the optional language in Clause 11(a) does not apply; under Clause 17, Option 1 applies and the law of Ireland governs; under Clause 18(b), the courts of Ireland have jurisdiction; Annex I is completed by Annex 1 of this DPA, Annex II by Annex 2, and Annex III by the Sub-processors page.
B. United Kingdom
For transfers subject to the UK GDPR, the UK Addendum is incorporated into this DPA and applies to the Standard Contractual Clauses as completed above. Tables 1 to 3 of the UK Addendum are completed by the information in this DPA and its Annexes, and in Table 4 neither party may end the UK Addendum under its Section 19.
C. Switzerland
For transfers subject to the Swiss Federal Act on Data Protection, the Standard Contractual Clauses apply as completed above, with references to the GDPR read as references to that Act, the Federal Data Protection and Information Commissioner as the supervisory authority, and "Member State" read so that data subjects in Switzerland may bring claims where they live.
D. Conflicts and other mechanisms
If the Standard Contractual Clauses or the UK Addendum conflict with the rest of this DPA or the Agreement, they control. If Emra adopts another transfer mechanism that Data Protection Laws recognize, that mechanism applies in their place to the transfers it covers.
9. U.S. State Privacy Laws
Where the CCPA or another U.S. state privacy law applies, Emra is the Customer's service provider or processor, and Emra:
- Will not sell or share Customer Personal Data.
- Will not keep, use, or disclose Customer Personal Data for any purpose other than the business purposes in the Agreement, which are providing, securing, and supporting the Services, or outside its direct business relationship with the Customer, except as those laws permit a service provider to do.
- Will not combine Customer Personal Data with personal data it receives from other sources, except as those laws permit a service provider to do.
- Will comply with the obligations those laws place on it, give Customer Personal Data the level of privacy protection they require, and tell the Customer if it decides it can no longer meet them.
- Agrees that the Customer may take reasonable and appropriate steps, on notice, to make sure Emra uses Customer Personal Data consistently with the Customer's obligations, and to stop and remediate any unauthorized use.
Emra certifies that it understands these restrictions and will comply with them.
10. Audits
Emra will make available to the Customer the information reasonably needed to show that it complies with this DPA. Emra meets this obligation by providing, under confidentiality, its current security documentation and any independent audit reports it holds, and by answering the Customer's reasonable written security questions no more than once a year.
Where that is not enough for the Customer to meet its obligations under Data Protection Laws, or a supervisory authority requires it, the Customer may audit Emra's processing of Customer Personal Data on at least 30 days' written notice, during business hours, no more than once a year, and at the Customer's expense. The auditor must be bound by confidentiality, must not be a competitor of Emra, and will not be given access to other customers' data. The parties will agree the scope and timing in advance.
11. Return and Deletion
The Customer may request deletion of its Workspace and Customer Personal Data by writing to support@emra.ai, subject to retention required by law. Canceling a subscription does not automatically delete the Workspace or its Customer Personal Data. Recovery backup retention is described in Terms of Service Section 15.C.
12. General
- Order of precedence. If this DPA conflicts with the Agreement, this DPA controls for the processing of Customer Personal Data, and Section 8.D applies to the Standard Contractual Clauses and the UK Addendum.
- Liability. Each party's liability under this DPA is subject to the limits in the Agreement. Nothing in this DPA or the Agreement limits either party's liability to data subjects under the Standard Contractual Clauses.
- Changes. Emra may update this DPA as the Agreement describes, and will not change it in a way that materially reduces the protection of Customer Personal Data during the Customer's subscription term.
- Governing law. The law and courts named in the Agreement apply to this DPA, except where the Standard Contractual Clauses or the UK Addendum provide otherwise.
- Contact. Send questions and notices about this DPA to privacy@emra.ai.
13. Annex 1: Details of Processing
| Item | Details |
|---|---|
| Data exporter | The Customer, at the contact details on its account or Order Form. Role: controller, or processor where it acts for another controller |
| Data importer | Emra Tech, Inc., 84 Crestview Ave, Daly City, CA 94015, United States, privacy@emra.ai. Role: processor |
| Subject matter | Providing the Services to the Customer under the Terms of Service |
| Duration | The term of the Customer's subscription, and afterward until Customer Personal Data is deleted under Section 11 |
| Nature and purpose | Hosting and storing Customer Data; sending it to AI model providers to generate Output; carrying out Agent actions, including through Connections; serving Published Apps; and supporting and securing the Services |
| Data subjects | The Customer's Members; people whose personal data appears in Customer Data, such as the Customer's employees, contractors, customers, contacts, and correspondents; and users of the Customer's Published Apps |
| Personal data | Whatever the Customer and its Members submit and Agents retrieve, such as names, contact details, account identifiers, the content of chats, files, email, messages, calendars, and documents, and other personal data in Customer Data |
| Special categories | None intended. The Acceptable Use Policy limits the sensitive data that may be submitted. Any that the Customer chooses to submit is protected by the measures in Annex 2 |
| Frequency of transfer | Continuous, for the duration above |
| Retention | As set out in Section 11 |
| Sub-processors | The sub-processors, purposes, and locations on the Sub-processors page, for the duration above |
| Supervisory authority | The authority that supervises the Customer under Clause 13 of the Standard Contractual Clauses |
14. Annex 2: Security Measures
- Separation. Each Customer's Workspace is logically separated from every other Customer's.
- Encryption. Customer Data is encrypted in transit over public networks and at rest, including in backups.
- Access control. Production access is limited to authorized personnel who need it, and everyone with access is bound by confidentiality obligations.
- Authentication. The Services offer multi-factor authentication and single sign-on.
- Credentials. Tokens for connected accounts are stored encrypted and are not held by Agents. The keys Emra uses to reach AI model providers are not exposed to Agents.
- Logging and monitoring. Security-relevant events are recorded in an audit log that Admins can review and export, and Emra monitors its security controls continuously.
- Backups. Workspaces are backed up regularly so they can be restored after a failure.
- Sub-processors. Emra engages Sub-processors only under written agreements that require them to protect Customer Personal Data.