Court-ready evidence by default.
EU Article 41 when it matters.
Every Provlyn deposit is anchored with SHA-256 hashing, RFC 3161 timestamping, Bitcoin blockchain proof, and per-recipient watermarking — on every plan. Qualified eIDAS adds the EU legal presumption under Article 41, for evidence destined for court inside the European Union.
Four anchoring layers, one record
Each layer proves a different property. The first four are included on every paid plan. The fifth is optional, drawn from your eIDAS allowance.
SHA-256 cryptographic hash
A unique 64-character fingerprint of the file at the moment of deposit. If one byte changes, the hash changes. Universally verifiable using any standard tool.
RFC 3161 timestamp
A trusted third party signs the hash, certifying the moment of deposit. Standard cryptographic timestamping, accepted as evidence in UK, EU, and US courts.
Bitcoin blockchain anchor
Hashes are batched and anchored to the public Bitcoin blockchain via OpenTimestamps. Independent of any third party. Permanent and globally verifiable.
Per-recipient watermarking
Each shared document or audio file carries a per-viewer identifier embedded into the content. If material leaks, the watermark identifies the source recipient.
EU-qualified timestamp (Article 41)
Issued by a Qualified Trust Service Provider on the EU Trusted List. Carries the Article 41 legal presumption of accuracy and integrity across all 27 EU member states. The burden of proof shifts to whoever disputes the timestamp.
How eIDAS is applied on Provlyn
Two distinct contexts. One automatic and bundled with your plan. The other per-deposit and drawn from your eIDAS allowance.
Daily access-log anchoring
Every vault produces an access log recording who viewed, downloaded, or shared what, and when. Once a day, the entire previous day's log is merkle-batched and anchored with a single qualified eIDAS timestamp. The audit trail itself carries Article 41 weight. Included on every paid plan.
Optional on individual deposits
When you upload a file, Provlyn shows a checkbox asking whether to apply qualified eIDAS to that deposit. The checkbox is unticked by default, so the free triple anchor applies on its own unless you actively choose to add the qualified layer. Each application draws one stamp from your monthly allowance or your standalone packages.
Questions about how eIDAS works, who issues the timestamps, or how to verify them?
See the eIDAS section in the FAQ →