DMCA evidence — what creators actually need to attach

The DMCA notice template

Standard DMCA notice under 17 U.S.C. § 512(c)(3). Components:

1. Identification of the copyrighted work allegedly infringed.
2. Identification of the allegedly infringing material (URL).
3. Contact information for the complainant.
4. Good-faith belief statement that use is unauthorized.
5. Accuracy statement under penalty of perjury.
6. Physical or electronic signature.

The template is the easy part. The evidentiary attachment is what determines processing speed and outcome.

What to attach (the strong version)

1. Proof of ownership of the original work. A receipt URL for the original timestamped at the moment of creation/publication. The receipt's timestamp predates the infringing copy, signed and externally anchored — this is the strongest possible proof of priority. Without this, ownership tends to come down to “trust my account dashboard,” which platforms accept but more slowly.
2. The infringing URL and a sealed screenshot of it. Don't just link to the infringing page; seal a screenshot of the page so the evidence survives the infringer deleting their post in response to your notice (which they often do, then claim “there was nothing infringing there” in their counter-notice). The sealed screenshot + receipt URL preserves the evidence cryptographically.
3. If using the Snitch Tracker watermark: the variant ID extracted from the leaked copy. The extraction output identifies which subscriber's copy was leaked. Including this in the DMCA notice lets the registrar see you have technical attribution evidence, not just an ownership claim.
4. A short paragraph explaining the receipt URL. Most DMCA agents are not cryptographers. A two-sentence explanation — “the receipt at the URL is a cryptographic timestamp signed by receipts.you and anchored to the Bitcoin blockchain; drop my original file on the verify page to confirm match” — closes the gap. The agent can verify in fifteen seconds.

What to skip

• EXIF dates as proof of creation. Easily edited (see our post). DMCA agents who know forensics will dismiss EXIF claims; agents who don't will accept them but weight them low. Either way, EXIF isn't worth the paragraph it takes to cite.
• Lengthy emotional appeal about how the leak hurt. Not relevant to DMCA review. The agent is checking technical compliance with § 512(c)(3) and the evidentiary basis. Keep the notice professional and the attachment factual.
• Excessive screenshots without context. Two well-chosen screenshots (the original sealed at creation, the leaked copy sealed at discovery) beats ten poorly-curated ones. DMCA agents triage by reviewability.
• Claims about identity of the infringer. Identifying the infringer is not the registrar's problem — they take down the material; identifying the person behind the account is a separate civil action. Including identity claims in the DMCA notice doesn't help and sometimes triggers a more cautious review.

The receipt URL in the notice text

Sample boilerplate for the “evidence of infringement and ownership” section of the DMCA notice:

Proof of my prior creation of the work: receipts.you/r/<original-receipt-id> (cryptographic timestamp signed and anchored to the Bitcoin blockchain at the date shown; the original file's SHA-256 is verifiable by dropping the file on receipts.you/verify).

Proof of the infringing material's current state: receipts.you/r/<infringing-receipt-id> (sealed screenshot of the infringing URL at <date>; preserves evidence even if the infringing party subsequently deletes their post).

Variant-ID attribution (if applicable): the leaked copy carries an extractable watermark identifying it as variant <N>, which corresponds to my distribution to subscriber <identifier>. Extraction is reproducible via the open-source Snitch Tracker at receipts.you/track.

Why this gets honored faster

Three reasons:

1. The provenance is verifiable in fifteen seconds. The DMCA agent doesn't have to take your word; they drop the file on /verify and get a binary answer. Faster than reviewing screenshots-of-account-dashboards.
2. Counter-notice cost is higher. The infringing party who files a § 512(g) counter-notice has to confront cryptographic provenance, not just “your word against theirs.” The threshold to credibly contest is meaningfully higher.
3. The watermark variant ID is technical attribution. Most leak-attribution claims in standard DMCAs are circumstantial. A cryptographically extractable watermark variant is direct attribution evidence — significantly stronger.

Counter-notice handling

If the infringer files a counter-notice (§ 512(g)), the material is restored in 10-14 days unless you initiate litigation. The receipt provenance helps here too: if the counter-notice claims “I created this independently,” your earlier-timestamped receipt is direct evidence of priority. The infringer would have to claim either (a) their independently-created version coincidentally matches your watermarked variant (cryptographically implausible) or (b) the timestamp is wrong (defeated by the OpenTimestamps anchor).

Most counter-notices die at this point because the practical cost of litigating against signed timestamp evidence exceeds the value of the leaked material to the infringer. The material stays down; the cycle ends.

For platform-side DMCA recipients

If you're a platform receiving DMCAs, the inverse advice applies: notices that arrive with receipts.you-style cryptographic provenance are higher-trust and warrant faster processing. The verification cost is low (one drop on /verify); the trust gain is high. Many platforms' T&S teams have started recognizing sealed-evidence DMCAs as a higher-priority intake category for exactly this reason.

For the broader creator workflow (per-subscriber watermarking, attribution, evidence preservation), see /for/creators. For the comparison with Privly/Ovarra/BranditScan bundled SaaS approaches, see vs. Privly / Ovarra.