VIDIMUS/QUESTIONS/WORM AND OBJECT LOCK
Does WORM storage prove that your data was not changed?
Short answerNot on its own. WORM storage (write once, read many, such as Object Lock in compliance mode) prevents a file from being overwritten or deleted during the retention period. That is a promise from the storage service, which a third party cannot recompute themselves. A fingerprint with an external timestamp adds to that: anyone can recompute it themselves.
Updated on 29 October 2026 · Oskar Verschoren, Vidimus (VO Initiatives BV, Antwerp)
Keeping and proving are two different things.
| question | WORM storage (Object Lock) | anchoring |
|---|---|---|
| What does it stop? | Overwriting and deletion at the storage service, until the retention period expires. | Nothing. It makes a change visible to whoever checks. |
| Who can recompute it? | Only someone with access to the storage settings; a third party has to trust the service. | Anyone with the file and the evidence bundle, even without Vidimus. |
| When did it exist? | A date in the storage service's own data. | A timestamp from an external service and a Bitcoin block. |
| What happened before it was written? | Outside its scope. | Outside its scope: both start at the moment of recording. |
| Can a deleted file come back? | Yes, it stays stored. | No, a fingerprint does not bring back a file. |
That is why Vidimus does both: anchoring, so that anyone can recompute, and storage with Object Lock, so that the original stays there.
How Vidimus does it.
Anchoringsha-256 · ed25519 · rfc 3161 · bitcoin
Each record gets a fingerprint and a signature, and within five minutes a timestamp from an external service on the group. The root goes into our ledger, where each entry hashes the previous one, and into Bitcoin via OpenTimestamps.
Encrypted storageaes-256-gcm
Originals and photos are stored encrypted with a separate key per document, wrapped under your organisation's key.
Object Lock in compliance modeHetzner Object Storage · Nuremberg
Each encrypted photo and record is also kept in storage with Object Lock in compliance mode: until the logbook's retention period expires, the storage allows no deletion or overwriting, not even at our request to the hosting provider.
Backupsevery night · thirty days
Every night, an encrypted copy of the database, ledger and keys goes to storage with Object Lock, kept for thirty days. Every quarter, we restore the latest backup into a shielded folder and check that everything can be recovered.
Deletion after the periodby destroying the key
Deletion works by destroying the document key: the encrypted file stays, but without the key it cannot be read, not even by us. Today this happens on request; automatic deletion after the retention period does not exist yet.
What it does not prove.
- WORM does not show when a file first existed. The storage date comes from the storage service itself.
- What happened before it was written. Both WORM and anchoring start at the moment of recording.
- That your own systems did not change. Vidimus's Object Lock protects the copies at Vidimus, not your database or the files on your side.
- That you meet a particular retention obligation. Which retention rules apply to you, and whether this storage is enough for them, is for your legal adviser or auditor to assess.
Specifications.
- object lock
- compliance mode · Hetzner Object Storage, Nuremberg (Germany)
- encryption
- AES-256-GCM · separate key per document · key per organisation
- retention period
- ten years per logbook by default, adjustable per organisation
- backups
- every night, encrypted, with Object Lock, thirty days · recovery tested every quarter
- anchoring
- SHA-256 · Ed25519 · RFC 3161 per five-minute group · ledger as a hash chain · OpenTimestamps → Bitcoin
- deletion
- by destroying the document key · on request · automatic after the period: not yet
- confidential logbook
- the phone encrypts before sending; only you have the key
Frequently asked questions.
What is the difference between governance mode and compliance mode?
In governance mode, an administrator with a special permission can lift or shorten the lock. In compliance mode, nobody can, not even the account administrator, until the retention period expires. Vidimus uses Object Lock in compliance mode.
How does WORM fit with the right to erasure (GDPR)?
By deleting the key, not the file. The encrypted original stays, but without its document key it cannot be read, not even by us. In the encrypted backups, that key remains for at most thirty days.
Do you still need WORM if everything is anchored?
Yes, if you want to keep the original. A fingerprint shows that something changed or disappeared, but it does not bring back a deleted file. Storage and anchoring complement each other.
Can Vidimus itself delete or change a record?
Not without it being noticed. A change afterwards breaks the fingerprint and the ledger, and the time comes from external timestamps and Bitcoin. Originals are written once and go to storage with Object Lock.
Further reading.
More questions and answers.
How we start: your first logbook today, the first 100 records free.
You create your account in two minutes. No payment details needed. A director identifies your company once with the Belgian eID; then you create your first logbook in a few minutes. Would you rather talk first? Book 15 minutes with the founder.