FOR AI LABS
Hashproof signs generated output with durable C2PA provenance, records the training-data lineage you register so you can check membership against it by perceptual similarity, and produces EU AI Act disclosure reports from your stored corpus. The standard regulators and platforms are converging on.
Three pressures arriving at once: regulation, rights, and durability.
EU AI Act Article 50 requires that synthetic content be machine-readable as such, with enforcement beginning August 2026. Voluntary labeling that any tool can strip is easy to lose and hard to evidence when a regulator asks for a durable, checkable record.
When a rights holder asks whether their work was in a training set, or a downstream user asks what a model was trained on, most labs cannot answer with evidence. The provenance of training corpora is rarely captured in a checkable form.
A generated image loses its metadata the first time it is screenshotted or re-encoded by a platform. A label that only lives in EXIF is gone within one hop, exactly when downstream systems need to know the content is synthetic.
Four primitives spanning output labeling and training-data lineage.
Store the C2PA manifests your generation pipeline signs, including AI-generation assertions such as c2pa.ai_generative. Stored manifests carrying those assertions are counted in EU AI Act compliance reports and stay retrievable by ID.
Register datasets and ingest the fingerprints of your training samples, then check membership: does an asset perceptually match something you registered. A match is a similarity match against the corpus you declared — not proof of what a model actually trained on — and a non-match means only that nothing you registered was close enough, not that the asset was never used.
Soft-binding resolution can often reconnect a screenshotted or re-compressed generation back to candidate manifests. Downstream platforms can often recover the synthetic label by resolving the asset back to those candidates, even after re-encoding — a similarity match, not a guarantee.
Generate EU AI Act Article 50 reports directly from your stored manifests. Each finding cites its manifest, so disclosure becomes a query against the record, not a manual audit.
From training-data registration to disclosure. Your training and inference stacks stay in place.
01
Register training datasets and ingest perceptual fingerprints through the API. The corpus becomes queryable for membership without exposing the underlying assets.
02
Your generation pipeline stores a C2PA manifest for each output, carrying the AI-generation assertions your signing tooling adds. The stored record is retrievable and verifiable through the API.
03
You can answer membership queries from rights holders and auditors against your registered datasets, and verify any generated asset against its manifest — including re-encoded copies that soft binding can often match back to candidate manifests.
04
The compliance endpoint produces Article 50 disclosure reports from the stored corpus, with each finding cited by manifest ID, ready for a regulator or a partner.
Disclosure infrastructure that does not ask you to expose the model.
C2PA is referenced across emerging AI-content rules and backed by a Linux Foundation membership spanning model providers, platforms, and hardware. Building on it means your disclosures verify in the same tools regulators and platforms use.
Manifests record that content is synthetic, and dataset registration lets you check membership against the corpus you declared, without revealing weights, prompts, or proprietary pipeline detail. Selective disclosure lets verification reveal only the fields you choose and replace the rest with their hashes. A zero-knowledge proof that confirms valid provenance while revealing nothing else is in development, available today as a labeled beta preview.
Hashproof labels and verifies. It does not judge outputs or gate generation. The provenance layer states facts about an asset; policy decisions stay yours.
One provenance layer across disclosure, transparency, and interoperability requirements.
For the reporting surface, see the compliance reporting page.
Start on the Free tier and sign a generation pipeline end-to-end. Volume lives on Scale and Enterprise; a standard DPA is published for all customers.