ProvenanceGuard
← Go back

← All guides

Provenance for Brands: Protecting AI Product Images Across Campaigns

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

The short answer

A brand should seal campaign imagery once, centrally, before any market or partner touches it. From that one record flow the labelled copies partners publish, the survival checks per platform, and the evidence packs regional compliance asks for. One registration per asset, made early, is what stops five markets from creating five incompatible stories about the same image.

Seal an image free → Recover a reposted image Pricing

Campaigns fragment by design, across markets, agencies and formats; the record is the one artefact that has to stay whole.

Provenance works when it is a step in the publishing workflow rather than a rescue operation afterwards. The working pattern is short: inspect the final export, seal it, download the sealed and labelled copies, publish the labelled copy, and file the verification URL with the asset's record wherever the team already keeps campaign or client information. Five minutes per asset at publication is the entire cost; reconstructing a record weeks later, from an unsealed original that may no longer exist, is the expensive alternative.

What is brand asset provenance? a brand's practice of sealing its AI campaign imagery at creation, registering fingerprints centrally, and giving every market and partner the same verification record for the same asset.

Why provenance for brands matters

Roles matter more than tools at team scale. One named person owns sealing for a campaign, the registry exhibit IDs are recorded next to the deliverables rather than in a personal downloads folder, and clients or partners receive the verification link as part of handover, not on request after a dispute. Paid plans exist for the depth around that routine: survival re-checks before publication, evidence packs when a jurisdiction's wording is needed, and bulk verification when the library, not the single image, is the unit of work. Pro is $29 a month and Team is $79 a month; the free tier does the complete sealing job on an asset without either.

The pattern the simulations reveal is consistent and worth internalising. Embedded metadata, including the signed assertion and any C2PA manifest, does not survive the transforms. The visible label generally does, as long as it stays in frame and legible at the reduced size. The perceptual fingerprint still matches the registry record after the transform, within the match threshold, and the registry lookup therefore survives even when everything inside the file is gone. Distribution-proof provenance is the registry plus the label; the embedded assertion is the record of origin.

How the record is built

Running the check before a campaign, rather than after a takedown or a complaint, turns those findings into decisions. If the label fails at a platform's width, the artwork changes. If a format conversion in the pipeline strips everything before publication, the seal is applied after that conversion instead of before it. The simulations are cheap and repeatable, so they belong in the pre-publish routine for any asset that matters, not in the post-mortem.

Survival re-checks, a Pro feature, answer the question publishing actually raises: after this platform does what it does to uploads, what is left of my marking? The check runs local simulations of documented platform transforms on the sealed and labelled copies: resize to the platform's maximum width, JPEG re-encode at its quality setting, and metadata stripped. The result is reported per platform for Instagram, TikTok, YouTube thumbnails, X and LinkedIn, and every row is labelled as a simulation, because that is what it is, not an actual upload.

Where it meets the real world

An evidence pack is the record, packaged for a reader who was not there. For a sealed asset it contains the exhibit ID and verification URL, the original and sealed SHA-256 hashes, the perceptual fingerprint, the file's format and dimensions, the tool identification and version, the registration timestamp, the creator and disclosure as declared, the inspection results for the original bytes, and disclosure wording by jurisdiction for the EU, California and New York. Exporting the pack is a Pro and Team feature, because it is the point where a working record becomes a compliance artefact.

The pack's value is mostly about timing and completeness under pressure. A brand safety question, a platform appeal, a client audit or a regulator's letter all arrive with deadlines, and all of them ask the same underlying questions: which file, made how, declared as what, published when. A team that exports the pack and sends it the same day looks, and is, organised. A team assembling screenshots and recollections does not, however innocent its actual process was. Evidence does not create innocence, but it is how innocence is demonstrated.

Putting it into practice

Provenance is the record of where a piece of content came from and what has happened to it since: who or what created it, when it was registered, and which copies descend from the original. For an AI-generated image that record matters because the file itself is easy to copy, rename, crop and re-upload, and none of those actions leaves a reliable trace inside a filename. A provenance record kept outside the file, in a registry keyed to the file's fingerprints, survives exactly the handling that erases the signals embedded in the file.

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.

Five actions to take

  1. Seal centrally at master stage, before localisation begins
  2. Give partners verification URLs in the brand asset pack, not on request
  3. Export an evidence pack while the context is fresh if the asset is regulated, client-facing or likely to be questioned
  4. Re-check one published asset through the Recovery lookup so you know the stripped-copy path works before you need it
  5. Seal the final export of the asset, with the creator and disclosure declared in your own accurate words

A worked example: A consumer brand running one AI campaign in 4 markets

Central sealing produced 28 records before launch; local teams published labelled copies, and a disputed repost in one market was matched to the master record in minutes, with the registration predating the campaign's public launch.

Notice what made the difference: not a better argument, but a record created before it was needed, carrying dates and hashes a stranger could check. That is the whole pattern this guide recommends, applied at the scale of one team and one deadline.

FAQ

Do local edits need their own records?

A materially edited local version is a new asset: record it as a lineage step or seal it as its own exhibit, so each published version maps to a record that actually matches its pixels.

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.

Is ProvenanceGuard's assertion a C2PA manifest?

No. It is ProvenanceGuard's own signed assertion, embedded as XMP and HMAC-signed, and labelled that way everywhere. The inspection detects genuine C2PA markers when a file carries them, but the two records are never conflated.

Seal an image free →