Status: Public Beta v0.2 · API · Privacy-first · No blockchain
Use Cases
Practical scenarios where proof of existence changes everything — without uploading your data.
Overview
What TimeProofs gives you: a small proof file you can keep and share. It proves when an exact piece of content existed and that it has not changed.
File date ≠ proof: file dates are local and editable. A proof is independently verifiable.
Privacy-first: your original content stays on your device. The proof file contains only a SHA-256 fingerprint (hash) and a signed timestamp.
Keep the .tproof.json proof file with your artifact. Stateless verification requires the full proof file.
1) AI outputs & agent traces
What you prove
- When an exact output (or prompt) existed.
- That it hasn’t changed since.
Why teams use it
- Make AI runs auditable without storing sensitive content in third-party systems.
- Attach proofs to outputs, evaluations, and intermediate steps.
Artifact: keep the proof file next to your logs.
2) Audit trails & compliance
What you prove
- Prior existence of a policy, decision, report, or disclosure.
- Integrity across revisions (one proof per version).
Why teams use it
- Show that a document existed before an incident, dispute, or deadline.
- Reduce ambiguity during audits.
Artifact: one proof file per finalized version.
3) Releases & builds
What you prove
- Which artifact was shipped (exact fingerprint).
- When it was issued.
Why teams use it
- Build integrity and supply-chain confidence.
- Attach proofs to release notes and shipped artifacts.
Artifact: a proof file for each release artifact.
4) Creators & deliverables
What you prove
- When a specific work existed (image/audio/doc).
- That shared copies match the certified version.
Why teams use it
- Clear evidence for deliverables and handoffs.
- Simple, portable proof you can attach anywhere.
Artifact: work.ext + work.ext.tproof.json.
5) Datasets & research
What you prove
- When a dataset snapshot existed.
- That the dataset used for analysis is the same later.
Why teams use it
- Reproducibility for research and model training.
- Verifiable snapshots for sharing and publishing.
Artifact: one proof file per dataset snapshot.
6) Supply chain & vendor artifacts
What you prove
- Integrity of delivered packages, SBOMs, and configs.
- Traceable issuance timestamps across vendors.
Why teams use it
- Less ambiguity in procurement and incident response.
- Clear evidence for “what was delivered, when”.
Artifact: attach a proof file to each deliverable.
Recommended workflow
- Hash locally (SHA-256) the exact bytes you care about.
- Create a proof via Create / Verify or the API.
- Store the
.tproof.jsonproof file next to the artifact. - Verify later using the proof file (offline or via stateless verification).
The proof file is the portable artifact you can keep, share, and inspect.
Best practices
- Reproducibility: for text, use UTF-8 and stable line endings if you need consistent hashes across systems.
- Minimal metadata: avoid personal data; keep proofs portable and neutral.
- Versioning: one proof per version/snapshot/release.
- Keep proofs: store the
.tproof.jsonfile with artifacts (not only links).
Implementation details and endpoints are in API Docs.
Try it now
Use Create / Verify to create a proof in seconds, or verify an existing .tproof.json.
Developer integration lives in API Docs.
Mini FAQ
Do you store my files? No. Your original content stays on your device.
Is a file date enough? No. File dates are editable; proofs are verifiable.
Blockchain required? No.
Next: API Docs · ProofSpec · Create / Verify