# Data Processing Agreement

Version 2026-11-21

> **Draft for counsel review. Not yet in force.**

This is a working draft. It sets out the processor commitments that the Esign Comply product specification states, with the specification reference beside each one. Licensed counsel has not yet written or reviewed it, and it is not yet an agreement that meets Article 28 of the GDPR. The specification requires a data-processing agreement to be in place before live keys are issued (PRV-2, EU-16).

## 1. Roles

The customer is the controller. Esign Comply is the processor for the signer evidence it is instructed to record, seal, store, and return (PRV-1).

The customer is also the controller of customer-supplied material: supplements and the notes it sends with a session. Esign Comply processes that material only to store, seal, return, and delete it (PRV-11).

## 2. Subject matter and data subjects

- **Processing.** Recording ceremony events sent from the signer's browser, sealing and timestamping the record, storing it, delivering signer receipts where configured, and returning records, reports, and evidence packages to the customer.
- **Data subjects.** The people who sign or accept documents in the customer's flows.
- **Duration.** The subscription term and the retention period in section 7.

## 3. Categories of data

The categories in section 10.2 of the specification, summarised in the [Privacy Notice](/legal/privacy):

- Signer identity asserted by the customer: external ID, name, email, phone, class, country.
- Verification data: verified email or phone, method, time, attempts; passkey credential ID and assertion.
- Intent data: control states, label and button text, typed name or drawn strokes.
- Time, network, and device data: server and client times, IP address, coarse geolocation, user agent, accept-language, TLS version, origin, page URL.
- Delivery data: receipt email time, message ID, delivery status.
- Later facts: withdrawal, dispute, supersession, legal hold, erasure action.
- Customer-supplied material, listed as a data category of unknown content (PRV-11).

The customer agrees not to send special-category data, payment card numbers, government identity numbers, or passwords (PRV-11, CS-11). Biometric identification is disabled unless separately approved (PRV-3).

## 4. Processor commitments

The specification (PRV-2) requires this agreement to cover:

- Processing on the controller's instructions, and notice where an instruction appears unlawful.
- Confidentiality.
- Security. Transport uses TLS 1.2 or later. All stores are encrypted at rest, with application-layer encryption for personal evidence fields (SEC-1, SEC-2). Staff access to customer evidence requires a ticket, is time-boxed and logged, and is visible to the customer in the audit log (SEC-7).
- Assistance to the controller, with deadlines. Esign Comply forwards signer requests it receives to the controller within two business days (PRV-9).
- Notice of a personal-data breach without undue delay after becoming aware of it, and assistance with the response (SEC-9).
- Audits.

## 5. Subprocessors

The controller's prior authorization, a process for objecting to a new subprocessor, and flow-down of these terms are required (PRV-2). The current vendors, their purposes, and their regions are in the [Subprocessor list](/legal/subprocessors).

## 6. Regions and transfers

A subscription's data region, US or EU, is chosen at domain registration. An EU region does not mean all processing stays in the EU. Transfer terms apply where needed, with United Kingdom mechanisms applied separately (PRV-2, PRV-8).

## 7. Retention, return, and deletion

- Ten years is the standard maximum capacity, not an EU default or a legal term. EU customers select a documented schedule by data class (RT-1).
- On termination the controller elects return or deletion (PRV-2, RT-3). A read-only EU archive of up to 12 months is available where requested and justified. For U.S. flows the 12-month export window applies (RT-3).
- Where a statutory floor recorded on a record has not expired, or a scoped legal hold applies, the affected content moves to archive at no charge until the floor expires or the hold is released, and then follows the controller's election (RT-10). Each hold records its basis, scope, necessity, and review date (RT-6).
- At expiry or instructed deletion, content and related data are purged, subject to the previous point (RT-4).

## 8. Erasure

Erasure deletes content, salts, indexes, queued copies, and linkable metadata (PRV-5). Copies in write-once storage are stored encrypted and erased by destroying their keys. Esign Comply treats data as erased only after confirming that all keys and recovery copies are unavailable (PRV-6). Restored backups are quarantined until past erasures have been replayed (PRV-7). Supplements tied to a signer are encrypted under that signer's key and are erased with the signer's data (CS-12).

The controller starts an erasure or restriction workflow through the API. Hashing alone does not make personal data anonymous.

## To be completed by counsel

The specification does not state the following, and this draft does not contain them:

- The parties' legal names, signature blocks, and the order of precedence with the Terms of Service.
- The annexes: processing details, technical and organisational measures, and the subprocessor list as a contractual annex.
- The transfer mechanism for each destination, including the standard contractual clauses module, the United Kingdom addendum, and Swiss terms.
- The notice period for new subprocessors and the consequences of an objection.
- Deadlines for assistance, and the audit procedure and its costs.
- Liability, governing law, and venue.
- Any joint-controller terms that the role assessment in PRV-1 requires.
