In force from 1 November 2026 (previous version 2026-10, in force from 28 September 2026). New organisations accept this version when they sign up; existing organisations are presented with it in the app. Each organisation accepts the version in force at that moment; that acceptance is itself anchored in the organisation's "agreements" logbook, with the date, the user and the version number.
Antwerp · KBO (Belgian company register) BE 0805.309.143 ("Vidimus", processor) and the organisation that creates an account ("the Customer", controller).
This text was drawn up by Vidimus and constitutes the agreement between the parties. Changes receive a new version number and are presented again for acceptance; each organisation can later check for itself which version it accepted.
What Vidimus does.
Vidimus is an electronic anchoring service. For every record that the Customer or its people make, Vidimus computes a cryptographic fingerprint (SHA-256), has it signed with the submitter's key, bundles it in a Merkle tree, has the root of that tree timestamped within five minutes by an independent timestamping service and, for records of customer organisations, usually within six hours with a qualified electronic timestamp from a qualified trust service provider on the EU trusted list (eIDAS), and writes it into a hash-chained ledger. When a person signs, their key exists only on their device. When a system of the Customer (for example a TMS, ERP or measuring device) sends records itself, that system keeps its own key, or Vidimus stores that key encrypted on its server if the Customer chooses this; even then, nobody can backdate a record or change it afterwards without the check showing it.
Vidimus thereby provides proof of integrity (the content has not changed since), time (the content existed before the qualified timestamp) and origin (signed with the device of a specific person at a specific organisation). Vidimus does not judge whether the content is accurate.
Vidimus is not a qualified trust service provider within the meaning of eIDAS and not a notary. Each record is signed with the key of the device of the person who signs, or with the organisation's system key. Records of customer organisations also receive a qualified electronic timestamp (Art. 42 eIDAS) from a qualified trust service provider on the EU trusted list, usually within six hours; this is included in the price. Vidimus buys these timestamps per year from the trust service provider. If that annual package is nearly used up, it can take up to twelve hours; if it is used up, the timestamp follows as soon as there is capacity again. Demo and test organisations, including the test customer of a software partner, do not receive a qualified timestamp.
Who owns what.
- The records belong to the Customer. Content, attachments, fingerprints and evidence bundles are the property of the Customer. Vidimus acquires no rights to them whatsoever, except the right to process them in order to provide the service.
- The Customer can always take everything with it. Every record can be exported as a self-contained evidence bundle with the content, the signatures, the Merkle path, the timestamp file and the ledger entry. That bundle can be checked with open standards, without Vidimus. Vidimus will never block that export, not even in a dispute about payment.
- Anchored proof is not changed or erased. Not by the Customer, not by Vidimus, not at the request of a third party. At the Customer's request, the content of a single record can be made unreadable by destroying its content key (GDPR, see 5); the fingerprint, the timestamp and the ledger entry remain and continue to prove that the content existed.
- Retention period. By default ten years per logbook, adjustable by the Customer. When it expires, Vidimus deletes the content; the fingerprints and anchors remain in the ledger. When the agreement ends, the Customer has ninety days to export everything.
People and devices.
- The Customer guarantees the identity of its people. Anyone the Customer invites via "Team members" (Medewerkers in the app) and links to a device signs on behalf of the Customer. That link is itself anchored. The Customer is responsible for the accuracy of name and position and revokes a device in case of loss or departure.
- People's keys stay on the device. Vidimus receives only the public half. A system through which the Customer sends records can keep its own key; Vidimus then receives only the public half. If the Customer chooses to have Vidimus store that key, it is stored encrypted on the server, with a master key outside the data folder and outside the backups. The Customer can revoke or replace any key at any time. Biometrics (Face ID, fingerprint) are processed exclusively by the device itself; Vidimus never receives or stores biometric data. Using them is the user's choice; the device key without biometrics always remains available.
- Location. When signing, the device requests its position and includes it in the record, only at that moment. Vidimus presents that position as "according to the device": it proves when and what was signed, not independently where the signatory was standing. The Customer informs its people about this.
- Partners and shared logbooks. If the Customer invites another organisation to a logbook, that organisation signs with its own devices and in its own name, after a director of that organisation has signed its own mandate with the Belgian eID (electronic identity card); the Customer's mandate does not apply to it. On such a shared logbook, all parties see each other's records: the facts, the times, the place of signing, the name and position of the signatory, and the photos of each stop. Not visible to partners: email addresses, phone numbers or other data of employees. Each party is the controller for its own people and informs them about this; acceptance of the invitation constitutes the mutual agreement on this data sharing and is anchored at both organisations. Legal basis: the performance of the transport or delivery contract and the legitimate interest in proof of handover, such as the driver's name on a consignment note.
Use, price, liability.
- Price. Free up to 100 records a month, with no end date and no payment details; anchored records and evidence bundles remain verifiable. After activation, the Customer pays per unit according to the pricing page at the time of use: per record (document, photo, signature, event) and per measurement source (sensor, logger or other device that sends measurements; unlimited measurements), per tier, with a monthly minimum and no cap (above one million records a month, an annual contract is offered on quote); prices excluding VAT, billed monthly in arrears, with no minimum term. A measurement is a value in the fixed measurement schema (source, time, number, unit) from a measurement source that the Customer created with a unit and a range, within that range, that arrives via the API's measurement endpoint; everything else counts as a record, including what arrives via the older general input endpoint. A measurement source counts in any month in which it sent at least one measurement. If the Customer uses the measurement endpoint to have events, documents or other records counted as measurements, Vidimus may, after notice, charge those measurements as records, from the start of that use. Charges are per record and per source; there are no other units. A chain partner co-signs free of charge, after identifying its organisation with its own eID mandate. If it wants its own logbooks, it pays for its own usage. Records of an invited organisation on a logbook of the Customer count as the Customer's usage.
- Payment. On the first of the month, Vidimus invoices what was used the month before, also as an electronic invoice via Peppol. With direct debit or card, the amount is collected automatically; with bank transfer, the invoice is payable within 14 days, or within 30 days for an annual contract. If a payment is not made, Vidimus notifies the Customer. Fourteen days later, new records fall back to the free limit (100 records a month and one measurement source) until the payment is settled; sixty days later, Vidimus may terminate the agreement. The account then remains as a free subscription and the outstanding invoice remains due. Proof is never collateral: anchored records remain verifiable, and verification, evidence bundles and export always keep working (see 2).
- Term and annual contract. A subscription runs from month to month, with no minimum term, and can be terminated at any time with effect from the end of the current month. Instead, the Customer can conclude an annual contract: twelve months, invoiced monthly, at a fixed monthly amount for an agreed volume, calculated as ten months of usage spread over twelve. Vidimus charges usage above the agreed volume per quarter according to the pricing page; lower usage gives no refund. If the Customer terminates an annual contract before the end, the monthly amounts for the current contract year remain due. After twelve months, the annual contract becomes an ordinary monthly subscription, unless the Customer chooses a new year; Vidimus notifies the Customer one month in advance. Here too, proof is never collateral (see 2).
- Availability. Vidimus aims for 99.5% availability per month, excluding announced maintenance, and does not guarantee it without a separate service agreement. The app works without a connection and sends later; the time of signing on the device is recorded as well, so an interruption costs no proof.
- Support. On working days, reports are answered within one working day by the people who built it; a fault that blocks anchoring is picked up within four working hours. Stronger guarantees, a credit arrangement and a fixed contact person are possible through a service level agreement (SLA) with an annual contract; see the pricing page.
- Continuity. Every night, an encrypted copy of the database, the ledger and the keys goes to storage with Object Lock (thirty days); the recovery procedure is documented and tested every quarter. The proof does not depend on Vidimus: the evidence bundle, the qualified timestamp and the Bitcoin proof can be checked without us. If Vidimus stops the service, it announces this at least ninety days in advance, exporting remains possible throughout that period and the public keys for checking bundles remain published.
- Liability. Vidimus is liable for the proper functioning of the anchoring as described in 1. Vidimus is not liable for the content of records, for decisions that the Customer or third parties base on them, or for indirect damage. Total liability is limited to the fees of the past twelve months.
- Prohibited use. No recording of content that is unlawful or to which the Customer has no right. Vidimus may suspend an account in case of abuse, while preserving the export right under 2.
- Governing law and disputes. Belgian law. The courts of Antwerp, Antwerp division, unless mandatory law provides otherwise.
Software partners.
- End customers via a partner. A software vendor, sector organisation or federation that has concluded a partner agreement with Vidimus can create organisations for its end customers through the partner API. Such an end customer is a Customer within the meaning of these terms: the records belong to it, it can export everything, and its content is encrypted with a key that the partner does not have. Towards Vidimus, the partner is responsible for the end customer's acceptance of these terms before the first record and for the accuracy of the end customer's data. Before the end customer's first logbook, its own director signs the mandate with the eID; the partner's mandate does not apply to the end customer.
- What the partner sees. Only counters and metadata of its end customers (names of logbooks, numbers, status); never content or attachments.
- Billing. With a reseller or integrator, the partner invoices its end customer and Vidimus invoices the partner. With a referral, Vidimus invoices the Customer directly; the referral changes nothing in these terms.
- Departure of the partner. If the cooperation between Vidimus and the partner ends, the end customer may continue directly under these terms, keeping its records, keys and verification links; Vidimus and the partner cooperate in the transfer.
Data processing agreement.
For personal data in records, the Customer is the controller and Vidimus the processor (Art. 28 GDPR). This chapter is the data processing agreement.
- Subject matter and duration. Processing of the data that the Customer and its people include in records (names of signatories, times, positions, content and attachments), for as long as the agreement runs and afterwards during the retention period of the logbooks.
- Instructions. Vidimus processes data exclusively to provide the service and according to the Customer's settings per logbook. No other use, no sale, no profiling.
- Security. Content and attachments are encrypted on receipt (AES-256-GCM) with a separate key per document, which in turn is wrapped under a key per organisation; two organisations cannot read each other's content. Every decryption by the server (dossier, bundle, search) is logged and visible to the Customer. Only the fingerprint goes into the ledger. For logbooks with personal data, a secret salt per record is included in the fingerprint, so that the fingerprint itself does not reveal any personal data; that salt is in the evidence bundle of that record, so that an expert can recompute the fingerprint without Vidimus, and it says nothing about other records. Public check pages never show the salt. Records from before 28 September 2026 use a secret key per logbook (HMAC) and remain recomputable that way. Originals are written once and also go to storage with Object Lock in the EU. Access to systems is limited to the managing director of VO Initiatives BV and is logged.
- Confidential logbook. The Customer can make a logbook confidential. The Customer's devices and systems then encrypt the content with a company key that the Customer creates and keeps itself; Vidimus receives only the public half, the envelope (type, reference, source) and the fingerprints, and cannot read the content. Services that need the content (dossier with content, before and after, searching in the content, recording web pages, measurements) are not available for that logbook. The Customer keeps the recovery file and the passphrase itself. If the Customer loses both and all devices with the key, nobody can open that content any more, not even Vidimus; the proof that something existed, when, and who signed, remains.
- Erasing without breaking the proof. At the Customer's request, Vidimus destroys the content key of a single record. The content is then permanently unreadable, also for Vidimus; the chain of fingerprints remains unbroken.
- Sub-processors. Hetzner Online GmbH (hosting and Object Storage, Germany, EU); a qualified timestamping service on the EU trusted list (qualified timestamps over Merkle roots; receives only hashes); Sectigo Limited (RFC 3161 timestamps over Merkle roots; receives only hashes, never content or personal data); the public OpenTimestamps calendar servers (Bitcoin anchoring; receive only hashes); Stripe Payments Europe Ltd (payments and invoices: the Customer's company and contact details, never record content); Recommand (Peppol access point for e-invoices: invoice data); Google Ireland Ltd (sending emails such as invitations and notifications: name and email address of the recipient); Anthropic, PBC (the assistant in the app, United States: only when a user asks the assistant a question does Anthropic receive that question and the data the assistant looks up for it within the Customer's organisation, exclusively to draft the answer; transfer outside the EU on the basis of the European Commission's standard contractual clauses). Changes are announced thirty days in advance; the Customer can object and terminate.
- AI services the Customer connects itself. If the Customer connects its own AI service (such as ChatGPT, Claude or Grok) via the MCP connection or the API, that service retrieves data on the Customer's instructions and under the Customer's own agreement with that provider. That provider is not a sub-processor of Vidimus; the Customer chooses which key and which rights it gives that service.
- Data breaches. Vidimus notifies the Customer of a breach without undue delay and at the latest within 48 hours of becoming aware of it, with the information the Customer needs for its own notification.
- Assistance and audit. Vidimus assists the Customer with requests from data subjects and with a data protection impact assessment. The Customer may have an audit carried out once a year, or after an incident, at its own expense, after reasonable notice.
- End. After the agreement and the retention period, Vidimus deletes the content and attachments. Fingerprints, timestamps and ledger entries contain no personal data and remain as proof.
How you accept.
When creating an account, the person responsible for the organisation ticks a box to confirm that they accept these terms and the data processing agreement. That acceptance is anchored as a record in the organisation's "agreements" logbook: organisation, user, time, version number, address and device. Both parties can check it afterwards on app.vidimus.be under Settings (Instellingen in the app), and without Vidimus via the evidence bundle.
Before the first logbook, the organisation identifies itself: an officer listed as such in the Belgian company register (KBO), for example a director or managing director, signs the mandate with the Belgian eID. That mandate is anchored in the "agreements" logbook. Logbooks from before this version was introduced keep working without a mandate; their evidence bundles state that the organisation has not been independently identified. An organisation that cannot provide a Belgian eID signature (a foreign company, a director without a Belgian eID) contacts Vidimus, which looks at the situation personally.
Questions: oskar@vo-initiatives.com.
Version 2026-11 · 1 November 2026: people's keys stay on their device, a system that sends records can keep its own key, otherwise Vidimus stores it encrypted; timestamp within five minutes, qualified usually within six hours; term from month to month or an annual contract with monthly payment; sub-processor Anthropic added (assistant in the app); AI services the Customer connects itself; qualified timestamp for records of customer organisations, usually within six hours and as long as the annual package has capacity; the signatures described without a legal qualification (13 October 2026); before the first logbook, a director identifies the organisation with the eID, chain partners and end customers of partners also sign themselves, and what an invited organisation records on a logbook of the Customer counts as the Customer's usage (15 October 2026). Existing organisations are presented with this version in the app again for acceptance · Version 2026-10 · 28 September 2026: new version (measurements only from a measurement source with a unit and a range, the old input endpoint counts per record, reclassification in case of misuse of the measurement endpoint; payment and what happens with an unpaid invoice; personal data: secret salt per record in the fingerprint instead of one key per logbook; confidential logbooks with a company key that only the Customer has) · 27 September (price per record and per source, without bundled packages; chain partners create their own account; qualified timestamp included, within six hours) · 26 September (new chapter on software partners; measurement, record and bundled packages according to the pricing model of 25 September; vault: key per organisation and access log instead of encryption on the device; sub-processors supplemented with Object Storage, OpenTimestamps, Stripe, Recommand and email sending) · 11 September: trial subscription and menu names clarified · 3 September: addition on shared logbooks