Delete the data.
Keep the proof.

Cryptographic compliance infrastructure for SRA-regulated firms. Every audit event is sealed, chained, and independently verifiable. On erasure, the key is destroyed — data becomes unrecoverable while the audit chain still verifies.

scroll
The contradiction

The SRA requires tamper-evident records.
UK GDPR requires permanent erasure on request.

SRA Accounts Rules · 7-year retention
Every record immutable. Every hash verifies.
vs
UK GDPR Article 17 · erasure on request
The middle record must vanish. Cannot be recovered.

Every SRA-regulated firm lives with this structural conflict. Accounts Rules mandate audit trails that can withstand seven years of scrutiny. Article 17 of UK GDPR mandates erasure on client request. Under conventional architecture, you can satisfy one or the other. Not both.

The approach

Encrypt. Chain. Erase.

01 · Encrypt

Every compliance event is sealed in place with a unique AES-256-GCM key, wrapped under a master key your firm controls.

02 · Chain

Every record links to the previous via SHA-256. Tampering with any record — even years later — breaks every downstream hash and is instantly detectable.

03 · Erase

On an Article 17 request, the wrapped key is zero-filled. The payload becomes mathematically unrecoverable. The audit chain still verifies end-to-end.

See the full sequence →
Integrations

Works with the tools your firm already uses.

C
Clio
live
L
LEAP
soon
O
Osprey
soon

Audit immutability. GDPR erasure.
At the same time.

Currently onboarding design partners from SRA-regulated firms.