|
| 1 | +DMCA Takedown Policy |
| 2 | +==================== |
| 3 | + |
| 4 | +These are the guidelines that Read the Docs follows when handling DMCA takedown |
| 5 | +requests and takedown counter requests. If you are a copyright holder wishing to |
| 6 | +submit a takedown request, or an author that has been notified of a takedown |
| 7 | +request, please familiarize yourself with `our process <Takedown Process_>`_. |
| 8 | +You will be asked to confirm that you have reviewed information if you submit a |
| 9 | +request or counter request. |
| 10 | + |
| 11 | +We aim to keep this entire process as transparent as possible. Our process is |
| 12 | +modeled after `GitHub's DMCA takedown process <github-dmca_>`_, which we |
| 13 | +appreciate for it's focus on transparency and fairness. All requests and counter |
| 14 | +requests will be posted to this page below, in the `Request Archive`_. These |
| 15 | +requests will be redacted to remove all identifying information, except for Read |
| 16 | +the Docs user and project names. |
| 17 | + |
| 18 | +.. _github-dmca: https://help.github.com/articles/dmca-takedown-policy/ |
| 19 | + |
| 20 | +Takedown Process |
| 21 | +---------------- |
| 22 | + |
| 23 | +Here are the steps the Read the Docs will follow in the takedown request process: |
| 24 | + |
| 25 | +Copyright holder submits a request |
| 26 | + This request, if valid, will be posted publicly on this page, `down below |
| 27 | + <Request Archive_>`_. The author affected by the takedown request will be |
| 28 | + notified with a link to the takedown request. |
| 29 | + |
| 30 | + For more information on submitting a takedown request, see: `Submitting a |
| 31 | + Request`_ |
| 32 | + |
| 33 | +Author is contacted |
| 34 | + The author of the content in question will be asked to make changes to the |
| 35 | + content specified in the takedown request. The author will have 24 hours to |
| 36 | + make these changes. The copyright holder will be notified if and when this |
| 37 | + process begins |
| 38 | + |
| 39 | +Author acknowledges changes have been made |
| 40 | + The author must notify Read the Docs that changes have been made within 24 |
| 41 | + hours of receiving a takedown request. If the author does not respond to this |
| 42 | + request, the default action will be to disable the Read the Docs project and |
| 43 | + remove any hosted versions |
| 44 | + |
| 45 | +Copyright holder review |
| 46 | + If the author has made changes, the copyright holder will be notified of |
| 47 | + these changes. If the changes are sufficient, no further action is required, |
| 48 | + though copyright holders are welcome to submit a formal retraction. If the |
| 49 | + changes are not sufficient, the author's changes can be rejected. If the |
| 50 | + takedown request requires alteration, a new request must be submitted. If |
| 51 | + Read the Docs does not receive a review response from the copyright holder |
| 52 | + within 2 weeks, the default action at this step is to assume the takedown |
| 53 | + request has been retracted. |
| 54 | + |
| 55 | +Content may be disabled |
| 56 | + If the author does not respond to a request for changes, or if the copyright |
| 57 | + holder has rejected the author's changes during the review process, the |
| 58 | + documentation project in question will be disabled. |
| 59 | + |
| 60 | +Author submits a counter request |
| 61 | + If the author believes their content was disabled as a result of a mistake, |
| 62 | + a counter request may be submitted. It would be advised that authors seek |
| 63 | + legal council before continuing. If the submitted counter request is |
| 64 | + sufficiently detailed, this counter will also be added to `this page |
| 65 | + <Request Archive_>`_. The copyright holder will be notified, with a link to |
| 66 | + this counter request. |
| 67 | + |
| 68 | + For more information on submitting a counter request, see: `Submitting a |
| 69 | + Counter`_ |
| 70 | + |
| 71 | +Copyright holder may file legal action |
| 72 | + At this point, if the copyright holder wishes to keep the offending content |
| 73 | + disabled, the copyright holder must file for legal action ordering the |
| 74 | + author refrain from infringing activities on Read the Docs. The copyright |
| 75 | + holder will have 2 weeks to supply Read the Docs with a copy of a valid legal |
| 76 | + complaint against the author. The default action here, if the copyright |
| 77 | + holder does not respond to this request, is to re-enable the author's |
| 78 | + project. |
| 79 | + |
| 80 | +Submitting a Request |
| 81 | +~~~~~~~~~~~~~~~~~~~~ |
| 82 | + |
| 83 | +Your request must: |
| 84 | + |
| 85 | +Acknowledge this process |
| 86 | + You must first acknowledge you are familiar with our DMCA takedown request |
| 87 | + process. If you do not acknowledge that you are familiar with our process, |
| 88 | + you will be instructed to review this information. |
| 89 | + |
| 90 | +Identify the infringing content |
| 91 | + You should list URLs to each piece of infringing content. If you allege that |
| 92 | + the entire project is infringing on copyrights you hold, please specify the |
| 93 | + entire project as infringing. |
| 94 | + |
| 95 | +Identify infringement resolution |
| 96 | + You will need to specify what a user must do in order to avoid having the |
| 97 | + rest of their content disabled. Be as specific as possible with this. |
| 98 | + Specify if this means adding attribution, identify specific files or content |
| 99 | + that should be removed, or if you allege the entire project is infringing, |
| 100 | + your should be specific as to why it is infringing. |
| 101 | + |
| 102 | +Include your contact information |
| 103 | + Include your name, email, physical address, and phone number. |
| 104 | + |
| 105 | +Include your signature |
| 106 | + This can be a physical or electronic signature. |
| 107 | + |
| 108 | +* Requests can be submitted to:* [email protected] |
| 109 | + |
| 110 | +Submitting a Counter |
| 111 | +~~~~~~~~~~~~~~~~~~~~ |
| 112 | + |
| 113 | +Your counter request must: |
| 114 | + |
| 115 | +Acknowledge this process |
| 116 | + You must first acknowledge you are familiar with our DMCA takedown request |
| 117 | + process. If you do not acknowledge that you are familiar with our process, |
| 118 | + you will be instructed to review this information. |
| 119 | + |
| 120 | +Identify the infringing content that was removed |
| 121 | + Specify URLs in the original takedown request that you wish to challenge. |
| 122 | + |
| 123 | +Include your contact information |
| 124 | + Include your name, email, physical address, and phone number. |
| 125 | + |
| 126 | +Include your signature |
| 127 | + This can be a physical or electronic signature. |
| 128 | + |
| 129 | +* Requests can be submitted to:* [email protected] |
| 130 | + |
| 131 | +Request Archive |
| 132 | +--------------- |
| 133 | + |
| 134 | +Currently, Read the Docs has not recieved any takedown requests. |
| 135 | + |
| 136 | +.. |
| 137 | + * :download:`Some Company, Inc <archive/2017-01-22.txt>` |
| 138 | +
|
0 commit comments