Vidimus
Explainer videos NL Start free

VIDIMUS/PRIVACY

Privacy notice.

This is a translation. The Dutch version prevails.

applies toThe Vidimus app and app.vidimus.be

For the website itself: see colophon & privacy.

controllerVO Initiatives BV

Antwerp · KBO (Belgian company register) BE 0805.309.143 · oskar@vo-initiatives.com

coreNo advertising, no tracking, no sale of data

The app contains no third-party advertising or analytics scripts and does not follow you across other apps or websites.

DATA

What we process, and why.

  • Account data — organisation name, your name and email address, and a hashed password. Needed to provide your account (Art. 6(1)(b) GDPR).
  • Record content — the fields and attachments that you or your partners record. This is your own business data; we process it exclusively to anchor, display and prove it — never for our own purposes. Attachments are stored encrypted, with a separate key per document under your organisation's key; every decryption by our server appears in your access log, which you can see yourself.
  • Signing keys — a person's signing key is created on their device and never leaves it; we receive only the public half. For connected systems (TMS, ERP, sensor), we store the system key on our server, reachable only by the service itself; our backups are encrypted.
  • Location when signing — when someone signs on the shop floor or as a recipient with the app, the device requests the GPS position at that moment (latitude, longitude, accuracy). It is anchored with that record and is visible to anyone allowed to see the record. Anyone who refuses simply signs without a location; the record then states that there was no location. Purpose: to show where a handover took place (Art. 6(1)(b) and 6(1)(f) GDPR). Kept for as long as the record.
  • The administrator's eID mandate — a director who signs their organisation's mandate with the Belgian eID (electronic identity card) provides a signed PDF. The eID certificate in it contains the name and the national register number (the Belgian personal identification number). We store that PDF separately, not in evidence bundles; in our database, the national register number is stored only as a hash. Purpose: to show that whoever uses Vidimus for the company is authorised to do so (Art. 6(1)(b) and 6(1)(c) GDPR). When it is signed, the PDF is stored locked for ten years: until then, the storage does not allow erasing or overwriting, not even at our request. The report of the signing (name on the eID, name and email address of the administrator, the hashed national register number) is kept with the agreements below.
  • Agreements — when your organisation accepts the terms, the director signs the eID mandate or you link a device to a team member, this is recorded as a record in your organisation's standard "agreements" logbook: who, when and what. When the terms are accepted, this also includes name, email address, IP address and browser (user agent); for a device, the name and position of the team member and the device. Purpose: to show who accepted what (Art. 6(1)(b) and 6(1)(f) GDPR). Retention period: thirty years.
  • Technical log data — IP address and time at login and for API traffic, kept briefly for security and abuse prevention (Art. 6(1)(f) GDPR).
  • Camera and photo library — only with your explicit permission, and only to capture slips, reports or QR codes that you add yourself. The app never watches in the background.
RETENTION

How long.

Records are kept according to the retention period you set per logbook (for example 5 or 10 years — often a legal obligation in your sector). Deletion is done by crypto-shredding: the encryption key is destroyed, after which the content is permanently unreadable. We delete account data at the latest 12 months after the end of your contract; security logs after 12 months at the latest. Two exceptions: the agreements have a retention period of thirty years, and the PDF of the eID mandate stays locked for ten years.

The ledger and timestamps contain only cryptographic fingerprints (hashes), never the data itself. They cannot be traced back to the content and are pseudonymised: once the content and the salt have been erased, they can no longer be linked to a person. This way the proof remains while the data itself can still be deleted, exactly as the GDPR asks.

THIRD PARTIES

Who else is involved.

  • Hosting — Hetzner Online GmbH (Germany, EU). All stored data is within the EU.
  • Timestamps — an external timestamping service (Sectigo), GLOBALTRUST, a qualified trust service provider on the EU trusted list, and the public OpenTimestamps servers (Bitcoin) receive only hashes, never content or personal data.
  • Payments and invoices — Stripe Payments Europe Ltd (Ireland, EU) for payments and invoices, and Recommand as Peppol access point for the statutory e-invoice. They receive company, contact and invoice data, never the content of records.
  • Email — invitations, notifications and password resets are sent via Google Ireland Ltd (Gmail): name and email address of the recipient.
  • Assistant in the app — if you ask the assistant a question, your question and the data the assistant looks up for it in your organisation go to Anthropic, PBC (United States), exclusively to draft the answer. The transfer outside the EU takes place on the basis of the European Commission's standard contractual clauses. If you do not use the assistant, nothing goes to Anthropic.
  • An AI service you connect yourself — if your organisation connects its own AI service (such as ChatGPT, Claude or Grok) via the MCP connection or the API, that service retrieves data on your instructions and under your own agreement with that provider. That provider is not a processor of Vidimus.
  • Fonts — the pages load Instrument Sans and JetBrains Mono from Google Fonts; Google sees your IP address, nothing else.
  • Our mailbox — what you email us yourself (questions, reports, requests) arrives at Namecheap Private Email, the mailbox of oskar@vo-initiatives.com.
  • Push notifications — if notifications are switched on in the app on your phone, a notification goes through your device's push service (Apple, Google, Mozilla or Microsoft). That service sees an encrypted message, not the content of your records.
  • PDF viewer in the app — the app still loads the PDF reader (pdf.js) from cdnjs (Cloudflare); Cloudflare sees your IP address, nothing else.
  • This website and booking an appointment — vidimus.be is hosted on GitHub Pages (GitHub sees the IP address of visitors); you book a demo via Cal.com (name, email address, time). Neither of them processes data from the app.
  • Administration — the managing director administers the server via Tailscale (a secured network). Tailscale sees device names and connection data, no customer data.
  • No one else. No advertising networks, no analytics services, no data brokers. We do not sell or share your data.
RIGHTS

Your rights.

Deleting your account (Vidimus, VO Initiatives BV). In the app and on app.vidimus.be: More › Settings › Delete account (in the app: Meer › Instellingen › Account verwijderen), confirmed with your password. No longer have access to the app? Email oskar@vo-initiatives.com with the email address of your account; we confirm within 30 days. Thirty days later we erase your name, email address, password, two-step verification and sessions; until then, you can cancel. Records, timestamps and anchors are kept until the end of the retention period of their logbook, because they are proof, also for the other party (Art. 17(3)(e) GDPR). Drivers without an account delete their key by removing the app; the dashboard can also revoke a device.

Access, rectification, erasure, restriction, portability and objection: email oskar@vo-initiatives.com — we reply within 30 days. Complaints can be lodged with the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit, gegevensbeschermingsautoriteit.be). If your organisation records data of third parties in records, your organisation is the controller for that data and Vidimus acts as the processor; the data processing agreement is in chapter 6 of the terms.

Last updated: 25 October 2026