What § 512(f) means for your DMCA takedown program

This is not legal advice. Run your DMCA takedown program with your own counsel. That said, most brand-protection programs operate without a clear understanding of 17 U.S.C. § 512(f), and the case law has evolved more than people realise. Here’s what to actually know before you file your next batch of notices.

The statute, in two sentences

17 U.S.C. § 512(f) provides that anyone who knowingly materially misrepresents that material is infringing, or that material was removed by mistake, shall be liable for any damages, including costs and attorneys’ fees, incurred by the alleged infringer or by the service provider. In practice this means: if you file a DMCA notice and you knew (or should have known after good-faith review) that the target wasn’t infringing, the seller you took down can sue you for damages.

Lenz v. Universal: the “dancing baby” case

The 2015 Ninth Circuit decision in Lenz v. Universal Music is the most important § 512(f) case for brand-protection programs. Stephanie Lenz uploaded a 29-second video of her toddler dancing to a Prince song. Universal sent a takedown. Lenz sent a counter-notice. The Ninth Circuit held that copyright holders must consider fair use before sending a DMCA notice, and that failing to do so can be a material misrepresentation under § 512(f).

For brand-protection programs, the takeaway is the “before sending a DMCA notice” clause. The fair-use consideration has to happen pre-filing, not as a post-hoc rationalisation. Documentation matters: a record showing your reviewer thought about whether the use was nominative, descriptive, or otherwise non-infringing is the difference between “good-faith review” and “rubber-stamped automation.”

What “knowingly material misrepresentation” means in 2026

Two threads of case law have hardened the standard:

• Online Policy Group v. Diebold (2004) and Rossi v. MPAA (2004) established that subjective good faith is enough: you don’t need to be objectively right about infringement, you need to actually believe you are.
• Lenz v. Universal (2015) tightened the standard: subjective good faith requires actual fair-use consideration on the record. A blanket policy of “file takedown on any keyword match” doesn’t qualify.
• Cabell v. Zimmerman (2010) and Tuteur v. Crosley-Corcoran (2013) clarified that § 512(f) damages include attorneys’ fees even when actual damages are minimal, making the suit cost-effective for the alleged infringer’s side.

The review gate (and why we built it)

Brand Protector’s review gate exists because the case law is clear: the record of how you decided to file matters, and it has to show good-faith review by a person.

Nothing is filed until you review the evidence and sign off on the exact listing. Two gates:

• Human review. A human operator sees the full evidence pack and explicitly confirms the detection, which writes the “considered the question” record to the audit log. Anti-rubber-stamp: the reviewer can’t click through fast. The page makes you scroll past the evidence sequentially.
• Signed attestation with explicit identifier confirmation. Before the takedown leaves the platform, an authorized signer signs the declaration for the channel in one deliberate signing act, on a surface that names the exact asset identifier (ASIN, item ID, domain) in the signing statement: sworn under penalty of perjury where the platform transmits the notice, a review-and-sign-off where the filing happens on the marketplace’s own complaint form. The declaration for the complaint is completed there at the moment of filing. The signing statement forces eyes on the exact identifier that ships in the notice: one deliberate signing act, one signed declaration, and a record of which kind was made.

Practical operations checklist

• Pre-filing fair-use / nominative-use review must be on the record per filing. A blanket policy isn’t enough.
• Treat your authorized-reseller and trusted-domain lists as load-bearing. A takedown that hits an authorized reseller is the canonical bad-faith filing the case law contemplates.
• Keep an audit trail of every filing: who, when, what evidence, what threshold scored it. Brand Protector emits one audit row per filing decision; if you’re running on a spreadsheet, log the same fields.
• When a marketplace rejects a notice, that’s a signal to audit your detection threshold. Repeat rejections from the same source are a § 512(f) red flag.
• Have counsel review your notice template at least annually. The cited case law evolves. Brand Protector ships per-platform templates pre-reviewed for English / UK jurisdiction; we re-verify quarterly.

None of the above replaces having IP counsel on retainer. But if you’re running brand protection without understanding why the review gate exists, this piece is the starter. We’ll publish the EU equivalent (the Digital Services Act’s parallel liability framework) in the next post in this series.