Electronic signature and evidence
Legally valid electronic signature, with evidence of what was signed
Delivering the work is the easy part. Proving it was done properly —to a client, an inspector or a board— is what nobody has solved. A document accepted by email evidences neither who accepted it, nor when, nor against what exact text.
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.
A consent or an engagement you can't evidence is the same as not having one: art. 5.2 GDPR puts the burden of proof on the controller.
The badges identify the obligation the program digitises. They are not certifications or conformity accreditations.
What gets handed over when somebody asks
- A signed document with a record of signatory, date and cryptographic hash
- An advanced signature certificate from the eIDAS provider where the document needs one
- A record of in-platform acceptance with a timestamp and the version of the text accepted
- Traceability of later changes: if the document changes, the hash stops matching
Lo que nos preguntan sobre Signature and evidence
The advanced one is issued by a provider certified under eIDAS and identifies the signatory to a higher standard. In-platform acceptance records the user, a timestamp and the document hash: it's a simple electronic signature, valid wherever the rule doesn't demand stronger identification.
Per document. There's no sense paying for an advanced signature on an internal acceptance, nor settling for a simple one where the rule asks for more.
No. The signature lives inside the file that produced it, so the signed document and the case it belongs to are never separated.
A 30-minute guided demo on the real platform, or a one-hour assessment session with a consultant.
