Exact file — recommended
Protects the exact bytes of any file through FRS-01. If a single byte changes, the source no longer matches.
The essentials for creating, preserving, sharing and verifying a PTC declaration.
Select the file or reference
Choose what you want to protect
Declare AI involvement
Generate and preserve the package
Verify it later
Protects the exact bytes of any file through FRS-01. If a single byte changes, the source no longer matches.
Protects canonical content under R-01. Some normalised physical differences can preserve the same textual identity.
Protects a normalised official reference when the source file is unavailable.
Preferably keep the complete generated ZIP.
Preferably keep the package; the canonical textual artefact with PTC can also verify the declaration.
Keep the package and the reference used.
Practical rule: whenever possible, send or archive the complete package.
The integrity of a PTC declaration and its cryptographic correspondence with the protected object. In a package it can also check the source, package structure and, where present, public disclosure.
Exact file is recommended when you want to protect the complete file as it exists. Textual content is for canonical text. Official reference is used when the source file is unavailable.
Any finite byte sequence that the browser can process within its operational limits: images, audio, video, ZIP, spreadsheets, code, datasets and other formats.
Yes. TXT and Markdown provide the most reproducible textual route. DOCX and PDF remain supported through document adapters, subject to the extraction limitations reported by the verifier.
No. PTC is declarative. Validator detects technical inconsistencies; it is not a lie detector. Provenance, date or priority may require external anchors.
In exact-file mode, any byte change causes the source to stop matching the protected reference.
Yes, when physical differences disappear under the R-01 normalisation rules. Textual mode protects the canonical object, not every byte of the physical file.
No. It records declared authorship but does not prove identity, originality or legal authorship.
Whenever possible, the complete package. This keeps together the pieces needed to verify each applicable axis.
It depends on the mode. In exact-file mode, without the source the declaration and descriptor can be checked, but the verifier cannot state that a particular file matches them.
It separates the results for the PTC declaration, source file, package structure and, where present, public disclosure. An issue in one axis should not hide the status of the others.
Yes. The verifier retains compatibility routes for earlier PTC distributions and for textual or document artefacts that remain supported. The current flow is recommended for new declarations.
No. Content processing takes place locally in the browser. Validator does not require an account to create or verify.
No. The website also processes locally. Portable is for working without depending on access to validator.es, for example in isolated or offline environments.
An optional profile that can bind a disclosure declaration to the same protected object and derive a public notice. It does not replace PTC.
No. It can verify correspondence between the included notice and the protected declaration, but it does not prove actual public display or, by itself, satisfaction of a specific legal obligation.