Copyright Enforcement and the DMCA

What Platforms Need to Manage

DMCA is more than a takedown process

Section 512 of the Digital Millennium Copyright Act was built to do two things at once: give rights holders a working mechanism to get infringing content removed from online services, and give qualifying online service providers (OSPs) limitations on copyright liability when specific conditions are met. Safe harbor is conditional, not automatic — an OSP earns it by meeting a defined set of statutory obligations, not simply by hosting user content in good faith. 

For platforms, that means DMCA compliance sits at the intersection of two different jobs: responding to individual notices, and maintaining the underlying processes — policies, records, designated contacts — that keep the safe harbor available in the first place. This page walks through both: how the safe harbors and the notice-and-takedown process actually work, what the courts have said about repeat infringers, and why enforcing all of this consistently becomes an operational challenge once a platform is handling it at scale.

How Section 512 safe harbors work

The Copyright Office describes four safe-harbor categories, each covering a different kind of OSP activity: 

  • Transitory digital network communications — merely transmitting or routing material at a user's direction. ‍
  • System caching — temporary storage that speeds up network performance. ‍
  • Information stored at the direction of users — hosting, the category most platforms rely on. ‍
  • Information location tools — search engines, directories, and other linking services. 

The requirements vary by activity, but three obligations run across all four: the OSP must not have actual or "red flag" knowledge of infringing material it fails to act on, it must not receive a financial benefit directly tied to infringing activity it has the right and ability to control, and — for the hosting and linking categories specifically — it must adopt and reasonably implement a policy for terminating repeat infringers, and must not interfere with qualifying standard technical measures used to identify or protect copyrighted works. 

None of this requires an OSP to proactively monitor its own systems for infringement. Section 512 explicitly does not impose a general affirmative duty to search for infringing content — the obligations are responsive, triggered by notices and by what the provider actually knows or is plainly on notice of.

What a valid DMCA notice requires

A takedown notice only starts the clock if it substantially meets the statutory requirements. In substance, it must include: 

  • a signature (physical or electronic) of the copyright owner or an authorized agent 
  • identification of the copyrighted work claimed to be infringed 
  • identification of the material claimed to be infringing, and its location 
  • contact information for the complaining party 
  • a statement of good-faith belief that the use is unauthorized 
  • a statement, under penalty of perjury, that the notice is accurate and the sender is authorized to act 

A notice that substantially fails these elements does not count as "actual notice" for safe-harbor purposes. Once a compliant notice is received, the OSP must act expeditiously to remove or disable access to the material — but the statute does not fix a specific number of hours. That is a meaningful difference from the TAKE IT DOWN Act's 48-hour requirement, and worth stating plainly so the two frameworks aren't read as interchangeable.

From notice to restoration: the full workflow

Removal is not the end of the process. The uploader is generally notified of the takedown and may respond with a counter-notice contesting it. If a valid counter-notice is filed, the material can be restored after a defined waiting period — not less than 10, and not more than 14, business days — unless the rights holder notifies the OSP that it has filed a lawsuit seeking a court order to keep the material down.

At what stage and what happens 

01

Notice received

Validate that the notice meets the statutory elements

02

Material identified

Remove or disable access expeditiously

03

User notified

Uploader is informed of the removal

04

Counter-notice (optional)

User may formally contest the takedow

05

10–14 business days

Material may be restored unless legal action follows

Each of these stages produces a record that, in principle, needs to stay connected to the asset and to the parties involved — a requirement that becomes harder to meet the more notices a platform processes.

Repeat infringers, knowledge, and what the courts have said

The repeat-infringer requirement is one of the most litigated corners of Section 512, and the case law gives it more concrete shape than the statute alone. 

BMG Rights Management v. Cox Communications (4th Cir., 2018) is the clearest illustration of what "reasonably implemented" means in practice. Cox had a written repeat-infringer policy, but the court found it was not meaningfully enforced — Cox routinely reactivated terminated accounts and, internally, treated infringement notices dismissively. The court held that a policy which exists only on paper does not satisfy Section 512(i); it has to be applied in a consistent, meaningful way. Cox lost its safe-harbor defense as a result. 

More recently, Cox Communications v. Sony Music Entertainment reached the U.S. Supreme Court, which issued a unanimous decision on March 25, 2026. The case addressed a related but distinct question: not whether Cox had a valid repeat-infringer policy, but how far an internet service provider's liability for its subscribers' infringement extends even without safe-harbor protection. The Court held that a service provider is only contributorily liable for user infringement if it induced that infringement or offered a service "tailored to infringement" — plain knowledge of ongoing infringement is not, on its own, enough. 

The two rulings work together rather than against each other. BMG v. Cox confirms that the repeat-infringer policy required for safe harbor eligibility has to be real, not nominal. Cox v. Sony narrows what happens on the other side of that question — how exposed a provider is if it doesn't have safe harbor at all. Read together, they reinforce a simple point for platforms: the repeat-infringer requirement remains a genuine, independently enforced condition of Section 512, even as the surrounding liability landscape shifts.

The designated agent requirement

For the hosting and linking safe harbors, an OSP must designate an agent to receive infringement notices, publish that agent's contact information on its own site, and register and keep that information current with the Copyright Office's online directory. A designation that lapses — through an address change, a platform sale, or simple inattention — can put safe-harbor eligibility at risk even if every other requirement is otherwise met. It's a small administrative detail with outsized consequences, and one that's easy to overlook once initial registration is done.

Why DMCA enforcement becomes an identity and evidence problem at scale

The Copyright Office's own Section 512 Study found that the system today handles an enormous volume of notices — into the millions — against a framework designed over two decades ago for a much smaller internet. At that volume, the practical difficulty stops being about any single notice and becomes about connecting notices to each other over time. 

The same copyrighted work can reappear across a platform in modified form — cropped, re-encoded, re-uploaded under a different account. Notices arrive faster than any team can manually cross-reference them against prior enforcement history. Counter-notices need context from earlier decisions to be evaluated consistently. And determining whether a given account is a "repeat" infringer — the exact question BMG v. Cox turned on — requires visibility into what happened before, not just what's happening now. 

Handling this well requires: reliable identification of an asset independent of the specific file that carries it, a record of prior enforcement decisions tied to that asset, evidence that survives the file being copied or modified, and a way to recognize an asset when it reappears without starting the investigation over from zero. Put together, DMCA enforcement at scale is less an inbox-management problem and more an identity, evidence, and continuity problem.

How SASHA supports DMCA enforcement at scale

SASHA doesn't run the legal process the DMCA requires — it supports the technical continuity underneath it. 

Persistent content identity. Because SASHA maintains a persistent identity for known content, organizations can reconnect a later occurrence — a re-upload, a modified copy — with an asset that was already identified, instead of treating every appearance as an unrelated, first-time event. In practice, a matched signature resolves to an exact ID in the SASHA registry, which is what carries that identity and its history forward. 

Survivability across modification. SASHA's signature is built on robust invisible watermarking designed to remain identifiable through common transformations that routinely break simple file-hash matching, including cropping, re-encoding, resizing and screenshotting. The watermark provides a durable content-level ID that allows SASHA to recognize previously identified content and reconnect it with its persistent identity and associated history. 

Evidence continuity. By preserving the relationship between a piece of content, the reports made against it, and prior decisions, SASHA helps teams reconstruct enforcement history when a notice, a counter-notice, or a later dispute requires it. 

Cross-system traceability. Where copyright workflows span multiple tools and teams — legal, trust and safety, engineering — content identity and its history can stay connected rather than being lost at the handoff between systems. 

Account-level traceability. SASHA can associate protected content with the account used to share it and with whom it was shared. When the same signed content is subsequently matched within a supported workflow, that attribution can provide additional context alongside previous reports and enforcement history — the kind of documented pattern the repeat-infringer determination in BMG v. Cox turned on (see Section 5). This can help platforms identify patterns relevant to repeat-infringer processes without SASHA itself determining whether a user is legally a repeat infringer. 

The legal boundary is explicit. SASHA does not determine whether a use is infringing, does not replace fair-use analysis, does not certify that a notice is legally valid, and does not determine or guarantee eligibility for a Section 512 safe harbor. It provides technical continuity that supports the processes an organization already runs to manage copyright enforcement at scale — nothing more, nothing less.

What SASHA does not decide

To be explicit about the limits: SASHA does not and cannot automatically determine — 

  • whether a claimant actually owns the copyright in question 
  • whether a specific use qualifies as fair use under the four statutory factors in 17 U.S.C. § 107 
  • whether a given notice is legally valid in every circumstance 
  • whether a user is, as a legal matter, an infringer 
  • whether a provider qualifies for a Section 512 safe harbor 
  • what "appropriate circumstances" for termination means, or whether termination is warranted in a given case — SASHA surfaces the pattern; the termination decision remains the platform's 

These are legal judgments that require human review, often legal counsel, and — in contested cases — a court. SASHA's role is technical enforcement infrastructure: the identity, evidence, and continuity layer underneath those judgments, not a substitute for them. 

Continue exploring

Overview
What the TAKE IT DOWN Act Means for Organizations

Official Sources

SASHA shield

Build defensible takedown infrastructure

The TAKE IT DOWN Act is one signal in a much broader shift. Organizations increasingly need systems that can act fast, preserve evidence, and prevent the same content from resurfacing again and again.

Book meeting