Terms of use

registry.falsify.dev · effective 2026-07-18 · operator: Cüneyt Öztürk (falsify.dev) · contact hello@falsify.dev

1 · What this service is

A public, no-account registry for PRML manifests. You submit a YAML manifest; the registry canonicalizes it, computes a SHA-256, signs a receipt (Ed25519), obtains an independent RFC 3161 timestamp, mirrors the hash to the Rekor public transparency log, and serves a permalink. The registry proves when a claim was locked — never that the claim is true.

2 · Public and permanent — by design

Everything you submit is published immediately and is designed to be permanent. Receipts are content-addressed and countersigned by third parties (timestamp authority, transparency log) precisely so that no one — including the operator — can silently alter or backdate them. Do not submit anything you may later want removed. See /privacy before submitting.

3 · Acceptable use

Submit only evaluation manifests and hash anchors you have the right to publish. No personal data in any field (enforced for machine-detectable classes, your responsibility for the rest). No unlawful content, no secrets. Rate limit: 20 submissions per IP per hour.

4 · No warranty · no fees

The public registry is provided free, "as is", with no availability or retention warranty. Manifests are content-addressed, so any receipt remains independently re-verifiable from your own copy of the bytes even if this service disappears — keep your own copy of every manifest you commit. The spec is CC BY 4.0; reference implementations are MIT; you never need this service to verify a PRML hash.

5 · Removal

If content violates these terms or the law, the operator may unpublish the stored manifest bytes from this service. The hash's existence in external logs (RFC 3161 tokens, Rekor) cannot be recalled by anyone — that irreversibility is the product. Requests: hello@falsify.dev.