Use Cases

1) AI provenance (prompts, outputs)

What it solves. Prove origin and integrity for prompts, model outputs, and intermediate artifacts. Share a public verify URL without exposing content.

Why TimeProofs. Local hashing, signed edge timestamp, and open verification make AI activity auditable without leaking data.

// How it works
1) Client hashes prompt or output bytes (SHA-256).
2) POST /api/timestamp { hash, type:"ai", meta:{ model:"gpt-4o", run:"2025-11-07" } }
3) Store the proof JSON or verify URL with the run metadata.

# Shell snippet
HASH=$(printf "%s" "$OUTPUT" | sha256sum | awk '{print $1}')
curl -s https://api.timeproofs.io/api/timestamp \
  -H "Content-Type: application/json" \
  -d "{\"hash\":\"$HASH\",\"type\":\"ai\",\"meta\":{\"model\":\"my-model\"}}"

Compliance: EU AI Act (traceability & logging). GDPR: hash-only, no model inputs or outputs stored.

2) Legal & compliance audit trails

What it solves. Immutable proofs for filings, evidence chains, policies, NDAs, and disclosures, without uploading the documents.

Why TimeProofs. Time anchoring with public verification, zero content retention, and a standard JSON proof format.

// Process
- Hash each PDF, contract, or policy file.
- Timestamp the hash via TimeProofs.
- Archive the proof JSON with the case or policy dossier.
- Share the verify URL with courts, auditors, or regulators.

Regulatory posture: helps demonstrate integrity and prior existence under GDPR, eIDAS-style evidence, and sector rules.

3) DevOps & secure releases

What it solves. Build and artifact integrity across CI/CD pipelines. Prove what was deployed, when, and from which artifact hash.

Why TimeProofs. Edge timestamps under 100 ms and a public verify API that can be embedded in your release notes.

# CI sample (bash)
HASH=$(sha256sum dist/app.min.js | awk '{print $1}')
curl -s https://api.timeproofs.io/api/timestamp \
  -H "Content-Type: application/json" \
  -d "{\"hash\":\"$HASH\",\"type\":\"release\",\"meta\":{\"source\":\"ci\",\"env\":\"production\"}}"

Compliance: supports NIS2, SBOM attestations, and supply-chain security programs.

4) Creators & media certificates

What it solves. Portable “proof bundles” for images, audio, video, and documents. You can prove you created or published something at a given time.

Why TimeProofs. Hash-only provenance and a simple .tproof.json bundle you can distribute with your work.

// Example bundle
{
  "version":"v0.1",
  "hash":"<64-hex>",
  "ts":"2025-01-01T00:00:00.000Z",
  "sig":"<hex>",
  "alg":"HMAC-SHA256",
  "type":"media",
  "issuer":"timeproofs.io",
  "meta":{"creator":"@handle","work_id":"my-photo-01"}
}

You keep the files. The world only sees hashes and verify URLs.

5) Data & research integrity

What it solves. Snapshot datasets, notebooks, and analysis outputs. Enable peers and reviewers to verify that what they see matches what was certified.

# Dataset example
HASH=$(sha256sum data.csv | awk '{print $1}')
curl -s https://api.timeproofs.io/api/timestamp \
  -H "Content-Type: application/json" \
  -d "{\"hash\":\"$HASH\",\"type\":\"dataset\",\"meta\":{\"version\":\"v1\",\"project\":\"study-42\"}}"

Compliance: aligns with Data Act expectations for data provenance and sharing.

6) Supply chain transparency

What it solves. Publish proofs for SBOMs, licenses, vendor deliverables, and configuration baselines.

// How it works
- Hash SBOM JSON, license packs, or configuration exports.
- Timestamp each hash.
- Include verify URLs in procurement docs and SLAs.

Helps demonstrate integrity across vendors and internal teams.

Compare options

TimeProofs. Hash-only, signed timestamp, public verify, no blockchain, privacy-first.

Traditional notarization. Manual, costly, sometimes requires content exposure.

Blockchains. Heavy, fees, latency, and potential PII or metadata leakage.

Quick FAQ

Do you store my files? No. Only hashes. Original content never leaves your device.

Can anyone verify a proof? Yes. Use the public verify endpoint or any ProofSpec-compliant client.

How fast are timestamps? Typical edge latency under 100 ms.

What about key rotation? Signatures support key IDs; verification remains stable across rotations.

Next steps: Create / Verify a proof · Read the API Docs · Learn the Protocol (ProofSpec)

This page is verified by TimeProofs

Release: … · Hash: … · Verify

The hash above is loaded from the central release manifest.