tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) 
4) #include "head.wmi" TITLE="Legal FAQ for Tor Relay Operators"
5) 
6) <div class="main-column">
7) 
8) <!-- PUT CONTENT AFTER THIS TAG -->
9) 

10) <h2>The Legal FAQ for Tor Relay Operators.</h2>

11) <hr>

12) 

13) <p>FAQ written by the Electronic Frontier Foundation (<a
14) href="https://www.eff.org">EFF</a>). Last updated August 24, 2011.</p>
15) <p>NOTE: This FAQ is for informational purposes only and does not
16) constitute legal advice. Our aim is to provide a general description of
17) the legal issues surrounding Tor in the United States. Different factual
18) situations and different legal jurisdictions will result in different
19) answers to a number of questions. Therefore, please do not act on this
20) information alone; if you have any specific legal problems, issues, or
21) questions, seek a complete review of your situation with a lawyer
22) licensed to practice in your jurisdiction.</p>
23) <p>Also, if you received this document from anywhere besides the EFF web
24) site or <a
25) href="<page eff/tor-legal-faq>">https://www.torproject.org/eff/tor-legal-faq.html</a>,
26) it may be out of date. Follow the link to get the latest version.</p>
27) <p>Got a DMCA notice? Check out our <a

28) href="<page eff/tor-dmca-response>">sample response

29) letter!</a></p>
30) <h2>General Information</h2>
31) <p><b>Has anyone ever been sued or prosecuted for running Tor?</b></p>
32) 
33) <p><b>No</b>, we aren’t aware of anyone being sued or prosecuted in the
34) United States for running a Tor relay.  Further, we believe that running
35) a Tor relay &#8212; including an exit relay that allows people to
36) anonymously send and receive traffic &#8212; is lawful under U.S.
37) law.</p>
38) <p><b>Should I use Tor or encourage the use of Tor for illegal
39) purposes?</b></p>
40) <p><b>No.</b> Tor has been developed to be a tool for free expression,
41) privacy, and human rights. It is not a tool designed or intended to be
42) used to break the law, either by Tor users or Tor relay operators.</p>
43) <p><b>Can EFF promise that I won't get in trouble for running a Tor
44) relay?</b></p>
45) <p><b>No.</b> All new technologies create legal uncertainties, and Tor
46) is no exception. Presently, no court has ever considered any case
47) involving the Tor technology, and we therefore cannot guarantee that you
48) will never face any legal liability as a result of running a Tor relay.
49) However, EFF believes so strongly that those running Tor relays
50) shouldn't be liable for traffic that passes through the relay that we're
51) running our own middle relay. </p>
52) 
53) <p><b>Will EFF represent me if I get in trouble for running a Tor
54) relay?</b></p>
55) <p><b>Maybe.</b> While EFF cannot promise legal representation for all
56) Tor relay operators, it will assist relay operators in assessing the
57) situation and will try to locate qualified legal counsel when necessary.
58) Inquiries to EFF for the purpose of securing legal representation or
59) referrals should be directed to our intake coordinator (<a
60) href="mailto:info@eff.org">info@eff.org</a> or US +1 (415) 436-9333).
61) Such inquiries will be kept confidential subject to the limits of the
62) attorney/client privilege. Note that although EFF cannot practice law
63) outside of the United States, it will still try to assist non-U.S. relay
64) operators in finding local representation.</p>
65) <p><b>Should I contact the Tor developers when I have legal questions
66) about Tor or to inform them if I suspect Tor is being used for illegal
67) purposes?</b></p>
68) <p><b>No.</b> Tor's developers are available to answer technical
69) questions, but they are not lawyers and cannot give legal advice. Nor do
70) they have any ability to prevent illegal activity that may occur through
71) Tor relays. Furthermore, your communications with Tor's developers are

72) not protected by any legal privilege, so law enforcement or civil
73) litigants could subpoena and obtain any information you give to
74) them.</p>

75) <p>You can contact <a href="mailto:info@eff.org">info@eff.org</a> if you
76) face a specific legal issue. We will try to assist you, but given EFF's
77) small size, we cannot guarantee that we can help everyone.  </p>
78) 
79) <p><b>Do Tor's core developers make any promises about the
80) trustworthiness or reliability of Tor relays that are listed in their
81) directory?</b></p>
82) <p><b>No.</b> Although the developers attempt to verify that Tor relays
83) listed in the directory maintained by the core developers are stable and
84) have adequate bandwidth, neither they nor EFF can guarantee the personal
85) trustworthiness or reliability of the individuals who run those relays.
86) Tor's core developers further reserve the right to refuse a Tor relay
87) operator's request to be listed in their directory or to remove any
88) relay from their directory for any reason.</p>
89) <h2>Exit Relays</h2>
90) <p>Exit relays raise special concerns because the traffic that exits
91) from them can be traced back to the relay's IP address. While we believe
92) that running an exit is legal, it is statistically likely that an exit
93) relay will at some point be used for illegal purposes, which may attract
94) the attention of private litigants or law enforcement. An exit relay may
95) forward traffic that is considered unlawful, and that traffic may be
96) attributed to the operator of a relay. If you are not willing to deal
97) with that risk, a bridge or middle relay may be a better fit for you.
98) These relays do not directly forward traffic to the Internet and so
99) can't be easily mistaken for the origin of allegedly unlawful
100) content.</p>
101) <p>The Tor Project's blog has some excellent <a
102) href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">recommendations</a>
103) for running an exit with as little risk as possible. We suggest that you
104) review their advice before setting up an exit relay.</p>
105) <p><b>Should I run an exit relay from my home?</b></p>
106) 
107) <p><b>No.</b> If law enforcement becomes interested in traffic from your
108) exit relay, it's possible that officers will seize your computer. For
109) that reason, it's best not to run your exit relay in your home or using
110) your home Internet connection. </p>
111) <p>Instead, consider running your exit relay in a <a
112) href="https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs">commercial
113) facility</a> that is supportive of Tor. Have a separate IP address for
114) your exit relay, and don't route your own traffic through it. </p>
115) <p>Of course, you should avoid keeping any sensitive or personal
116) information on the computer hosting your exit relay, and you never
117) should use that machine for any illegal purpose.</p>
118) <p><b>Should I tell my ISP that I'm running an exit relay?</b></p>
119) <p><b>Yes.</b> Make sure you have a Tor-friendly ISP that knows you're
120) running an exit relay and supports you in that goal. This will help
121) ensure that your Internet access isn't cut off due to abuse complaints.
122) The Tor community maintains a <a
123) href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/GoodBadISPs">list</a>
124) of ISPs that are particularly Tor-savvy, as well as ones that
125) aren't.</p>
126) 
127) <p><b>Is it a good idea to let others know that I'm running an exit
128) relay?</b></p>
129) <p><b>Yes.</b> Be as transparent as possible about the fact that you're
130) running an exit relay. If your exit traffic draws the attention of the
131) government or disgruntled private party, you want them to figure out
132) quickly and easily that you are part of the Tor network and not
133) responsible for the content. This could mean the difference between
134) having your computer seized by law enforcement and being left alone.</p>
135) <p>The Tor Project <a
136) href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">suggests</a>
137) the following ways to let others know that you're running an exit
138) relay:</p>
139) <ul>
140) <li>Set up a reverse DNS name for the IP address that makes clear that
141) the computer is an exit relay.</li>
142) <li>Set up a notice like <a
143) href="https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/contrib/tor-exit-notice.html">this</a>
144) to explain that you're running an exit relay that's part of the Tor
145) network.</li>
146) 
147) <li>If possible, get an <a href="https://www.arin.net">ARIN</a>
148) registration for your exit relay that displays contact information for
149) you, not your ISP. This way, you'll receive any abuse complaints and can
150) respond to them directly. Otherwise, try to ensure that your ISP
151) forwards abuse complaints that it receives to you.</li>
152) </ul>
153) <p><b>Should I snoop on the plaintext traffic that exits through my Tor
154) relay?</b></p>
155) <p><b>No.</b> You may be technically capable of modifying the Tor source
156) code or installing additional software to monitor or log plaintext that
157) exits your relay. However, Tor relay operators in the United States can
158) possibly create civil and even criminal liability for themselves under
159) state or federal wiretap laws if they monitor, log, or disclose Tor
160) users' communications, while non-U.S. operators may be subject to
161) similar laws. Do not examine the contents of anyone's communications
162) without first talking to a lawyer.</p>
163) <p><b>If I receive a subpoena or other information request from law
164) enforcement or anyone else related to my Tor relay, what should I
165) do?</b></p>
166) <p><b>Educate them about Tor.</b> In most instances, properly configured
167) Tor relays will have no useful data for inquiring parties, and you
168) should feel free to educate them on this point. To the extent you do
169) maintain logs, however, you should not disclose them to any third party
170) without first consulting a lawyer. In the United States, such a
171) disclosure may violate the Electronic Communications Privacy Act, and
172) relay operators outside of the United States may be subject to similar
173) data protection laws.</p>

174) 
175) <p>You may receive legal inquiries where you are prohibited by law from

176) telling anyone about the request. We believe that, at least in the
177) United States, such gag orders do not prevent you from talking to a
178) lawyer, including calling a lawyer to find representation. Inquiries to
179) EFF for the purpose of securing legal representation should be directed
180) to our intake coordinator (info at eff.org or US +1 (415) 436-9333).
181) Such inquiries will be kept confidential subject to the limits of the
182) attorney/client privilege.</p>
183) <p>For more information about responding to abuse complaints and other
184) inquiries, check out the <a
185) href="<page docs/faq-abuse>">Tor Abuse
186) FAQ</a> and the collection of <a
187) href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTemplates">abuse
188) response templates</a> on the Tor Project’s website.</p>
189) <p><b>My ISP, university, etc. just sent me a DMCA notice. What should I
190) do?</b></p>
191) <p>EFF has written a <a

192) href="<page eff/tor-dmca-response>">short template</a> to help

193) you write a response to your ISP, university, etc., to let them know
194) about the details of the Digital Millennium Copyright Act’s safe harbor,
195) and how Tor fits in. Note that template only refers to U.S.
196) jurisdictions, and is intended only to address copyright complaints that
197) are based on a relay of allegedly infringing material through the Tor
198) node. </p>
199) 
200) <p>If you like, you should consider submitting a copy of your notice to
201) <a href="https://www.chillingeffects.org">Chilling Effects</a>. This

202) will help us recognize trends and issues that the lawyers might want to
203) focus on. Chilling Effects encourages submissions from people outside
204) the United States too.</p>

205) <p>EFF believes that Tor relays are protected from copyright liability
206) under the DMCA, although no court has yet addressed the issue in the
207) context of Tor itself. If you are uncomfortable with this uncertainty,
208) you may consider using a <a
209) href="<page docs/faq>#ExitPolicies">reduced
210) exit policy</a> (such as the default policy suggested by the Tor
211) Project) to try to minimize traffic types that are often targeted in
212) copyright complaints. </p>
213) <p>If you are a Tor relay operator willing to stand up and help set a
214) clear legal precedent establishing that merely running a relay does not
215) create copyright liability for either operators or their bandwidth
216) providers, EFF is interested in hearing from you. Read more <a
217) href="https://lists.torproject.org/pipermail/tor-talk/2005-October/016301.html">here</a>
218) about being EFF's test case.</p>