What is in a Chain of Proof certificate, and why platforms care
A Chain of Proof certificate turns a watermark detection into a document enforcement can act on. Here is what is inside it and why each element matters to a reviewer.
Detecting your watermark in a stolen image answers the question “is this mine?” for you. A Chain of Proof certificate answers it for someone else, the reviewer at a host or marketplace who has to decide whether to act. It packages a detection into a dated, verifiable document built to satisfy the people who process takedowns. Here is what goes into it, and why each part earns its place.
The detected watermark and your store identifier
The core of the certificate is the recovered mark and the unique identifier tied to your store. This is what converts the document from a claim into a demonstration. It does not say “I believe this is mine,” it records that the image carries the specific mark associated with your shop. That is the difference between an assertion and evidence, which is the whole battle in the burden of proof.
Image hashes
A hash is a short fingerprint calculated from the image data. Two identical files produce the same hash, and any change produces a different one. Including hashes lets a reviewer confirm that the image described in the certificate is the same file they are looking at, and it makes the document tamper-evident: the record is tied to a specific image, not a swappable description.
Detection date and confidence
The certificate records when the detection was made and how confident the match is. The date establishes a timeline that is harder to dispute than a social post. The confidence level is an honest signal of strength, which reads as credible rather than absolute, the kind of measured claim a reviewer trusts.
Full image details
Resolution, format, and file size are recorded alongside the detection. These technical specifics make the document concrete and checkable. They describe exactly which image was examined, leaving less room for a reviewer to wonder whether the certificate really matches the copy in front of them.
A verification QR code
The certificate includes a QR code that links to a matching copy of the document, so a host or platform can independently confirm it is genuine rather than taking a PDF at face value. Independent verifiability is one of the things that separates evidence that gets actioned from evidence that gets queued, as covered in what makes evidence admissible for a takedown.
Why platforms care about the format
Step back and the design makes sense. A reviewer wants evidence that identifies the work, demonstrates ownership, is verifiable, and is tamper-evident and dated. The certificate is built to tick every one of those, and to map onto what a DMCA notice or a marketplace IP form actually asks for. It gives the reviewer a reason to act and removes the reasons to hesitate. How to use it inside a notice is covered in the DMCA takedown playbook for Shopify owners.
It only exists if the image was protected first
The one catch is timing. A certificate can only be generated for an image that carried a watermark before it was stolen, because the proof is read out of the mark embedded in the copy. There is no way to add it after the fact.
That is why protection and proof are two ends of the same tool. Tilkie embeds the invisible watermark in your Shopify images now, so that later, when you find a copy, the detection becomes a Chain of Proof certificate you can hand straight to the platform that can remove it.