Draft for counsel review. Not yet in force.
This is a working draft. It describes how the Esign Comply product specification says personal data is handled, with the specification reference beside each point. Licensed counsel has not yet written or reviewed it. It is not the notice required by data-protection law until a reviewed version is published on this page with the status "published".
1. Roles
- Signer evidence. When a company (the customer) uses Esign Comply to record a signing or acceptance ceremony, the customer is the controller and Esign Comply is the processor for the evidence it is instructed to record (PRV-1). The customer's own privacy notice governs that processing.
- Customer-supplied material. The customer is the controller of everything it sends as a supplement or as notes with a session. Esign Comply processes it only to store, seal, return, and delete it (PRV-11).
- Esign Comply's own purposes. Esign Comply acts on its own account for some purposes, for example keeping the delivery and acknowledgment log for guidance notices, which holds team members' email addresses (PRV-12). The assessment of its other own purposes is listed for counsel below.
2. What a record contains
The specification (section 10.2) lists the evidence captured for each record. Fields are tagged observed, meaning seen or generated by Esign Comply, or asserted, meaning supplied by the customer.
| Category | Fields | Tag |
|---|---|---|
| Signer identity | External ID, name, email, phone, class, country | Asserted |
| Signer verification | Verified email or phone, method, time, attempts; passkey credential ID and assertion | Observed |
| Intent | Control type, label and button text, typed name or drawn strokes, trusted-event flag, initial control state | Observed |
| Presentation and consent | Presentation mode, visibility and link measurements, scroll completion, viewport, notice snapshot, disclosure version, consent act | Observed |
| Time | Esign Comply server time for every event; client clock and time zone; external timestamp | Observed |
| Network and device | IP address, coarse geolocation, user agent, accept-language, TLS version, origin, page URL | Observed |
| Delivery | Receipt email time, message ID, delivery status | Observed |
| Later facts | Withdrawal, dispute, supersession, legal hold, erasure action | Mixed |
A record also holds the document version and its hashes, conformance results, and integrity data such as the record hash, seal, and timestamp token.
3. What is not collected
Esign Comply captures what shows the act and no more: no session replay, no cross-site identifiers, and no fingerprinting beyond request metadata (PP-7). Live EU ceremonies use minimal capture by default, with drawn signatures, fingerprinting, and optional device data switched off (EU-14). Biometric identification is disabled unless separately approved (PRV-3). Free text a customer sends is never used to train or prompt a language model (PRV-11).
4. Retention
- Ten years from signing is the standard maximum capacity on Starter and Unlimited while subscribed. It is not an EU default, a legal requirement, or a guaranteed term (RT-1).
- EU customers select a documented retention schedule by data class. On termination the EU controller elects return or deletion (RT-1, RT-3).
- For U.S. flows, records remain exportable for 12 months after cancellation (RT-3, US-31).
- A statutory floor recorded on a record, or a scoped legal hold, can extend retention for the affected records only (RT-10).
- Signers keep access to their own executed copies through the receipt link for the retention period, and receive 60 days' notice and a download link before a copy is removed (RT-9, RT-10).
- Test-mode evidence is kept for 30 days.
5. Erasure
Personal evidence fields are encrypted at the application layer (SEC-2). Erasure deletes the content, salts, indexes, queued copies, and linkable metadata (PRV-5). Copies held in write-once storage cannot be rewritten, so they 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).
A hash can remain in the ledger after erasure. Hashing alone does not make personal data anonymous.
6. Signer requests
If you signed or accepted a document through a company that uses Esign Comply, that company is the controller. Send your request to it. Where a signer writes to Esign Comply instead, Esign Comply forwards the request to the customer within two business days and assists the customer (PRV-9). The receipt email also carries a "This was not me" link, which records a dispute on the record (SR-3).
7. 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. Vendors that process data for Esign Comply are named in the Subprocessor list. Timestamp authorities and public anchoring services receive hashes only.
8. Security incidents
As processor, Esign Comply notifies the controller without undue delay after becoming aware of a personal-data breach and assists its response (SEC-9).
To be completed by counsel
The specification does not state the following, and this draft does not contain them:
- The identity and contact details of the controller, and any representative or data protection officer.
- The lawful basis and purpose for each field and each of Esign Comply's own purposes (PRV-1, PRV-3).
- Transfer mechanisms and the transfer map (PRV-8).
- The inventory of cookies and device access on Esign Comply's own sites (PRV-4).
- Retention periods for account, billing, and website data.
- The rights of data subjects, how to exercise them, and how to complain to a supervisory authority.
- Disclosures required by U.S. state privacy laws.