Over the past few weeks, I’ve been getting a lot of requests for information about Twitter and their DMCA procedure. Most of these issues stem from avatar or backgrounds that are infringing, not the tweets themselves. It seems the exponential increase in Twitter members has brought with it a wide range of individuals who are decorating their profiles with the works of artists that didn’t grant permission.
However, I’ve been hard pressed to advise these people as Twitter’s DMCA process is an unadulterated mess. There are three separate policies, one of which appears to be out of date, two separate email addresses and three different means of filing a notice.
It appears that these issues may have caught Twitter as off guard as the other trappings of their popularity and their response to the issue appears scattered, creating headaches for anyone who has had their content misused on the site.
On that page, the very first section deals with filing a copyright notice. It says the following:
Copyright complaints concern the unauthorized distribution or republishing of copyrighted material. In order for something to be removed for copyright purposes, we must receive a DMCA take down notice by mail or fax. Email is not sufficient. If we receive a physical take down notice, Twitter will respond within 24 hours of receiving this document.
This is incorrect on many different fronts, many of which I talked about when dealing with Google, which has a similar policy for many of its sites, but what makes it worse is that clicking the link to read the full policy, and supposedly get the fax number/mailing address, takes you to a broken link.
However, if you go back to the forum home page, you see another topic entitled “Filing a copyright complaint or DMCA take down notice“. That page, contains a much different copyright policy, one with an email (copyright@), the fax number, the mailing address and even an invitation to file via the support form.
This is a complete turnaround from the first policy, which said that “Email is not sufficient” and requires a “physical” takedown notice.
However, all of this is altered yet again when you look up their DMCA contact information on the U.S. Copyright Office Web site. It uses a different email address (support@) and was filed two months before either of the above policies went live.
In short, Twitter currently has three different DMCA filing procedures.
- A procedure that requires a fax or an email
- One that may be sent to copyright@ or filed via a support form
- A final one that should be sent to support@
This isn’t worrisome in that Twitter is not attempting to follow the DMCA or isn’t taking the law seriously, it clearly is, but there is clearly an organization issue here and that’s leading to confusion.
The filing with the Copyright Office is two months before the two posts on the Twitter help site, both of which went up in December, thus, I believe that the second one is the real policy and, recently, I’ve been encouraging people to file DMCA notices using Twitter’s support function. This seems to work.
Many of the notices filed by members get rejected because they are incomplete. It is important to remember you do still have to file a full DMCA notice so use my stock letter and paste it into the form, failure to do so (or use another complete notice) will result in it getting kicked back.
If that fails, send a message to both the support@ and copyright@ accounts. Though either should work (notices people sent to the support@ account have been acted on) it is better to be safe than sorry so long as there is conflicting information.
Between those two things, the matter should be handled. I haven’t had anyone be told they need to send a fax or snail mail letter, as the first policy indicates, but it is important to be aware Twitter has indicated as such, just in case that changes.
The Strange Caveat
There is another element to this that is worth mentioning. When you’re dealing with images on the Twitter, service, which does seem to make up the bulk of the copyright complaints, the images are not actually hosted on Twitter’s servers, but they use Amazon S3. You can tell this clearly when you look at an image by itself, as with my profile pic.
However, in this case, it doesn’t seem that such a takedown is quite in order. Not only would it likely be slower to work with Amazon, especially since Twitter promises to respond within 24 hours (at least in one of their policies), but Twitter would be in a position to take other actions, such as banning accounts of repeat infringers.
This may well be an exception to the image/file hosting problem.
Twitter clearly has some work to do in this area. Though it is understandable that the Copyright Office papers would be different from the site, especially considering if often takes months for updated filings to appear on the site, but the dueling policies on the Twitter site itself, especially with the broken link and direct contradictions between them, is not excusable.
My hope is that Twitter will clarify their policy, take the second one as their actual DMCA procedure and be done with it. The second one makes the most sense and offers the best solution to the problem.
Failing that, I at least hope they can unify their language and their policy, so that everyone knows what the procedure is. After all, the only thing worse than having a bad policy is having three different ones.