Who issues the timestamp?

An external time stamping authority that follows the RFC 3161 standard. We use DigiCert's service and, if it does not respond, a backup. We do not set the date: a third party does.

Is it a qualified timestamp?

No. It is a third-party RFC 3161 timestamp, not a qualified electronic timestamp under the EU eIDAS regulation or from an accredited provider in Chile. It works as technical support; its weight in a proceeding is decided by the competent authority.

In file, photo and chat certification, no: your browser computes the fingerprint and only that fingerprint travels. In website capture we keep the captured files for 24 hours so you can download them.

Does it replace a notary?

No, and it does not promise legal value. A notary or an expert can attest to facts a technical certificate does not cover. Ask a lawyer in your country if you need it in a lawsuit or official process.

What if I change the file afterwards?

Its fingerprint changes and stops matching the certificate. That is why you must keep the original untouched: we do not store it.

Can anyone check a certificate?

Yes, with the code, on the verification page, no account needed. You can also select the file: its fingerprint is computed in the browser and compared with the certificate's.

How a timestamped certificate works

Updated October 14, 2026

The short answer

A Tinta Tech certificate fixes two things: your file's SHA-256 fingerprint (which changes if a single byte is altered) and a date signed by a third party (an RFC 3161 timestamp). It proves that this content existed as-is no later than that date. It does not prove who created it, that it is true, and it does not replace a notary.

Step by step: what happens when you certify something

Your browser computes the fingerprint. With the SHA-256 standard, on your device. The file is not uploaded.
We request the timestamp. We send only the fingerprint to a time stamping authority (DigiCert, with a backup), which signs it together with the exact time.
We check the response. We verify that what the authority returned matches the fingerprint we asked for. If it does not match or fails, we issue nothing: we never fake a timestamp.
We store the certificate. A unique code, the fingerprint, the file's name, type and size, the timestamp date and the authority's response. Not the file.
We generate the PDF with a QR code that leads to the public verification page.

What it proves

Integrity: the file you have today is identical, byte for byte, to the one that was certified.
A definite date: that content already existed no later than the timestamp date, according to an independent third party.

What it does not prove

Who created the file or that its content is true.
When it was originally created: only that it existed by that date.
That declared metadata (a photo's date and device, a chat's participants) is true: certificates label it as declared by the file itself.
Legal value: it does not replace a notary, a public official or a forensic expert.

How to check a certificate

On the verification page you can enter the certificate code or select the file: its fingerprint is computed in your browser and compared with the certificate's. If it matches, it is exactly the file that was certified. Anyone can do it, with no account and at no cost.

Today verification matches the fingerprint and shows the authority and the timestamp date. The authority's cryptographic signature is not validated on our server, and we do not yet offer downloading the timestamp to check it with external tools. If you need that level of independent verification, ask at hola@tintatech.com.

AI detectors are estimates, and we measure them

The image and audio detectors give an estimate in three levels (probably made by a person, cannot be determined, probably AI-generated), with a confidence level and stated limits. Never a percentage or proof. We tested our detectors with samples of known origin; the text detector was not reliable in that test and is out of service until there is a better one.

Frequently asked questions

Who issues the timestamp?: An external time stamping authority that follows the RFC 3161 standard. We use DigiCert's service and, if it does not respond, a backup. We do not set the date: a third party does.
Is it a qualified timestamp?: No. It is a third-party RFC 3161 timestamp, not a qualified electronic timestamp under the EU eIDAS regulation or from an accredited provider in Chile. It works as technical support; its weight in a proceeding is decided by the competent authority.
Do you see my file?: In file, photo and chat certification, no: your browser computes the fingerprint and only that fingerprint travels. In website capture we keep the captured files for 24 hours so you can download them.
Does it replace a notary?: No, and it does not promise legal value. A notary or an expert can attest to facts a technical certificate does not cover. Ask a lawyer in your country if you need it in a lawsuit or official process.
What if I change the file afterwards?: Its fingerprint changes and stops matching the certificate. That is why you must keep the original untouched: we do not store it.
Can anyone check a certificate?: Yes, with the code, on the verification page, no account needed. You can also select the file: its fingerprint is computed in the browser and compared with the certificate's.

This page is general information, not legal advice. About us · See the tools