Privacy-first
Only the hash leaves the device. Originals never upload.
Hash-only input No content storage
Status: Public Beta v0.2 · ProofSpec v0.1 · API v0.2 · Privacy-first · No blockchain
About
Mission, values, and transparency behind TimeProofs — a minimal, privacy-first protocol that issues signed
.tproof.json proof bundles and supports offline verification.
Mission
TimeProofs answers a simple question: when did this data exist, and has it changed?
You hash locally, receive a signed .tproof.json bundle, and anyone can verify it later
online by submitting the proof bundle (no original upload) or offline locally.
Stateless v0.2: verification is bundle-based. A hash alone cannot be verified without the bundle.
Values
Open verification
Anyone can verify via the public API or offline with a ProofSpec-compliant verifier.
Public verify Offline
Minimal & durable
A small, auditable spec designed to outlive providers and remain interoperable.
ProofSpec Stable format
How it works (v0.2)
- Hash locally (your device computes SHA-256 or equivalent).
- Request a signed timestamp from the stateless API.
- Download the signed
.tproof.jsonproof bundle. - Verify later by submitting the bundle (online) or by verifying locally (offline).
Integration details and examples are documented in API Docs.
Limits
It does
- Prove a hash existed at a time (issued/signed).
- Prove integrity against the same hash later.
- Support offline verification.
It does not
- Prove authorship, ownership, or intent.
- Prove delivery, reading, acceptance, or consent.
- Provide notarization or legal certification.
See the full disclaimers on Legal.
Transparency
- Protocol: ProofSpec is public and designed for interoperability.
- Reference implementation: the public API is stateless (v0.2).
- Security: disclosure policy via security.txt.
- Privacy: data minimization described in Privacy.
Contact
General: contact@timeproofs.io · Security: security@timeproofs.io