ProvenanceGuard
← Go back

← All guides

Your AI Image Was Reposted Without Credit: What Provenance Can Prove

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

The short answer

Match the repost to your record first, through recovery if it was stripped or check-a-copy if you hold a candidate file. Then document the match, distance, exhibit, registration date, and only then contact the reposter, leading with the record rather than the accusation. Provenance proves the copy descends from your registered original and when you registered it; what happens next is negotiation or process built on that fact.

Seal an image free → Recover a reposted image Pricing

A calm message carrying a dated registry record outperforms an angry thread, because it moves the conversation from opinion to paperwork.

Recovery exists for the copy that comes back to you with nothing attached: no metadata, a new filename, dimensions changed by two platform hops. The Recovery Registry lookup fingerprints the uploaded copy perceptually, using aHash, dHash and pHash together, and searches the registry for a record within the stated threshold: a combined distance of at most 36 differing bits out of 192 compared, or 12 out of 64 for older records that carry only the legacy average hash. A match returns the original exhibit, its creator and disclosure declarations, and its registration time.

What is uncredited repost? a copy of your image published by someone else without attribution, typically stripped of metadata and caption, whose connection to your original must be established before any credit or takedown conversation can begin.

What goes wrong without a plan for reposted without credit

The honesty of the method is in its stated limits. This is fingerprint-only soft binding: ProvenanceGuard embeds no invisible watermark, so recovery can only find images that were registered before they travelled, and only while their pixels stay within threshold of the original. Heavy cropping, collage, or aggressive filtering can push a copy beyond matching, and the lookup then says so rather than forcing a nearest guess. A tool that always found something would be manufacturing provenance, which is the opposite of the point.

The registry model also disciplines what a match means. A fingerprint match says this image is the registered image or a close descendant of it; it does not say the person showing it to you owns it, and it does not say the disclosure attached to it was correct. Those judgements stay human. What the registry removes is the argument about identity and timing: which file, registered when, carrying which declaration. Most real disputes shrink considerably once those three facts stop being contestable.

What the inspection, seal and registry each contribute

The registry is the part that survives distribution. At sealing, the asset's SHA-256, its sealed copy's SHA-256, and its perceptual fingerprints are stored against a public exhibit ID. Anyone with that ID, or with the file's hash, can open the public verification page or query the verification API and confirm that this exact file, or a near copy of it, was registered, when, and with what declared creator and disclosure. Verification pages are public by design: a record only a vendor can check would not settle disputes.

Two kinds of fingerprint do two kinds of work. The SHA-256 is exact: change one byte and it changes completely, which makes it perfect for proving a copy is bit-for-bit the registered file and useless for recognising a resized repost. The perceptual fingerprints, computed from the pixels rather than the bytes, are approximate on purpose: they stay close when a copy is resized, re-encoded or lightly edited, and drift as edits accumulate. A good registry stores both and is honest about which kind of match it is reporting.

The honest limits

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.

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.

Decisions to make before you publish

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.

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. Match and screenshot the repost before contacting anyone
  2. Lead with the exhibit and date, not with blame
  3. File the exhibit's verification URL beside the asset wherever your team keeps campaign or client records
  4. Run check-a-copy on the version you actually published, and note which checks held: hash, signature, fingerprint
  5. Export an evidence pack while the context is fresh if the asset is regulated, client-facing or likely to be questioned

A worked example: A creator finding her AI illustration on a larger tutorial channel

The channel's version matched her record at a combined distance of 24 bits; her message quoted the exhibit and date, and credit plus a link to her verification page were added to the video description within the day.

What the case really shows is timing. Every artefact used, the registry entry, the fingerprint match, the pack, existed because someone spent a few minutes at publication. The same team, equally honest, starting from memory a month later would have had a much harder week.

FAQ

What if the reposter also sealed the image later?

Then both records exist and dates decide the shape of the conversation: the earlier registration is the earlier fact. Registries reward being first, which is a system working as designed rather than a loophole.

What does the free tier actually do?

The complete job on an asset: byte-level inspection, a signed assertion embedded as XMP, a visibly labelled copy, SHA-256 and perceptual fingerprints registered, and a public verification page. Paid plans add survival re-checks, evidence packs and bulk verification.

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.

Seal an image free →