Validation build: the evidence log is live; the pricing example is simulated and places no cover. What that means

No integration, no software to install, and the file never leaves your computer

Seal a file today. Prove later that nobody changed it.

An advice note, a signed contract, an email you sent, a report you filed: choose the file below, or the folder that holds them, and press Seal. Your browser computes its fingerprint; we record only a salted fingerprint of that, in a log nobody can edit, including us. You download a small receipt and keep it next to the file. Years later, anyone you give both to can check, on this page or with the free offline verifiers, that the file is exactly the one sealed, and when.

Seal

Any file, any size, or drop it on this box. It is read here, in your browser, and never uploaded.
Every file in it, sealed together as one entry. Your browser may ask whether to “upload” the files: that only lets this page read them here. Nothing is sent but one fingerprint.

No account, no form, no email. The first seal takes a free sandbox key for you, kept in this page only; sandbox keys seal up to 50 files a day.

I already have an API key
Kept in this page only, never stored. Seals made with it are recorded against your account.

Check

Given a file and its receipt, this checks that the file is the one sealed, that the log recorded it, and that we signed the log’s state, against our published key. A folder is checked file by file: anything missing or changed fails. One file from a sealed folder can be checked against the folder’s receipt. Nothing is uploaded.

What a seal proves, and what it does not

It proves
that this exact file existed no later than the moment its seal entered the log, and has not changed by a single byte since. The log’s signed state is time-stamped by two independent authorities (not qualified under eIDAS) and anchored in Bitcoin.
It does not prove
who wrote the file, that what it says is true, or that it satisfies any law. It shows the file is the one you had at the time; whether that file is enough is yours to judge.
Checkable without us
The receipt is a standard record bundle. The open-source verifiers check it offline: python3 riskrouter_verify.py receipt.json --key anchors/. Verifiers and keys
A folder
is one entry in the log, however many files it holds (up to 10,000). The receipt lists each file’s path inside the folder and its SHA-256, in the format sha256sum writes, and that list is what is sealed. It proves those files were there, as they were; a file added later is not covered, and is said so when you check. .DS_Store, Thumbs.db and desktop.ini are left out: the system rewrites them when a folder is only opened.
For many files
Sealing by hand suits a few files a day. For every advice note your software writes, the same seal is one API call from inside it. Integrate