Does a matching collection hash prove a dataset is complete or licensed?

No. It validates the byte hashes of files listed in the assertion. It does not prove that every dataset file was listed, that licenses or consent exist, or that the content is true.

Are selected dataset files uploaded?

No. Listed file bytes are hashed in the browser. The application sends neither source files nor relative paths to the server.

Do extra selected files invalidate the C2PA result?

No. The C2PA specification allows a collection assertion to cover only selected members. Extra local files are reported as not covered, not silently treated as a standard failure.

C2PA 2.4 / COLLECTION DATA HASH / BROWSER LOCAL

Prove which dataset files still match the signed collection binding.

Supply a c2pa.hash.collection.data assertion and select its local folder. The browser verifies every listed byte digest and separates tampering, missing files and uncovered additions.

2,000: LISTED FILES
3: SHA-2 ALGORITHMS
0: FILE UPLOADS

LOCAL DATASET INTEGRITY

Assertion-to-folder audit

Files never leave this browser. A match proves listed byte hashes only, not authorship, licensing, consent, completeness or truth.

COLLECTION ASSERTION

JSON / crJSON

ASSERTION JSON0 B

Accepts a bare collection-data-hash map, an assertion wrapper, or a crJSON object containing one matching assertion.

LOCAL COLLECTION

0 FILES

Select the collection root folder or individual files.

Relative paths are used only to resolve assertion URIs in this browser.

No local files selected.

COLLECTION EVIDENCE

IDLE

Add an assertion and local files to begin.

0: MATCHED
0: MISMATCHED
0: MISSING
0: NOT COVERED

STANDARD RESULT CODE not-run

RELATIVE URI	STATE	REVIEW
No file evidence yet.

Allow detailed exports containing relative URIs and hashes.

WHAT THE RESULT MEANS

Four states, no invented score.

01
MATCH
The selected file bytes equal the hash declared for that URI.
02
MISMATCH
The file exists, but its current byte digest differs from the assertion.
03
MISSING
A URI listed by the assertion cannot be resolved in the selected collection.
04
NOT COVERED
A selected file is not listed. C2PA permits partial collection coverage, so this is reported without becoming a standard failure.

ENTERPRISE HANDOFF / FIXED SCOPE

Turn a local result into a review-ready dataset evidence package.

The Dataset Provenance Audit Sprint reviews one assertion and up to 2,000 listed entries, verifies the minimized receipt, maps unresolved evidence and delivers a bounded audit memo. Source media stays with your team.

PILOT PRICEUSD 790One collection / five business days / no legal certification REQUEST AUDIT SPRINT

STANDARD BOUNDARY

Integrity evidence is narrower than dataset governance.

Hash binding: Shows whether listed local bytes match the assertion at audit time.
Completeness: Not proven. The assertion may intentionally omit files.
Rights and consent: Not evaluated by a byte hash and require separate evidence.
Manifest signature: Not validated by this folder audit. Validate the source C2PA manifest separately in the Evidence Workspace.

Normative source: C2PA Content Credentials 2.4, Collection Data Hash validation.OPEN OFFICIAL SOURCE

Prove which dataset files still match the signed collection binding.

MATCH

MISMATCH

MISSING

NOT COVERED

Turn a local result into a review-ready dataset evidence package.

Integrity evidence is narrower than dataset governance.