🔏 Release — Verified
🔐 Privacy-first • ⚡ Edge-native • 🌍 Open Protocol

Prove When Data Existed. Privately.

Hash anything on your device. Receive an instant, signed timestamp. Anyone can verify later that it existed and is unchanged — without seeing your data.

One self-describing JSON proof readable by any ProofSpec-compliant tool.

Regulations & Compliance →

No account · No content stored · Hash locally · Signed timestamp · Public verification · No blockchain

Create / Verify a Proof
⏱ <100 ms edge 🛡 Hash-only, no PII 🌍 Public verification
DEMO Quick Check
Local hash → API verify

Demo only. Your text is hashed locally, then verified via the API. For signed proofs and options, use the full tool.

Mission

What we’ve built

TimeProofs is an open, neutral standard for digital proof of existence. One JSON proof any compliant tool can read.

Create/Verify →

Why it matters

Generated content and critical data need provenance. A verifiable fingerprint solves “did this exist then, and is it unchanged?”

See use cases →

ProofSpec

A minimal, auditable spec to certify existence and integrity without storing originals.

Explore ProofSpec →

Built for teams that need proof

AI teams · Data & Security · Legal & Compliance

How It Works

Model: Hash locally → Signed timestamp → Public verification

1) Hash locally

const buf = new TextEncoder().encode(text);
const digest = await crypto.subtle.digest('SHA-256', buf);
const hash = [...new Uint8Array(digest)]
  .map(b => b.toString(16).padStart(2,'0')).join('');

2) Timestamp

const r = await fetch("https://api.timeproofs.io/api/timestamp", {
  method:"POST",
  headers:{ "Content-Type":"application/json", "Accept":"application/json" },
  body: JSON.stringify({ hash, type:"event", meta:{ source:"web" } })
});
const proof = await r.json();

3) Verify anywhere

const res = await fetch(
  "https://api.timeproofs.io/api/verify?hash="+hash,
  { headers:{ "Accept":"application/json" } }
);
const check = await res.json();

Output: a self-describing .tproof.json with hash, algorithm, signed timestamp, and a public verify URL.

Protocol vs API

Protocol — ProofSpec

Open rules, interoperable, peer-verifiable. Designed for standardization and independent validation.

Read ProofSpec v1 (Draft)

API — Reference implementation

Edge-native reference with predictable latency and auditable logs. Drop-in examples to ship fast.

Open the API Docs

Why TimeProofs

Instant Proof

Milliseconds at the edge. No accounts. Predictable costs.

Privacy-First

Only the hash leaves the device. Originals never upload.

Interoperable

Proofs read by any client that follows ProofSpec.

AI-Ready

Provenance for prompts, outputs, datasets, and chains.

Open & Auditable

Public verification by anyone, with verifiable logs.

Edge-Native

Fast, efficient, globally distributed architecture.

Regulatory Readiness

Traceability without personal data. Open verification. Stateless by design.

EU AI Act

Traceability for model inputs/outputs with signed, auditable events.

Signed timestamp · Public verify

GDPR

No content stored. Hash-only. Minimal, purpose-bound logs.

Privacy by design · No PII

Data Act / DSA

Integrity and provenance for shared and programmatic data flows.

Event proofs · Audit trail

NIS2 / Supply chain

Release integrity for CI/CD: binaries and artifacts carry proof links.

Proof links · Edge-native

Read full Regulations & Compliance →

🔏 Proof of Release

Verified by TimeProofs

We publish a public proof of this website build. Anyone can check it.

Release: … · Hash: … · Verify

Each build is timestamped and linked here. “Verify” opens a public endpoint that returns the signed record used to prove existence and integrity.

Learn more on Regulations & Compliance and transparency on About.

Planned: Product Hunt launch, Dev.to deep-dive, GitHub release, and W3C Community Group proposal.

Ready to prove it?

Create / Verify a Proof Learn the Spec

Looking for mission and transparency? See About →