Data Processing Agreement
Last updated November 4, 2026
Draft template. Have qualified legal counsel review and complete this document before launch. Text in [BRACKETS] must be replaced.
Effective date: [Effective date]
This Data Processing Agreement ("DPA") forms part of the Terms of Service between esacode, LLC, [Registered address] ("Processor", "EsaSim") and the customer that accepts the Terms ("Controller", "Customer"). It applies where EsaSim processes personal data on behalf of the Customer in providing the Service.
1. Definitions
"Data Protection Law" means all laws applicable to the processing of personal data under this DPA, including, where applicable, the EU General Data Protection Regulation 2016/679 ("GDPR") and the UK GDPR. "Personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meanings given in the GDPR. "Customer Personal Data" means personal data in Customer Content that EsaSim processes on the Customer's behalf.
2. Scope and roles
The Customer is the controller and EsaSim is the processor of Customer Personal Data. EsaSim is an independent controller for account, billing and security data as described in its Privacy Policy.
The Service is designed so that datasets and large job outputs remain on Workers that the Customer controls. EsaSim does not have access to data stored only on Workers. The Customer is responsible for processing that takes place on its own Workers.
3. Details of processing
| Item | Description |
|---|---|
| Subject matter | Provision of the EsaSim Service |
| Duration | The term of the Terms of Service plus the deletion period in Section 10 |
| Nature and purpose | Hosting, storage, transmission and display of job metadata and organization data to coordinate jobs on Customer Workers |
| Categories of data | Names and email addresses of members and invitees; user identifiers in job metadata, logs and audit entries; IP addresses; any personal data the Customer includes in job names, parameters, log lines or small output files |
| Data subjects | Customer's members, invitees and other individuals whose data the Customer includes in Customer Content |
| Special categories | None intended. The Customer must not submit special categories of data to the Service without prior written agreement. |
4. Processor obligations
EsaSim will:
- Process Customer Personal Data only on documented instructions from the Customer, including those in the Terms and given through the Service, unless required by law. EsaSim will inform the Customer if an instruction appears to infringe Data Protection Law.
- Ensure that personnel authorized to process Customer Personal Data are bound by confidentiality.
- Implement the security measures in Annex A.
- Assist the Customer, taking into account the nature of processing, in responding to data subject requests and in meeting its obligations on security, breach notification, impact assessments and prior consultation.
- Make available information reasonably necessary to demonstrate compliance with this DPA.
5. Customer obligations
The Customer is responsible for the lawfulness of the processing, for providing required notices and obtaining required consents, and for the accuracy of Customer Personal Data. The Customer is responsible for the security of its Workers and of data stored on them.
6. Sub-processors
The Customer gives general authorization for EsaSim to engage sub-processors. Current sub-processor categories are:
- Hosting provider: infrastructure for the website, database and backups. [Name and location]
- Stripe: payment processing and billing for the Customer's subscription.
- Email delivery provider: transactional email such as invitations and notifications. [Name and location]
EsaSim will impose data protection obligations on each sub-processor that are no less protective than this DPA. EsaSim will notify the Customer of new or replacement sub-processors at least [30] days in advance. The Customer may object on reasonable data protection grounds. If the parties cannot resolve the objection, the Customer may terminate the affected Service and receive a refund of prepaid fees for the remaining period.
7. International transfers
Where Customer Personal Data is transferred to a country without an adequacy decision, the parties agree that the Standard Contractual Clauses approved by the European Commission (and, for UK transfers, the UK Addendum) apply and are incorporated by reference. [Counsel to specify modules, options and annexes.]
8. Personal data breaches
EsaSim will notify the Customer without undue delay, and in any case within [48] hours, after becoming aware of a personal data breach affecting Customer Personal Data. The notice will include, as far as known, the nature of the breach, the categories and approximate number of data subjects and records concerned, likely consequences and measures taken or proposed. EsaSim will take reasonable steps to contain and remediate the breach.
9. Audits
EsaSim will respond to reasonable written questionnaires about its security and compliance. Where these are not sufficient, the Customer may conduct an audit, at its own cost, no more than once per year, with at least [30] days' notice, during business hours and subject to confidentiality. EsaSim does not currently hold third-party security certifications. SOC 2 and ISO 27001 are on the roadmap. When available, reports may be provided in place of audits.
10. Deletion and return
The Customer can export data and delete its account through the Service. On termination, EsaSim will delete Customer Personal Data within [30] days, except where retention is required by law. Data in backups is deleted as backups are overwritten within [number] days. Data on the Customer's Workers is under the Customer's control and is not affected.
11. Liability and precedence
Liability under this DPA is subject to the limitations in the Terms, unless Data Protection Law provides otherwise. If this DPA conflicts with the Terms on data protection matters, this DPA prevails. If the Standard Contractual Clauses apply and conflict with this DPA, the Standard Contractual Clauses prevail.
Annex A: Technical and organizational measures
- Encryption in transit: HTTPS for all traffic between browsers, Workers and the Service.
- Encryption at rest of stored secrets, such as cloud credentials, using AES-256-GCM.
- Password hashing with Argon2id, with bcrypt as fallback.
- Two-factor authentication with TOTP, enforceable per organization.
- Organization controls: roles, per-member permissions, allowed IP ranges and session timeout.
- CSRF protection on every form.
- Audit log of administrative and security events, with CSV export.
- Outbound-only Worker connections. The Service does not connect into Customer networks.
- Signed software updates for Workers.
- Data minimization: datasets and large outputs stay on Customer Workers.
- Access to production systems limited to authorized personnel. [Describe access control, logging and review.]
- Backups and recovery. [Describe frequency, encryption and testing.]
- Vulnerability reporting at security@esacode.com. [Describe patching and incident response process.]
Contact
Data protection questions: privacy@esacode.com. Security incidents: security@esacode.com.