ProvenanceGuard
← Go back

← All guides

HMAC-Signed Assertions Explained: A Signature You Can Verify

By the Ingenious AI team · Published: November 14, 2026 · Reviewed: November 14, 2026 · 8 min read

The short answer

ProvenanceGuard's assertion, asset hash, declared creator and disclosure, registration time, is signed with HMAC-SHA256 under the product signing key, and verification recomputes the signature over the payload as found. Match means the assertion is byte-identical to what was issued; mismatch means something in it changed. It authenticates the statement's integrity and issuer, not the truth of what a creator declared.

Seal an image free → Recover a reposted image Pricing

A signature moves a statement from 'someone wrote this in a file' to 'this service issued exactly this statement', and knowing the difference is most of digital evidence.

Sealing is the moment a record is created. ProvenanceGuard takes the creator and disclosure the uploader declares, the SHA-256 of the original bytes, and the registration time, and signs that assertion with HMAC-SHA256 under the product signing key. The signed assertion is embedded into the file as XMP, producing the sealed copy. Because the signature covers the assertion's contents, altering the creator, the disclosure or the hash inside the file afterwards invalidates the signature, and the verification page shows that plainly.

What is an HMAC signature? a keyed hash, here HMAC-SHA256, computed over a statement's exact contents with a secret signing key, so that anyone with verification access can confirm the statement is unaltered and was issued by the key holder.

The problem behind HMAC-signed assertions

Alongside the sealed copy, sealing produces a visibly labelled copy: the same image with a parchment custody strip in the pixels naming it as AI-generated content whose provenance is registered with ProvenanceGuard. The distinction matters. Embedded assertions are machine-readable and fragile in transport; a visible label is human-readable and survives anything that keeps the strip in frame, including a screenshot. Publishing the labelled copy where the audience actually sees the image, and keeping the sealed copy as the record, uses each layer for what it is good at.

What sealing does not do is just as clearly bounded. It does not certify that a disclosure statement is legally sufficient, it does not turn the assertion into a C2PA manifest, and it does not store the uploaded original: the registry keeps the sealed and labelled copies and the record, so verification and downloads keep working, while the original bytes are not retained. The seal is evidence of a declaration made at a time, about a specific file, and that precision is what makes it useful later.

How ProvenanceGuard handles it

For libraries rather than single files, bulk verification is a paid API feature: submit up to a hundred SHA-256 hashes in one call and get back, per hash, whether it is registered, its exhibit ID, its public verification URL and its registration time. That shape suits the questions teams actually ask at scale: whether everything in a delivered campaign folder was sealed, whether a partner's asset library overlaps the registry, or whether a month of published images all carry records. Single lookups stay free and public through the verification page and the single-hash API.

Checking a copy is the mirror image of sealing one. On an asset's verification page, uploading a candidate copy runs the same byte inspection on it and compares it against the record: its SHA-256 against the original and sealed hashes, whether a ProvenanceGuard assertion is present and its signature valid, and the perceptual distance between the copy and the registered fingerprint, with a match at a Hamming distance of ten or under on the average hash, or an exact hash match. The result states which of those held and which did not, separately, instead of collapsing them into one vague verdict.

What survives distribution, and what does not

Used inside those limits, the record is strong. Used outside them, by claiming a seal proves authorship in law, or that a simulation proves a platform's behaviour, or that a registry match proves ownership, the same record becomes a liability, because the first competent challenge will find the overclaim. The teams that get the most from provenance tooling are the ones whose public language is as precise as the tool's own: sealed, registered, verifiable, with the dates and hashes to show it.

The limits deserve the same prominence as the features. ProvenanceGuard does not detect deepfakes, does not judge whether an image is harmful, and does not verify that a creator's declared disclosure is true; it records declarations, binds them to fingerprints, and makes them checkable. Its signed assertion is its own XMP-embedded, HMAC-signed statement, explicitly not a C2PA manifest and not a certification by any standards body. Survival re-checks are local simulations of documented platform transforms, not actual uploads, and they are labelled that way in every result.

A routine that survives busy weeks

The practical problem is distribution. An image is rarely published once, in one place, in its original form. It is uploaded to platforms that resize and re-encode it, forwarded by partners, saved and reposted by audiences, and archived by people who strip whatever context surrounded it. Each step is normal and usually innocent, yet together they separate the image from anything that said how it was made. Planning for that separation, rather than hoping it will not happen, is the whole discipline this guide is about.

No single layer does this job alone, and honest tooling says so. Embedded metadata can be stripped. A visible label can be cropped. A fingerprint can drift if an image is edited heavily. A registry entry proves registration, not authorship in a legal sense. Used together, though, the layers cover each other's failures: when the metadata is gone the fingerprint can still find the registry record, and when a copy is too altered to match, the labelled version and the evidence pack still tell the story.

Five actions to take

  1. Verify the signature before quoting an assertion's contents
  2. Quote assertions as issued statements, with their issuer named
  3. Run check-a-copy on the version you actually published, and note which checks held: hash, signature, fingerprint
  4. Export an evidence pack while the context is fresh if the asset is regulated, client-facing or likely to be questioned
  5. Re-check one published asset through the Recovery lookup so you know the stripped-copy path works before you need it

A worked example: A partner challenging an assertion's wording in a delivered file

Recomputing the signature showed the assertion intact and exactly as issued at registration; the disagreement turned out to be about a caption written later by hand, and the distinction ended the argument in one meeting.

The lesson generalises beyond this case. Records made at publication time are cheap, calm and complete; records reconstructed under pressure are expensive, partial and contested. Everything in this guide is in service of moving work from the second category into the first.

FAQ

Could someone forge an assertion without the key?

Forging requires producing a signature that verifies under a key they do not hold, which is the problem HMAC-SHA256 is designed to make impractical. What they can do is remove the assertion entirely, which verification reports as absence, not as a valid record.

What do Pro and Team cost?

Pro is $29 a month and Team is $79 a month, as shown on the pricing page. Paid depth means per-platform survival re-checks, evidence pack export with EU, California and New York wording, and the bulk hash-verification API.

Are my uploaded originals stored?

No. The registry keeps the sealed and labelled copies derived at sealing time and the registry record, so downloads and verification keep working, while the uploaded original bytes are not retained.

Can anyone verify a record, or only the owner?

Anyone. Verification pages are public by design, the single-hash lookup is a public API, and an exhibit ID or a file hash is enough. A record only its owner could check would not settle a dispute with a stranger.

Seal an image free →