VIDIMUS/LEGAL & AUDIT/THE SIXTEEN QUESTIONS
The sixteen hardest questions. Answered honestly.
These are the questions a customer, a partner, an IT person or a lawyer asks before signing. Each answer describes what runs today — not what we plan to do. Where something has a limit, the limit is stated. Partners may copy these answers word for word.
01Is this evidence in court?
Vidimus supplies evidence, not a verdict. Between businesses in Belgium, evidence is free (Book 8 of the Belgian Civil Code, Art. 8.11): all means of evidence are admissible and the court weighs them. An electronic signature, an electronic timestamp and an electronic document may not be refused solely because they are electronic (eIDAS Arts. 25, 41 and 46). What Vidimus adds on top: every link can be recomputed without Vidimus — the counterparty, its expert or the court does not have to take our word for it. For customer organisations there is a qualified timestamp per group: it gives the legal presumption of the accuracy of the date and time and of the integrity of the data to which it is bound (eIDAS Art. 41(2), see 2). The record is linked to it through hash calculations you can recompute yourself (Merkle path, Evidence Record). Whether the presumption also applies to the record itself is for the court to assess. More under legal & audit.
02Is the signature qualified? And the timestamp?
The GLOBALTRUST timestamp is, for groups with customer records. The device signature is not. The key is created on the device and does not leave it, and any later change is visible. Whether that is an advanced electronic signature (eIDAS Art. 26) is for the court to assess. The director signs the mandate that identifies their organisation, using their Belgian eID. Whether that signature is qualified is shown by a check of the certificate (for example with the European Commission's DSS), not by Vidimus. The timestamp is a qualified electronic timestamp (eIDAS Art. 42) from GLOBALTRUST, a qualified trust service provider on the EU trusted list, included in the price. Groups with records from customer organisations usually receive it within six hours, and each record is linked to it through its Merkle path, as long as our annual package with that provider has room; demo and test organisations do not receive it. Vidimus itself is not a qualified trust service provider and not a notary.
03Can Vidimus itself forge, backdate or delete a record?
Not without it being noticed. When a person signs, the signature comes from a key that does not leave their device; we do not have it. If your system (TMS, ERP, sensor) sends records itself, it holds its own key, or we keep it if you choose; in that case, this is stated in every bundle. Nobody can give a record an earlier anchoring time, not even us, and a later change stands out: that time comes from external timestamps and from a Bitcoin block, not from our clock. The ledger is a hash chain: changing one entry breaks everything after it. And the evidence bundle is with the customer, with script and guide. What we could do with a stored system key: create a new record in that system's name, with the anchoring time of now. If you want to rule that out, let your system hold the key itself. Nor can we delete: originals are written once and go to storage with Object Lock.
04What about personal data (GDPR)?
For the content of the records, the customer is the controller and Vidimus the processor; for the mandate, the agreements and the accounts, Vidimus is itself the controller. The data processing agreement is in the terms. Only a mathematical anchor is public, with which you can check whether your logbook was rewritten afterwards. Who you are, what you record and with whom stays within your organisation and with whoever you give a link to yourself. In logbooks with personal data, a secret salt per record is part of the fingerprint, so nobody can guess names or numbers; the salt is only in the bundle of that one record. Content and attachments are stored encrypted in the vault (AES-256-GCM, a separate key per document, a key per organisation); every decryption by our server appears in the access log, which the customer sees. Access to systems is limited to the managing director and logged.
05Locked storage and the right to erasure — how do they go together?
By deleting the key, not the file. The encrypted original stays (Object Lock does not allow anyone to overwrite it), but without its document key it is noise for good — for us too. This is called crypto-shredding. In our encrypted backups, that key remains for at most thirty days; after that, it is gone everywhere. The fingerprint, the timestamp and the ledger entry are pseudonymised and continue to prove that something existed, when and by whom. After the logbook's retention period, the key is deleted in the same way: today this happens on request; automatic deletion after the retention period does not exist yet.
06What if Vidimus stops?
Your bundles remain verifiable, even without Vidimus. The bundle belongs to the customer: open formats, standard cryptography, the reference script and the guide are inside. The timestamp file (.tsr) can be checked back to a root certificate that is already on every computer; the Bitcoin proof against Bitcoin itself. If Vidimus stops voluntarily, we announce it at least ninety days in advance, exporting remains possible for that whole period and the public keys to check bundles stay published; in a bankruptcy, the bankruptcy trustee decides. Every night, an encrypted copy of the database, ledger and keys goes to storage with Object Lock; the recovery procedure is documented.
07What exactly does Vidimus store?
Always: the fingerprint, the signature, the time, the Merkle path, the ledger entry and the "envelope" (type, reference, source and time; also the logbook) needed for the invoice and to find things again. Only if the customer sends it along: the content and the attachments themselves — photos, PDFs, CMRs — encrypted per document in the vault. If you only send the hash (for example a whole folder via the manifest), you keep the originals yourself. What we never have: the private key of a device, and biometric data. The secret salt of a record with personal data never appears on a public page; it is only in the bundle of that one record.
08Where is the data, and who are the sub-processors?
Server and Object Storage at Hetzner Online GmbH in Nuremberg, Germany (EU). Storage in the EU only. Sub-processors: Hetzner (hosting, storage), the qualified timestamping service and Sectigo (timestamps; receive only hashes), the public OpenTimestamps calendars (only hashes), Stripe (payments; company and contact details, never record content), Recommand (Peppol e-invoices; invoice data), Google (sending emails; name and address of the recipient), Anthropic (the assistant in the app, United States: only when you ask the assistant a question does Anthropic receive that question and the data the assistant looks up for it). An AI service you connect yourself via MCP or the API works on your instructions and is not a sub-processor of Vidimus. Changes are announced thirty days in advance. Suppliers that do not process record content (our mailbox, the website, push notifications, booking an appointment) are listed in the privacy notice.
09Sandbox, limits, idempotency — how do I test and connect safely?
Every partner immediately gets a sandbox end customer with its own key and test logbook. A real end customer only gets a logbook after its own director has signed the mandate with the eID; you request a signing link for this via the partner API. Every organisation can test up to 100 records a month for free, without payment details. A new organisation starts with the mandate of an officer listed in the Belgian company register (KBO; see question 16). Records accept an idempotency_key: sending the same key twice returns the same record, not a duplicate. Creating end customers via the partner API is idempotent on your customer number. Measurements only come from a measurement source you create with a unit and a range: at most one every ten seconds per source, in ascending time and no older than 24 hours. Sending too fast gets a clean 429, not a silent loss; a value outside the unit or range is refused. Recording stops when an account is suspended; reading and verifying always keep working.
10Key management, pentest, ISO — how secure is it really?
Device keys are created on the phone and never leave it; we receive the public half. System keys of organisations and the vault keys (per document, per organisation, master key) are on the server with restricted permissions, and every decryption is logged. What is and is not in place is stated without embellishment on the security page: no ISO 27001 certificate (we are working towards the CyberFundamentals framework of the Centre for Cybersecurity Belgium, CCB), responsible disclosure is open, access is restricted and logged, TLS with HSTS. If you need a certificate or an independent test under contract, say so at the start; then we plan it.
11Who invoices and who provides support if I work through a partner?
Reseller and integrator: the partner invoices its customer under its own name and provides first-line support; Vidimus invoices the partner and provides second-line support. Referral: Vidimus invoices the customer directly and provides the support; the partner receives its share. In all cases: the end customer owns its records, can export everything, and its content is encrypted with a key the partner does not have. See partners.
12What if the customer wants to leave its partner — or the partner stops?
Then the customer continues directly with Vidimus, or with another partner, keeping its records, keys and verification links. Vidimus and the partner cooperate in the transfer; this is set out in the terms (chapter 5) and in the partner agreement (Art. 7). Nothing of the proof is tied to the partner.
13What SLA do I get?
Without a separate agreement: we aim for 99.5% availability per month, a reply within one working day from the person who built it, a fault that blocks anchoring picked up within four working hours, a nightly backup and a tested recovery plan. The app works without a connection and sends later; the time of signing on the device is recorded as well, so an interruption does not lose any proof. Firmer commitments, a credit scheme and a fixed contact person: through an SLA with an annual contract.
14What is Vidimus liable for?
For the anchoring working as described in the terms: fingerprint, signature, timestamp, ledger, verification. Not for the content of records, not for decisions someone bases on them, not for indirect damage. Total liability is limited to the fees of the past twelve months. For partners, the same limit applies in the partner agreement (Art. 8).
15Can a bundle still be checked in ten years' time?
The fingerprint (SHA-256), the Merkle path, the Ed25519 signatures and the ledger entry remain recomputable as long as those standards exist — and they are in the bundle with script and guide. The Bitcoin proof remains recomputable as long as Bitcoin exists. One honest limit: the certificate of the timestamping authority has a term; after it expires, the timestamp file still shows the root and the time, but the signature of the timestamping service can then no longer be used in the strict sense of the certificate check. That is why, for matters that run for a long time, we recommend re-anchoring the bundles periodically (a whole folder in one record): each new anchor proves that the old bundle, including the old timestamp file, existed unchanged at that moment.
16Who signs the mandate, and when?
Before your first logbook, an officer of your company (for example a director or managing director), as listed in the KBO, signs the mandate once with the eID. This also applies to a chain partner who co-signs in your logbook, and to an end customer of a software partner: each company signs for itself. Colleagues and team members of an identified company do not need their own eID step. Why? So that every record shows which company recorded it and who represented that company. What a record is worth as evidence is always for the court to assess.
A summary, not legal advice. Is your question not listed? oskar@vo-initiatives.com — reply within one working day, from the person who built it.
Questions and answers.
One more question? Ask the bundle itself.
Download the sample bundle and run the script. Everything stated above can be recomputed there.