Qualified Timestamping

A date that holds before a third party.

An internal timestamp can be edited in a database. eIDAS qualified timestamping (RFC 3161) is a stamp delivered by a qualified trust service provider (QTSP): it carries a presumption of date accuracy and data integrity.

DIRECT ANSWER

eIDAS qualified timestamping is an electronic timestamp delivered by a qualified trust service provider (QTSP), conforming to RFC 3161. It establishes a presumption of accuracy of the date and time, and of the integrity of the associated data, under Article 41 of the eIDAS Regulation (910/2014).

THREE LEVELS

Internal timestamp

Editable by the vendor, no third party. No probative value.

Non-qualified timestamp

Delivered by a timestamping authority, but without qualified status. Useful, but no legal presumption.

eIDAS qualified timestamp

Delivered by a qualified trust provider, audited and supervised. Presumption of date accuracy and integrity (Art. 41 eIDAS).

QTSPs are partners, never enemies. Qualified timestamping is integrated into 0DATA proof in co-processing with qualified providers (premium tier).

FAQ

What is eIDAS qualified timestamping?

An RFC 3161-compliant electronic timestamp delivered by a qualified trust service provider (QTSP). It carries a presumption of date/time accuracy and data integrity (Art. 41 eIDAS).

What is the difference between simple and qualified timestamping?

A simple timestamp (database) is editable by the vendor. eIDAS qualified timestamping is delivered by a regulated, supervised third party and carries a legal presumption of accuracy and integrity.

Is qualified timestamping enough to prove compliance?

No, alone it proves anteriority. To prove continuous compliance you also need continuous measurement at the source and public anchoring — the exact combination 0DATA implements.