WORM storage

WORM means write once, read many. Lexkeep uses WORM storage to help preserve important files in their uploaded form and reduce the risk of silent overwriting or impermissible replacement.

WORM storage supports stronger recordkeeping for files that may later be needed in an audit, investigation, dispute, regulatory review, or other high-trust workflow.

How WORM storage works

When a file is uploaded to Lexkeep, its stored record is preserved as a distinct file version.

If the document needs to be updated, do not overwrite the original file. Instead, create a [new file version]. The earlier version remains in the file’s version history, together with the later version and its amendment note.

This provides a clearer record of:

• The original uploaded file
• Later versions of that file
• The order in which versions were created
• The reason for an update, where an amendment note is added
• The integrity status of each version, where applicable

Why WORM storage matters

Conventional file storage can make it difficult to determine whether a document was replaced, changed, or overwritten without a reliable record.

WORM storage helps support:

• Preservation — Important files are retained as distinct records.
• Version traceability — Updates are added as new versions rather than silently replacing earlier files.
• Record integrity — Preserved files can be checked against their integrity reference.
• Defensible workflows — Teams can better explain how a record was created, updated, and maintained.

Use WORM storage with other Lexkeep controls

WORM storage is most effective when used with Lexkeep’s other recordkeeping features:

• Create file versions for revised or corrected documents.
• Use Amendment Notes to explain why a new version was added.
• Enable Anchor on Blockchain for files that require independently verifiable proof of integrity and timing.
• Review file activity and anchoring status from the relevant file card.
• Organize related records within a cohort.

Important

WORM storage preserves the history of uploaded records. It does not prevent you from creating a newer version when a document changes.

For lifecycle, retention, legal-hold, or withdrawal decisions, follow your organization’s records-management policies and applicable legal obligations.