Zero retention for documents: store less, account more clearly

Solicitor documents belong in the firm’s matter file - not permanently in every tool that briefly touches them. Zero retention means the service processes content and does not keep it longer than needed for the technical job. For GDPR and professional secrecy that is a structural advantage, not a slogan.

Processing is not archiving

Friction often starts when teams treat cloud tools as a second DMS. Folders “just in case” in the tool, old versions, share links without end. Zero retention reverses the logic: the tool is a station; the matter file is the destination. Export into practice software or the approved drive is mandatory, not optional.

That eases processor agreements and deletion concepts - it does not replace them. You still need clarity on controller role, sub-processors, logs and how long temporary caches live.

Checklist for selection and use

• Describe purpose narrowly (OCR, compression, merge).
• Check retention and deletion logic in the DPA / documentation.
• Do not build permanent matter storage inside the tool.
• Fix and train the export path into the firm file.
• Named access, no shared catch-all passwords.
• Where useful: local copy of the filing version with hash/date.

What teams must still keep

Zero retention does not excuse professional record-keeping. The filed version, proof of sending, internal approvals belong in the matter file. Relying only on the processing path loses evidence once the job ends - that is intentional and must be caught organisationally.

LexLogik is designed as a processing tool with short retention and hosting in Germany. The firm remains master of the file.

Client communication about storage

Some clients ask whether papers “sit in the cloud”. Short honest answer: processing tool with short retention, matter file in firm infrastructure, DPA in place. Over-claiming creates unmet expectations.

Internally, leavers should lose processing-tool access too. Zero retention helps only when export routines stick.

Think erasure separately

Tool and file need separate erasure descriptions. Local downloads and email forwards remain common gaps in access requests.

Everyday culture

Partners should say plainly: “Done means in the file, not in the tool.” Assistants need simple save targets (watch folder, matter folder). Data minimisation then becomes practical rather than abstract.

Export as a mandatory matter step

Fix in the internal flow: after processing in the tool, export immediately into the matter file, then leave no working copies in the service. Zero retention then becomes lived practice, not only contract wording.

Support access and approval log

Require that support may touch clear text only with documented approval - and that approval ends after the incident. Store ticket number and time window on the matter. Zero retention alone does not block a support view; organisation and tech must work together. Client questions about “who could see this?” then get facts, not guesses.

Zero retention helps only if the tool stays a station and the matter file is the destination. Narrow purpose, short caches and consistent export cut liability and deletion questions. Keeping “just in case” folders in the cloud turns zero retention back into a second archive.