What the platform holds
- The ledger: the escrow contracts and their transactions. They are shared with every party to an escrow and are the legal record. Each party keeps its own copy on its own infrastructure.
- Working data off the ledger: drafts before they are agreed, private annotations, compliance screenings and decisions, custody operations, settings and a searchable index of the ledger.
- Identity: who an institution’s or customer’s people are, their sign-in link and their wallet links.
- Documents: evidence files in encrypted object storage. The ledger holds only their hash and location.
- Logs: the operational audit record, which names people only by pseudonymous reference (see Records & non-repudiation).
Whose data is personal
- Institutions are not people. An institution and the users and parties it operates are named in the clear.
- An institution running its own node is its own operator. Its node, ledger and logs are its own; the platform holds only what it needs to serve it.
- A customer’s people on the shared platform are identified by their institution or customer group. Their personal data (name, email, sign-in) lives only in the identity service. Logs and the ledger carry pseudonymous references and party ids.
- A person’s erasure. On request, the identity service erases the person: the link from their references is deleted and their identity record is reduced to an anonymous placeholder. Their past activity stays in the record but no longer leads back to them. Live.
Legal holds
A hold placed for litigation or a regulator’s request, on a person or on a whole customer, stops erasure and deletion until it is released. Export still runs under a hold. Placing and releasing a hold is restricted to the platform’s auditors and recorded. Live. Holds on a single escrow, and freezes that stop the funds, are covered in Legal orders.
When a customer’s contract ends
Under EU data protection law a processor returns or deletes the customer’s data when the service ends. The platform runs this as a recorded case, from the customer’s written notice to the last deletion.
- Inventory. Every store’s rows for the customer are counted. A store the platform adds is not released until it is accounted for here.
- Export. Everything held for the customer is exported as a bundle. A manifest lists each file’s hash and row count, and the platform’s termination key signs it. The bundle is encrypted to the customer’s own public key, so only they can open it. They can check the signature and hashes with standard tools.
- Receipt. The customer confirms receipt, and the confirmation is recorded. Nothing is deleted before it.
- Deletion. The customer’s own data is deleted.
- Shared records stay. An escrow’s contract, its documents and drafts that name a counterparty belong to the counterparty as much as to the customer.
- Records the law requires are kept. AML screenings and decisions, custody records and the audit trail are kept for the period their regulation sets, then deleted.
- Holds. Deletion refuses while a hold stands, and refuses if the data changed after the export.
- Certificate. A signed deletion certificate lists, for each store, what was exported, deleted and kept, and until when. It names the customer, not its people.
- Retention end. A scheduled job deletes each kept record when its period ends and adds a signed addendum to the certificate. A hold defers it. After the last period ends, the platform keeps no identifiers for the customer.
Status: Rolling out. The case, export, deletion, certificate and retention end are built for the escrow service’s records, the customer’s people are erased from the identity service with a signed record, and the billing account is cancelled. Agreement authoring and document stores follow, service by service. Until each is built, the operator completes its part by hand under the same case.
What stays
- The ledger is not rewritten. Its contracts are shared with the counterparties and are the legal record. The customer’s people are erased from the identity service instead, so the ledger keeps only pseudonymous party ids.
- The write-once ledger trail is locked for its retention period and can’t be deleted before then.
- Billing records are kept. The customer’s billing account is marked cancelled, not erased. Its billing contacts, addresses, accounts, invoices and usage are kept for the accounting and tax periods. Anything still owed is billed in a final invoice and kept as a receivable until it is paid.
- The case and its certificate are kept as proof of what was done. They name the customer and the operator, never the customer’s people.