TAKEDOWNLegal
Architecture
that holds.
Click any clause to cross-reference its counter-notification equivalent. Every field is annotated. Every procedure is mapped.
Boilerplate
vs. Engineered
Every gap in a standard policy is a vector for abuse. The left panel shows what most sites copy-paste. The right shows what actually holds up under a subpoena.
"My copyrighted content was used without permission."
"The copyrighted work is [TITLE], Registration No. [REG_NO], first published [DATE]. The specific infringing material is located at [EXACT_URL] and reproduces [DESCRIPTION] verbatim."
"Contact me at my email."
"[FULL_LEGAL_NAME], [PHYSICAL_ADDRESS], [CITY, STATE, ZIP], [PHONE], [EMAIL]. If acting as agent: [COMPANY_NAME] on behalf of [RIGHTS_HOLDER]."
"I believe this is infringement."
"I have a good faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law. This declaration is made under penalty of perjury."
No designated agent listed. DMCA notices sent to generic contact@.
Designated Agent: [NAME], registered with USCO DMCA Agent Directory, updated [DATE]. All notices to: dmca@[DOMAIN] with subject line: "DMCA NOTICE — [REFERENCE_ID]".
The Right to
Fight Back.
A counter-notification is the mechanism that prevents DMCA from being weaponized for censorship. Most policies implement the minimum. Takedown implements what works.
Full name, address, phone, email
Full legal name + physical address + daytime phone + email + government ID type (for verification)
URL of removed content
Original URL + content hash (SHA-256) + creation timestamp + alternative hosting proof
Standard good faith belief language
Good faith belief + specific basis (e.g., fair use, license, original authorship) + citation to applicable statute or license terms
Consent to federal court jurisdiction
Consent to jurisdiction of Federal District Court for [USER_DISTRICT] + acceptance of service from complainant's designated address
Click any specification row to analyze the defensive upgrade
Repeat Offenders
Meet the Wall.
§ 512(i) requires a policy for terminating repeat infringers. Without a documented, enforced tiered system, your safe harbor protection dissolves. This is what enforcement looks like.
→ Warning email sent
→ Account suspended temporarily
→ Account terminated
→ Account flagged in system, warning issued with § 512(i) citation, 30-day monitoring window activated
→ Content removal, 90-day account suspension, notification to upstream hosts, CDN cache purge initiated
→ Permanent account termination, IP block, legal referral memo generated, § 512(i) compliance documented for safe harbor preservation
Stop Using
Boilerplate.
A DMCA policy isn't a formality. It's a legal instrument. The difference between the one you copy-pasted and this one is the difference between safe harbor and liability.
Four steps.
Zero ambiguity.
Replace all [BRACKETED_FIELDS] with your organization's legal details. Minimum: entity name, physical address, designated agent.
Register your designated agent at dmca.copyright.gov/osp. Required for § 512(c) safe harbor. Takes 10 minutes.
Register your designated agent at dmca.copyright.gov/osp. Required for § 512(c) safe harbor. Takes 10 minutes.
Host at /dmca or /legal/dmca. Link from footer. Ensure it's publicly accessible — obscured policies don't satisfy § 512(i).
Set up dmca@yourdomain.com with auto-acknowledgement. Log all notices with timestamps. Retain records for 3 years minimum.
Set up dmca@yourdomain.com with auto-acknowledgement. Log all notices with timestamps. Retain records for 3 years minimum.
By the time a bad actor finishes reading this policy, they'll know it's not worth testing.