What you get
A proof file you can store and share (.tproof.json).
A signed timestamp from a stateless API (no server-side storage required).
Independent verification later (online or offline) to confirm the content existed and is unchanged.
Status: Public Beta v0.2 · Stateless API · Privacy-first · No blockchain
Prove when a file existed — without uploading it.
When a file is disputed, a “creation date” or a screenshot is not proof.
TimeProofs creates a verifiable proof file (.tproof.json) that shows when this exact content existed and that it hasn’t changed — without revealing the original.
Developers: see API Docs.
🔏 Verifiable proof file
🛡 Your content stays private
⚡ Edge-fast
🌍 Open standard
A file date is not proof
A file “creation date” is local and editable. A TimeProofs proof is verifiable: it proves when an exact piece of content existed and that it has not changed.
TimeProofs doesn’t certify intent or origin. It certifies two facts: existence at a time and integrity over time.
What TimeProofs is (and is not)
Why it’s safe
Privacy-first: your original content stays on your device.
Open protocol: designed to be implemented by other tools and verifiers.
Domain-agnostic: works for files, AI outputs, datasets, releases, audits.
What it’s not
Not storage: TimeProofs doesn’t host your content.
Not blockchain: no chain, no tokens, no mining.
Not identity / authorship: it doesn’t prove who created it, or why.
Examples of when a proof matters
Situations where “this existed then” becomes critical:
Contract or document before changes
Keep a verifiable record of the exact version you had at a specific time.
Report or policy before an audit
Show what was published internally (or externally) before review or investigation.
AI output used in a decision
Freeze the exact output that influenced a human or automated workflow.
Dataset or research snapshot
Prove the state of data at time T, and detect any later changes.
Software release or technical specification
Attach a proof to releases or specs to support integrity and traceability.
In these moments, a file date or a screenshot is not enough.
How It Works
Three steps: hash locally → request a signed timestamp → verify with the proof file
1) Hash locally (SHA-256)
Your device computes a SHA-256 hash of your content. The original content never leaves your device.
2) Request a signed timestamp
No content is uploaded — only a cryptographic hash is sent. The API returns a signed timestamp for your proof file.
3) Download & verify the proof file
You store the proof (.tproof.json) next to your content. Anyone can verify later that the content existed at that time and hasn’t changed.
Want technical details and examples? See API Docs and Use Cases.
Why TimeProofs
Private by default
Your content stays with you. The proof is designed to be shareable without revealing the original.
Verifiable later
Independent checks, without relying on trust in a single platform or a screenshot.
Built for real-world proof
Useful for files, AI outputs, datasets, audits, releases, and compliance workflows.
Compliance context: Regulations & Legal framework →
🔏 Proof of Release
Verified by TimeProofs
We publish a signed proof file for this website build, so anyone can independently verify integrity. Verification requires the proof file (.tproof.json) — no hash-only verification.
Release:
… ·
Hash:
… ·
Verify (upload proof file)
Values are loaded from the v0.2 release manifest (/releases/v0.2.json) with v0.1 kept as an archive.
Ready to prove it?
Looking for mission and transparency? See About →