DataSeal.net
Learning center

Guide

Proof modes

Every DataSeal.net timestamp uses the same clone-proof fingerprint and blockchain anchor. Modes control what else is stored with that proof—and how private your original content remains.

What all modes share

Regardless of mode, creating a timestamp costs 1 credit and produces:

  • A SHA-256 fingerprint of your exact bytes (file or text)
  • A dashboard entry you can open, share, or download as a package
  • Blockchain anchoring so others can verify when that fingerprint was recorded

Modes only change payload storage and who can read the original content later. They do not change the strength of the cryptographic proof.

The same choices as Create timestamp

These are the three options you see in the dashboard. Tap a card to jump to that mode's details.

Private proof

Hash

Private hash proof — content stays with you.

Stores
Fingerprint only
Best for
IP, drafts, max privacy
Protected storage

Encrypted

Encrypt in-browser before anchoring.

Stores
Ciphertext (you hold the key)
Best for
Privileged documents
Public record

Public

Readable archive for effortless verification.

Stores
Readable archive
Best for
Disclosures & notices

Hash mode

Private proof

Private hash proof — content stays with you.

Hash (sometimes called hash-only) fingerprints your payload in the browser and stores only that fingerprint plus metadata you choose. The original file or text never leaves your device as stored content on DataSeal.net.

  • Privacy — maximum. Even with a public proof page, visitors see the certificate and hash, not your draft.
  • Your responsibility — keep the original bytes. Without them, nobody (including you) can re-hash and prove a match later.
  • Packages & shares — downloads do not include a payload file; live pages cannot offer payload download.

Ideal before sharing ideas with collaborators, investors, or AI tools—when you want dated proof without uploading the sensitive source.

Encrypted mode

Protected storage

Encrypt in-browser before anchoring.

Encrypted mode encrypts your payload in the browser with AES-GCM before upload. DataSeal.net stores the ciphertext and anchors a fingerprint of the original plaintext (so verification still matches your real content).

  • Key custody — the decryption key is shown once at create time. Copy or download it immediately; we cannot recover it.
  • On a proof page — you may optionally allow ciphertext download. Recipients still need your key to decrypt.
  • In a package — the ZIP includes the .enc file plus offline decrypt tools in certificate.html.

Use this when you need an archived copy under your control, but not an openly readable file on the internet.

Public mode

Public record

Readable archive for effortless verification.

Public mode stores a readable copy of your file or text alongside the fingerprint. Anyone with access to the payload (via a share that allows download, or a package you send) can open the original content and hash it to match the certificate.

  • Transparency — simplest path for notices, disclosures, and records meant to be inspected.
  • Share carefully — a live proof page can optionally enable payload download for visitors while the share is active.
  • Not for secrets — if the content must stay confidential, choose Hash or Encrypted instead.

See an example public proof page — open a live certificate in your browser (no account required).

Choosing a mode

  1. Need maximum privacy and you will keep the original yourself? → Hash
  2. Need an archived copy but not public readability? → Encrypted
  3. Content is meant to be opened and inspected by others? → Public

You pick the mode when you create a timestamp. It cannot be changed later for that entry—create a new proof if your privacy needs change.

Related guides