Delete the data.
Keep the proof.
Nexum keeps a one-way fingerprint of each record, never the record itself, and a verifiable log of every retention decision. When retention ends, the data goes. The proof that you handled it lawfully stays.
The SRA requires records that cannot be altered.
UK GDPR requires permanent erasure on request.
Every 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. Nexum addresses this by leaving the mandatory record untouched in your practice management system, while providing the cryptographic verification, decision-audit, and compliant lifecycle layers around it.
Seal. Audit. Comply.
Every document and compliance event is hash-sealed into an append-only Merkle chain. Each record gets a unique cryptographic fingerprint that proves it existed in exactly this form at exactly this time.
Every retention decision, access event, and lifecycle action is recorded with full actor context: who did it, when, and why. Tampering with any record breaks every downstream hash and is instantly detectable.
When a record's retention period expires and the firm's COLP authorises destruction, Nexum destroys only its own encrypted metadata, such as the file name, and issues a key-destruction certificate. The document itself never came to Nexum and stays in your PMS throughout.
When AI touches a matter,
prove it.
Solicitors remain fully accountable for AI-assisted work. Nexum seals each AI interaction at the moment it is used on a matter: which model ran, for what purpose, over which sealed documents, and which named person reviewed the output. The prompt and the output are hashed in your browser and discarded; the text never reaches Nexum in any form.
When a client exercises their right to erasure, Nexum destroys the interaction's encryption key and issues a destruction certificate. What remains is exactly what an inspection needs: proof that the interaction existed, was reviewed, and was erased, with none of the personal data that proof used to require.
Production, August 2026. The two erased interactions keep their hash and their place in the chain. The envelope behind them is gone for good.
Your case management system stays where it is.
Nexum never takes custody of the file. It seals a fingerprint of what your system already holds, so nothing is migrated and no workflow changes.
Sealing works today with or without any of these. An integration removes a copy-and-paste step. It is not what makes the proof valid. Our Clio connection is live and can be checked at /api/integrations/clio/status, which answers with whether this deployment can reach Clio and nothing about what is on the other side.
The record they can't dispute.
Built for regulated UK law firms.
Currently onboarding design partners from regulated law firms.