A repeat infringer policy is the least-understood lever in the DMCA and your best weapon against someone who steals on a schedule. Under 17 U.S.C. § 512(i), a service provider keeps its safe-harbor immunity only if it has adopted and reasonably implemented a policy for terminating subscribers who are repeat infringers, and only if its users have been told the policy exists. No policy, no shield. That one sentence is the legal foundation of every strike system you have ever met.
The rule changes your objective. One takedown removes a file. A documented series removes the operator. What follows covers what the statute actually requires, how platforms turn it into strike counts, and the record-keeping discipline that converts a handful of your notices into a terminated account, even against a thief who keeps re-registering.
What the DMCA actually requires of platforms
The termination duty lives in 17 U.S.C. § 512(i)(1)(A). To qualify for any safe harbor, user storage, caching, linking, even acting as a plain conduit, a provider must satisfy three conditions: it has adopted a policy providing for termination of repeat infringers in appropriate circumstances, it reasonably implements that policy, and it informs subscribers and account holders that the policy exists. Miss one, and the shield is gone. The provider faces copyright claims like any ordinary defendant.
What the statute never does is define "repeat infringer" or "appropriate circumstances." Courts have treated the silence as deliberate flexibility: a platform may set its own threshold, two strikes, three, a pattern over a year, so long as the threshold is real and enforced. That flexibility is why the counts differ from platform to platform and why the statute never says "three." The other conditions attached to the shield are covered in how safe harbor works.
How strike systems turn the rule into software
A strike system is the repeat-infringer policy expressed as software. Every notice you file that gets granted becomes a mark on an account; when the marks cross the platform's threshold, the system fires and the channel, shop, or hosting account closes. YouTube is the famous example: three copyright strikes and the channel is terminated, though a strike can age out after a waiting period if the holder completes the platform's copyright education. Marketplaces close shops over accumulated IP complaints. Hosts suspend servers whose owners will not stop uploading infringing files. Every one of those numbers is a policy choice, not a statutory command.
One distinction matters on platforms with automated matching: fingerprint claims, such as Content ID matches, are not strikes. A fingerprint claim may reassign revenue or block a video; a strike comes from a formal complaint. If termination is the goal, your takedown notice is the instrument that leaves the mark, and what a DMCA strike is is worth reading before you file. Platforms also differ on whether a single notice covering several works counts once or per work, so check before batching when the count is the point.
The case that made platforms take termination seriously
Service providers used to treat the termination duty as paperwork. BMG v. Cox Communications ended that. Cox, a major ISP, had a written repeat-infringer policy on paper. In practice, its abuse staff could reset strike counts, and known repeat infringers kept their service. The Fourth Circuit held in 2016 that a policy enforced this loosely is not "reasonably implemented" at all, so Cox stood exposed to the copyright claims with no safe harbor behind it. The full story of BMG v. Cox is a short, instructive read.
Two lessons follow. For platforms: inconsistent enforcement is worse than a strict rule, because it forfeits the shield the rule was supposed to earn. For you: a platform that keeps granting your notices against the same account while doing nothing about the account is carrying risk its lawyers understand. You rarely need to raise your voice. A documented pattern report that names the termination policy lands on desks where people know exactly what that case decided.
Building the record that ends an account
The discipline is simple, and most victims skip it: treat every infringement as evidence, not just damage.
- File every infringement, every time. Each granted notice is a mark on the record. Skipping the small reposts because the big one hurts more keeps the count low.
- File correctly. A defective notice can be rejected without earning a strike, and the requirements are strict, how to file a DMCA takedown notice walks through them, and accuracy matters more when termination is the goal.
- Log everything in one place: case numbers, confirmation emails, URLs, account names, dates, screenshots. Timestamped evidence of when your work existed and when theirs appeared closes the credibility gap.
- Refile on every repost. The same work re-uploaded is a new infringement, and it earns a new mark.
Platforms do not terminate because you are angry. They terminate because a count crossed a line. You cannot control their threshold; you fully control whether the count is complete. A complainant who can produce eleven clean notices with eleven case IDs is treated differently from one who filed three and lost the confirmation emails. The pattern is the argument.
Reporting the pattern once the strikes stack up
When your file shows a series, one account, or several accounts you can tie to a single operator, stop reporting URLs one at a time and report the pattern. Route it to the platform's copyright team or legal contact rather than the general abuse form, and be explicit: this user is a repeat infringer under your termination policy, and here is the record, account names, filing dates, case IDs, the repost cycle.
Ask for account-level review by name. "Remove this URL" feeds a takedown queue. "Review this account for termination under your repeat-infringer policy" starts a different process, one with counsel attached. If the platform stalls, move upstream: the host behind the site, the CDN, the registrar. Those providers act under their own abuse terms rather than the DMCA, and a documented serial-infringer file is exactly what their abuse desks act on.
What happens when the thief files a counter-notice
Serial infringers who know the system file counter-notices, because a counter-notice can strip a strike. Under 17 U.S.C. § 512(g), once the platform receives one, it must restore the material within 10 to 14 business days unless you file a court action seeking an order against the user. The mechanics and deadlines are laid out in what happens after a counter-notice.
The counter-notice is not free for them. It is a statement under penalty of perjury that the material came down by mistake or misidentification, and a knowingly false one carries liability under § 512(f). From an operator already filed on five times, that signed statement is evidence you keep. The real decision is strategic: let the file return and keep building the record, or file the court action that preserves the strike and escalates. Both are legitimate; when a court order beats a takedown covers the trade-off.
Whack-a-mole: when the operator re-registers
Now the failure mode everyone knows. Termination works, and the operator opens a new account the same afternoon, new handle, new channel, sometimes a new domain, same content. Strike counts do not follow identities on their own.
Evidence does. Same files, same listings, same payment link, same contact details, that is what connects identities, and your case file is where it lives. Continuous monitoring catches reposts when they arrive rather than weeks later, and each documented cycle, account, takedown, re-registration, makes the next escalation easier to justify.
Past a certain size, two doors open. A § 512(h) subpoena can compel a platform to identify the account holder behind the pattern; courts have limited its use against providers acting purely as conduits, but it works where the target actually stores the content, and how 512(h) subpoenas work is its own article. The second door is suing the operator directly for damages or an injunction. Neither case gets built from one takedown. Both get built from the record you kept.
If you host user content: your half of the bargain
The duty cuts both ways. If you run a site with user uploads, the termination policy is not optional; it is the price of the shield. Adopt it in writing, publish it in your terms so subscribers are informed, define what repeat infringer means at your service, apply it consistently, and keep records of terminations. Inconsistent application is precisely what sank Cox. A repeat-infringer policy template plus the full safe-harbor requirements turn this into a weekend task rather than a legal project.
Where the rule's reach ends
The DMCA is US law, and the termination duty travels only as far as the statute does. In the European Union, the DSA's notice-and-action machinery governs most illegal content, but intellectual-property enforcement largely runs through pre-existing law and platform terms, how the EU's notice-and-action system works is separate reading. Canada uses notice-and-notice: providers forward your notice and do nothing more, no takedown duty and no termination duty, though Canada's notice-and-notice regime does preserve a paper trail that helps later in court. Many global platforms apply strike-style policies everywhere anyway, because one enforcement system is cheaper than two. But the statutory lever, your immunity depends on terminating this user, exists only where the DMCA does. Elsewhere, your leverage is the platform's own terms: a persuasion problem rather than a compliance one.
Frequently asked questions
How many strikes does it take to terminate an account?
However many the platform's policy says. The DMCA requires a termination policy but sets no number, so a three-strike video platform, a two-strike marketplace, and a host that suspends on a single warning for certain material are all lawful implementations. The threshold must exist and be enforced; its size is the platform's call. Check the terms of service or ask the platform's copyright contact.
Do strikes follow a repeat infringer to a new account?
Not automatically. Strike systems attach to accounts, not people, which is why re-registration is the standard evasion move. Platforms can and do link accounts when evidence connects them, identical files, shared payment details, matching device or fingerprint signals, and your documented repost record is what supplies that connection. File against the new account and cite the old case IDs.
Can a counter-notice erase a repeat infringer's strikes?
Platform policy decides whether a strike clears, but the statute requires the platform to restore the content within 10 to 14 business days after a counter-notice unless you file a court action. Do nothing, and the material returns with the count possibly reset. Keep the counter-notice itself either way, it is a sworn statement a serial infringer files at their own risk under § 512(f).
Do I have to sue anyone to get a repeat infringer terminated?
Usually not. Most terminations result from accumulated notices alone; that is the system working as designed. Litigation becomes relevant when a counter-notice forces the choice, when a § 512(h) subpoena is needed to unmask an anonymous operator, or when you want damages on top of removal. The typical repeat case ends at the strike count, not in a courtroom.
Does the repeat infringer rule apply outside the United States?
Not as a legal requirement. The DMCA binds US service providers, and safe harbor is a US defense. Elsewhere, enforcement runs on other systems, the EU's notice-and-action framework, Canada's notice-and-notice, local copyright law. Most major platforms enforce similar termination policies worldwide anyway, because running one system is simpler, so the practical answer is often yes.
What to do today
If a repeat uploader is hitting you right now, say so when you file. Recurring cases get pattern documentation built in from the first notice, the kind that later becomes the termination letter.
- File the current takedown, correctly, a defective notice earns no strike. If you want it handled for you, start here.
- Log the case ID, URL, account name, and date in one file.
- File every repost. The count only builds if every mark lands.
- When the strikes stack up, send the pattern letter requesting termination review.
- If the operator re-registers, connect the accounts in your file and weigh a § 512(h) subpoena or a court filing.
The repeat-infringer rule is the one part of the DMCA where patience is structurally rewarded. File every one, keep every number, and let the count do the terminating.