01
Fingerprint locally
The browser converts the source into a SHA-256 fingerprint. The original source text or file is not included in the proof request.
VERIFIABLE HUMAN CONTROL POINTS
Make human review
provable later.
HUMANPROOF gives teams a compact evidence layer for sensitive review and approval workflows. The source is fingerprinted locally; the proof service records the fingerprint and minimal non-sensitive context instead of centralizing the original content.
Source stays localSHA-256 fingerprintAuthenticated recordsDeterministic verificationPortable receiptEU-hosted pilot backend
THE PROBLEM
When a decision is challenged weeks or months later, teams often need more than the final document. They need to show what was reviewed, when the control point happened, and which exact source state the record refers to—without creating another repository of sensitive material.
02
Record the control point
The authenticated proof record contains the fingerprint, proof kind, creation time and only the minimal non-sensitive metadata needed for the workflow.
03
Verify later
Re-hash the source locally and compare it with the recorded fingerprint. A match establishes byte-for-byte correspondence with that record.
OUR POSITION
Evidence, not a verdict.
HUMANPROOF is deliberately narrow about what it proves. That makes the result easier to understand, defend and integrate into existing governance.
A recorded fingerprint corresponds to an exact source state.
It can document an authenticated proof record, its creation time in HUMANPROOF, its proof type and selected non-sensitive context. The record can be exported as a portable JSON receipt and checked deterministically against the source.
That matching content is true, lawful, owned, compliant or independently notarized.
A cryptographic match is evidence of correspondence—not a judgment about truth. The current pilot does not claim public-chain anchoring, external immutable timestamping, regulatory certification, C2PA conformance or guaranteed legal evidentiary status.
WHERE IT FITS
One evidence layer. Existing workflow.
Compliance & investigations
Preserve a reference to the exact evidence state used at a review or decision point.
AI governance
Record the human review or approval point around AI-assisted work without sending the underlying sensitive payload to HUMANPROOF.
Legal & audit operations
Create a compact, portable record that can later be checked against the material held in the system of record.
Quality & approvals
Bind a review checkpoint to an exact source version when later changes would otherwise make reconstruction difficult.
BUYER FAQ
Questions we expect—and answer precisely.
What exactly does HUMANPROOF prove?
It proves that the content you verify locally produces the same SHA-256 fingerprint as the fingerprint stored in a specific HUMANPROOF proof record. That establishes byte-for-byte correspondence with the recorded source state.
Do you upload or store our source document?
Not in the current proof workflow. Hashing and verification happen in the browser. Proof requests contain the fingerprint and selected non-sensitive metadata, not the source text or file. Pilot users should still use non-sensitive metadata only.
Does HUMANPROOF prove that a document is true or genuinely human-authored?
No. A fingerprint cannot establish factual truth, ownership, intent or authorship by itself. HUMANPROOF records a verifiable control point. The surrounding organization and workflow determine what that control point means.
Is this a blockchain or digital notarization service?
No. The current pilot does not claim public-chain anchoring, independent notarization or an external immutable timestamp. Those mechanisms may be evaluated later where customer evidence requirements justify them.
Is HUMANPROOF C2PA compliant?
Not currently. We follow compatible design ideas—clear assertions, verification, privacy and portable evidence—but we do not claim C2PA conformance until an actual conforming implementation exists.
Why not just store the original file in another audit system?
Many teams already have systems of record. HUMANPROOF is designed as a small evidence layer: keep the sensitive material where it belongs and store a deterministic reference that can be verified later.
What is the pilot meant to validate?
One real workflow, one responsible owner and one measurable control point. We test whether the proof record improves reconstruction, review or auditability enough to justify broader integration. The pilot is not represented as enterprise-wide deployment.
What security boundary should a buyer understand?
The pilot uses authenticated records, per-user row-level isolation, restricted production origins and a source-minimizing browser workflow. It is not yet organization-level multi-tenancy, a certification, or a substitute for the customer's own access controls and records-management obligations.
FOUNDING PILOT
Validate one control point before buying a platform.
We start with a bounded workflow in compliance, governance, legal, audit or quality. Together we define the evidence event, acceptance test and measurable outcome—then decide whether broader integration is justified.
1 workflow1 ownerClear acceptance testDocumented outcome
€2,500working one-time founding-pilot pricing hypothesis · net
- Workflow and evidence-boundary workshop
- Pilot setup and onboarding
- Verification acceptance test
- Closeout with findings and next-step decision
PRIVATE PILOT CONSOLE
Create, verify and inspect proofs
Use non-sensitive pilot material only. Source content entered for hashing or verification stays in this browser workflow and is not included in proof requests.
Access
Create proof
Verify locally
Evidence boundary
A matching fingerprint confirms byte-for-byte correspondence with the recorded hash. HUMANPROOF does not currently claim external immutable timestamping, public notarization, regulatory certification, ownership, factual truth, or guaranteed legal evidentiary status.
YOUR RECORDS
Proof ledger
Sign in to load your proofs.