Vidimus
Explainer videos NL Start free

VIDIMUS/SECURITY

Security and trust.

What is in place today, without claims that are not there. Every line below is live and verifiable. What is not here, we do not have.

Only a mathematical anchor is public, which shows whether your logbook was rewritten afterwards. Who you are, what you record and with whom stays within your organisation and with the people you give a link to yourself.

Keys stay with you.

01
  • Signing happens on the device. Every team member and every counterparty signs with an Ed25519 key that is created on their own phone and does not leave the device. We cannot sign with a team member's key: it does not leave their device. A new key in their name would be visible in the bundle as a different key.
  • We store system keys. If your TMS, ERP or sensor sends records itself, a system key stored by Vidimus signs, with the name of that system in the certificate. Even then, nobody can give a record an earlier anchoring time, not even us, and a change afterwards stands out: the time comes from an external timestamping service and the evidence bundle is with you.
  • Biometrics are optional, never required. Anyone who turns on Face ID or Touch ID links a passkey to the key. Without biometrics, the device simply works with its key; iOS then asks for the passcode.
  • Revoking takes one click. Lost phone or someone leaves: the dashboard revokes the key. What was signed earlier remains anchored and recomputable.

What we anchor, and how.

02
  • Fingerprint per record: SHA-256 over the canonical content and the hash of every attachment. One character different gives a different fingerprint. How an expert recomputes this without Vidimus: verification guide.
  • Anchor every five minutes: all new fingerprints in one Merkle root, signed by Vidimus and externally timestamped. If records of customer organisations are included, the new roots together receive a qualified timestamp (eIDAS) from GLOBALTRUST, a qualified trust service provider on the EU trusted list, usually within six hours; each record is connected to it through its Merkle path. So the clock is not ours.
  • Public anchor in Bitcoin: every root is also submitted to OpenTimestamps and included in a Bitcoin block within a few hours. Changing or erasing stands out there for anyone who checks, even if we were to try; the proof (.ots) is in every bundle and can be recomputed with ots (opentimestamps-client) and a public block explorer.
  • Ledger, append-only: every entry refers to the previous one; an insertion or a change afterwards visibly breaks the chain.
  • Everything verifiable yourself: the evidence bundle (zip) contains content, signatures, Merkle path and timestamp file. With openssl and a SHA-256 tool, you check it without Vidimus. How it works →

Where your data is.

03
  • Hosting: Hetzner Online GmbH, Nuremberg data centre, Germany (EU). Content stays in the EU; only fingerprints go to the timestamping services and OpenTimestamps.
  • The vault: originals and photos are stored encrypted (AES-256-GCM) with a separate key per document, wrapped under your organisation's key; those keys are themselves stored encrypted in a separate key vault, and every decryption by our server appears in the access log (Inzagen in the app), which you can see yourself. If you want us to be technically unable to read the content as well, choose a confidential logbook: then only you have the key. With a confidential logbook, it works like this: every device encrypts with your company key, and only your browser with the private key can read it. That key is created on your side and never reaches us; you keep a recovery file with a passphrase yourself. Vidimus then sees the fingerprint and a short envelope (type, reference, source and time), not the content.
  • Object Lock: every encrypted photo and record is also stored in Hetzner Object Storage (Nuremberg) with Object Lock in compliance mode: until the logbook's retention period expires, the storage does not allow erasing or overwriting, not even at our own request to the hosting provider. Erasing after the period is done by destroying the key; the file remains noise.
  • Backups and recovery: every night an encrypted copy of the database, the ledger and the keys goes to Hetzner Object Storage with Object Lock, kept for thirty days, at the same EU location; the recovery procedure is written down, and every quarter we automatically restore the latest backup into an isolated temporary folder and check that the database, ledger and documents can be fully recovered. The last test succeeded on 8 October 2026.
  • Retention period: by default ten years per logbook, adjustable per organisation. Closing a logbook produces a final root; after that nothing more is added, and what it contains can still be consulted and recomputed.

Access and connection.

04
  • Encrypted transport with TLS, HSTS enabled; headers against clickjacking and content sniffing; camera and location only for the app itself.
  • Sessions of twelve hours, signed cookies, two-step verification available under Account.
  • API keys per organisation, revocable; systems sign with their own system key and measurement sources with their own key, never with a personal one.
  • No trackers. No advertising networks, no analytics services. Fonts are loaded from Google Fonts; that is the only external request from your browser.

Report a vulnerability.

05
  • Email security@vo-initiatives.com. You get a reply within two working days from the people who wrote the code, not from a helpdesk.
  • We publish security.txt (RFC 9116) and do not hold anything against researchers who report in good faith.
  • In an incident that affects your data, we notify you without undue delay and at the latest within 48 hours of becoming aware of it, with what happened and what we did.

What we do not have, and when we will.

06
  • No ISO 27001 certificate. We are working towards the Belgian CyberFundamentals framework (CCB, the Centre for Cybersecurity Belgium); the self-assessment follows in 2026. We plan ISO 27001 as soon as a customer asks for it in a contract.
  • No qualified signature per record within the meaning of eIDAS. Each record is signed with the device key or with the organisation's system key. Groups with records of customer organisations usually receive, within six hours, a qualified timestamp from GLOBALTRUST, a qualified trust service provider on the EU trusted list, as long as our annual package with that service has capacity; each record is connected to it through its Merkle path. Demo and test organisations do not receive one. Only the director's mandate is signed with their Belgian eID (electronic identity card); whether that signature is qualified is shown by a validation of the certificate, not by Vidimus.
  • No crypto network of our own. The ledger is a hash chain on our infrastructure, signed and timestamped. Since 7 September 2026, every Merkle root also goes to Bitcoin via OpenTimestamps: a public second witness outside Vidimus, recomputable against Bitcoin itself.