Go straight to the content
TakedownRequest

The TakedownRequest blog: notes on notices and the replies they draw

This takedown request blog collects dated notes on what surrounds a takedown request: why a recipient refused a notice, how a counter-notice changes the timetable, what a repeat-infringer policy says, and where a notice becomes public. Each note answers one question and names the document it relies on. Nothing has been posted yet.

The notice guides deal with the document: its fields, its statements, and its delivery. This blog deals with everything around the document. A notice is one message in an exchange, and most of the questions we are asked concern the other messages.

Four subjects come up again and again, and the notes will be grouped under them.

  • Replies. What a refusal actually says, which missing element it points to, and when a corrected notice is the right answer. Under the Digital Services Act a recipient has to state its decision and the options for redress, and those statements can be read closely.
  • Counter-notices. What the other side has to declare, what the original sender is told, and how the period of 10 to 14 business days in 17 U.S.C. § 512(g) runs.
  • Policies. How individual platforms describe their treatment of repeat infringers and of senders whose notices are manifestly unfounded, quoted from their own pages.
  • Publication. Which recipients pass notices to a public archive, which fields they withhold, and what a sender can do about a notice that is already published.

A note is shorter than a guide and narrower. It takes one question, gives the answer in its opening lines, and then shows the source: the section of the statute, the article of the regulation, or the recipient’s published page, with the date we read it. Where sources disagree, or where a recipient says nothing on the point, the note says so and does not fill the gap with a guess.

There are things this blog will not carry. It reports no outcome percentages, because we publish none. It tells no client stories, since a case belongs to the person who sent it. It offers no methods for getting lawful material removed, and no ways around a refusal that was correctly reasoned.

Notes appear below with the newest first. If your question is about a live case and cannot wait for a note, the case intake page explains what to send, and the home page covers the basics of what a notice has to say.

Posted notes

What can a reader expect from the blog?

How is a note different from a notice guide?

A guide follows one recipient’s form from the first field to delivery. A note answers a single question about what surrounds a notice, such as a refusal, a counter-notice, or publication.

Are the notes drawn from client cases?

No. They are written from statutes, regulations, and recipients’ public pages. Nothing that identifies a person who sent us a case appears in a note.

Will a note tell me whether my own notice will succeed?

It cannot. A note explains a rule or a published practice. Whether a particular notice is acted on is decided by its recipient, on the facts in front of it.

How often are notes added?

There is no schedule. A note is posted when a question has a sourced answer, and it carries the date its source was read.

The blog is written by TakedownRequest for general information. It does not speak for any platform, host, search engine, or authority it mentions, and reading it creates no client relationship and no legal advice.

Send the case