ProvenanceGuard
← Go back

← All guides

Content Provenance for Newsrooms Publishing AI-Assisted Images

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

The short answer

Newsrooms should seal AI-assisted images at the desk, before publication, publish labelled copies where the imagery is synthetic, and keep the verification URL in the asset's record so any reader, subject or regulator query can be answered from the registry rather than from a photographer's memory. The evidence pack covers the formal requests.

Seal an image free → Recover a reposted image Pricing

A newsroom's scarcest asset is the reader's belief that it shows its working; provenance is one of the few tools that manufactures that belief on demand.

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.

What is newsroom provenance? provenance practice for a news organisation: sealing AI-assisted images at publication, keeping registry records an editor can produce, and giving readers a verification route for imagery whose origin will be questioned.

Provenance for newsrooms: the plain-English version

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.

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.

Reading the result properly

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.

A visible label does the communicating that metadata cannot. Most people who see an image will never open its properties, and most platforms will never show them a credentials panel. A label in the pixels, naming the content as AI-generated, is read by exactly the audience the disclosure rules exist for, on exactly the surface where they encounter it. ProvenanceGuard's labelled copy carries that strip as part of the image, so the disclosure travels with the pixels instead of depending on a caption that can be separated from them.

Mistakes that quietly break the record

Labels have their own failure modes, and a serious workflow plans for them. A label placed along an edge can be cropped out; a label rendered too small becomes illegible after a platform resize; a screenshot of the centre of an image may exclude it entirely. That is why the visible label is one layer among several: the survival re-checks specifically test whether the label remains detectable after simulated platform transforms, and the registry fingerprint remains as the fallback when the label is gone.

There is also a tone question. A custody strip that looks like part of the work's presentation, clearly worded and consistently used, reads as professionalism rather than apology. Teams that label every AI asset the same way, from the first post rather than after a complaint, find the label becomes part of their brand's trust signal. The creators who struggle are usually the ones who labelled inconsistently, so that an unlabelled repost looks like concealment next to their labelled originals.

When free is enough and when paid depth earns its place

ProvenanceGuard is built around those layers, and its wording is deliberately narrow. The free job inspects one JPEG or PNG, embeds a signed ProvenanceGuard assertion in XMP, produces a visibly labelled copy, registers the SHA-256 and perceptual fingerprints, and gives the asset a public verification page. The assertion is HMAC-signed and labelled accurately everywhere as ProvenanceGuard's own assertion; it is not a C2PA manifest and is never described as one.

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.

Five actions to take

  1. Make sealing a desk step with a named owner, like legal review
  2. Put the verification link where corrections and credits already live
  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 regional newsroom introducing AI-assisted explainers

It sealed 11 explainer graphics in its first month, printed verification links in the credits, and when a rival outlet questioned one graphic's origin, the desk replied with the registry record showing registration before the rival's screenshot was taken.

File the pattern, not just the outcome: a dated record, a measured match, and wording that never claimed more than the record holds. Repeated across a catalogue, that pattern is what turns provenance from a feature into a reputation.

FAQ

Should news photos that are merely AI-enhanced be sealed?

If AI processing touched the published image, a record costs little and answers the exact question readers ask. Seal the published file and declare accurately what was done; the declaration field exists for that honesty.

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 →