Document and evidence manager
Demonstrable integrity: hash, timestamp and chain of custody
The difference between a document and a piece of evidence is being able to prove it hasn't changed since it was created. That takes a cryptographic hash, a timestamp from a qualified provider, and a log of every access.
Screens from DSA Compliance v6.2 in a demo environment. All data shown is fictitious.
What the rule requires, and in which article
For information only, not legal advice. Always check against the consolidated text in force.
It has no penalty regime of its own: lacking demonstrable integrity weakens your defence in any proceeding and may itself breach the security measures of art. 32 GDPR.
The badges identify the obligation the program digitises. They are not certifications or conformity accreditations.
What gets handed over when somebody asks
- A SHA-256 hash computed at upload
- A qualified timestamp and an electronic signature on the document
- A chain of custody logging every access, user, device and time
- Versioning without deletion, with a stated reason for every change
- A read-only space for an auditor or inspector, with access logged
What we get asked about Document manager
A legal presumption as to date, time and the document's integrity, under art. 41 of the eIDAS Regulation.
Versions are never deleted: they're superseded by a new version with a stated reason. Retention rules and legal holds block deletion while they are active.
Through a read-only space limited in scope and with an expiry date, where every opening is logged.
A 30-minute guided demo on the real platform, or a one-hour assessment session with a consultant.
