]> jfr.im git - irc/freenode/web-7.0.git/blob - content/pages/policies.md
2021-06-05: update people
[irc/freenode/web-7.0.git] / content / pages / policies.md
1 ---
2 Title: The Policies
3 ---
4
5 Purpose
6 ==================
7 The freenode project exists to help all communities. Its focus is peer-directed projects
8 and open innovation communities. Peer-directed projects combine open, informal participation
9 with broad licensing and wide dissemination of output.
10
11 freenode provides facilities to peer-directed project communities and the combined efforts
12 of open innovations, including those of free and open source software (FOSS). Freenode
13 utilizes IRC to service its users — but the network was created to serve groups that
14 exist outside of IRC. freenode is designed to encourage community members to improve their
15 skills in the areas of cooperative effort, interpersonal communication and project
16 coordination, and to create a real-time bridge to the outside world for our target communities.
17
18 Nickname ownership
19 ==================
20
21 Nicknames are allocated on a first-come, first-served basis, to the first person
22 who registers the name with NickServ. However, we expect users to act in good
23 faith and reserve the right to remove a nickname registration where we believe
24 that this has not been the case.
25 Nickname and account registrations expire ten weeks after they are last used.
26 For nicknames, ‘used’ means that you were using the nickname while logged in to
27 the account which owns it. For accounts, ‘used’ means that you logged in to the
28 account, regardless of the nickname you used to do so. Nicknames which are the
29 primary account name expire only when the entire account is expired.
30
31 In some cases, such as for very old accounts, we may, at our discretion, extend
32 the expiry time of a nickname or account. We will not normally do this beyond 15
33 weeks past the last use.
34
35 Some nicknames and accounts, including but not limited to some of those owned by
36 current or former network staff, do not expire at all. These accounts can be
37 identified by the ‘Hold’ flag in their NickServ info output.
38
39 Nicknames and accounts which are expired will not automatically be dropped.
40 Please contact network staff if you would like to take over an expired nickname.
41
42 Channel ownership
43 =================
44
45 Channels on freenode fall into one of two categories. Primary channels, which
46 begin with a single # character, are reserved for on-topic projects. Primary
47 channels are required to stay open. If a primary channel closes access to its
48 users or is in violation of freenode policies, then it will be closed and forwarded
49 to a topical channel. If you’d like to take over one of these primary channels, then
50 you’ll need to be associated in some way with the project in question. Topical,
51 or ‘about’ channels, begin with two # characters, and these are allocated on a
52 first-come, first-served basis to the first person who registers it with ChanServ.
53 As with nicknames, however, we reserve the right to remove or alter registrations
54 where we believe they have not been made in good faith.
55
56 Primary channels do not expire with inactivity, though they can be claimed at
57 any time by a representative of an on-topic project with the appropriate name.
58 Topical channels expire after 60 days in which no user on the access list for
59 the channel has joined it. Further information, policies and guidelines relating
60 to channel ownership can be found under [group registration](http://freenode.net/groupreg).
61
62 On-topic Use
63 ============
64
65 freenode’s primary goal is to encourage and foster the development and use of
66 free and open source software projects and other peer-directed communities
67 producing broadly licensed creative output. Any project falling under this broad
68 description is likely to be considered on-topic for the purposes of primary
69 channel naming and other project services which we may provide, but individual
70 decisions may be made at the discretion of staff.
71
72 We strongly urge you to adhere to the [channel guidelines](http://freenode.net/changuide) and [catalyst guidelines](http://freenode.net/catalysts).
73
74
75
76 Off-topic Use
77 =============
78
79 We expect all users of the network, whether affiliated with a project or not, to
80 act in good faith and in accordance with both their local laws and those
81 applicable where freenode operates. Use of freenode and its facilities is a
82 privilege, not a right, and may be withdrawn where we believe that this has not
83 been the case.
84
85 Unlawful activities and related support activities are considered off-topic, as are
86 inappropriate advertising, heavy media file trading, proprietary game software modding,
87 warez, porn and various forms of antisocial behaviour, including (but not limited to)
88 political, racial, ethnic, religious or gender-related invective.
89
90 In accordance with UK law freenode has no tolerance for any activity that could be construed
91 as:
92
93 * incitement to racial hatred
94 * incitement to religious hatred
95
96 or any other behaviour meant to deliberately put upon a person harassment, alarm or distress.
97 We do NOT endorse or encourage discrimination on the grounds of e.g. race, religion, gender or sexual preference and
98 operate with a zero-tolerance policy for libel and defamation.
99
100 While we believe in the concept of freedom of thought and freedom of expression, freenode does not
101 operate on the basis of absolute freedom of speech, and we impose limitations, e.g. on "hate speech".
102
103 We expect all members of the community to be respectful of one another and of the privacy of others,
104 and we reserve the right to terminate anyone's access to our services at our discretion.
105
106 While we encourage registered groups (projects) and channel owners to adopt our channel guidelines and catalyst guidelines, projects are free to set their own policies for their namespaces as long as such policies do not contravene network policy, and many projects choose to extend their code of conduct and similar agreements to their presence on freenode. In the event that a project makes the decision to ban a user from their channel(s), we ask that such bans be respected and note that ban evasion may result in a network ban.
107
108 Please note that the examples above are examples only and do not constitute an exhaustive list. In line with our policies, philosophies and guidelines we will review each case individually and the response and actions may differ from case to case.
109
110 Unlawful Activity
111 =============
112 freenode cannot condone or support behaviour which is clearly unlawful. While we do not have the resources
113 to closely monitor the thousands of channels on the network, volunteers are required by policy to pass on credible
114 information, provided by you as a user of the freenode project, about any unlawful activities. This is true whether you
115 are talking about your own activities or those of someone else. Please be aware that we have this responsibility.
116
117 freenode and financial transactions
118 =============
119
120 We appreciate that end users may sometimes wish to reward a project or a project
121 contributor after having had a positive support experience in a project channel
122 and it is great when this results in a donation to the project in question or
123 perhaps a micropayment to the contributor concerned or the purchase of an item
124 from the contributor's wish list.
125
126 Nevertheless, we would urge our users to carry out their own due diligence
127 before entering into financial transactions of any kind and stress that any
128 financial transactions entered into on the freenode network must be undertaken
129 entirely at the user's risk and freenode accepts no liability for any losses
130 incurred as the result of such transactions.
131
132 Public Logging
133 =============
134 If you are considering publishing channel logs, think it through. The freenode network is an interactive environment and users may not weigh their comments with the idea that they will be enshrined in perpetuity.
135
136 Nevertheless, we understand that projects might find it useful to publish channel logs so that other users may search and find answers to questions that have previously been addressed on the freenode network. Ensure that you notify users (by way of channel topic, channel entry message or similar) that the channel is being publicly logged and consider providing a way for users to make comments without logging.
137
138 If you operate a service that scrapes internal channel content or publishes logs, always make sure to obtain permission from the channel owner or freenode staff before you start publishing logs or other data, and ensure that there is an easy way for projects to opt-out later and to request removal of previously published logs or data. You must respect the opt-out requests in a timely manner.
139
140 If you are thinking of "anonymizing" your logs (removing information that identifies the specific users), be aware that it's difficult to do it well—replies and general context often provide identifying information which is hard to filter.
141
142 If you just want to publish a single conversation, be careful to get permission from each participant. Provide as much context as you can. Avoid the temptation to publish or distribute logs without permission in order to portray someone in a bad light. The reputation you save will most likely be your own.
143
144 Privacy Policy and Data Retention
145 =============
146 This section describes how freenode makes use of the information you provide when you use the freenode network, freenode.net, jobs.freenode.net and freenode.live websites (hereinafter collectively referred to as 'freenode services').
147
148 If you are asked to provide information when using freenode services, such information will not be used for any purposes other than those described in this section.
149
150 freenode collects and uses certain information about users in order to provide services and enable certain functions.
151
152 freenode may collect the following information:
153
154 * Nickname/handle on the freenode network
155 * E-mail address
156 * IP address/hostname
157 * Name and project affiliation
158
159 Collecting the above data helps freenode deliver its services to you.
160
161 Specifically, freenode may use data:
162
163 * To improve the provided services.
164 * To enable you to reset your password/recover your account.
165 * To contact you in relation to group registrations and associated channel namespace management.
166 * To respond to a specific enquiry made via e-mail or the support system.
167 * To provide information in connection with conference registrations, sponsorship enquiries and similar relating to the freenode network and freenode #live conference.
168 * To communicate with you about the status of job postings on the jobs.freenode.net website.
169
170 Please note that the freenode websites and network may contain links to other websites, and freenode has no control of websites outside of the freenode.net and freenode.live domains. If you provide information to a website or service to which freenode links, freenode shall not be responsible for its protection and privacy.
171
172 freenode retains data for the purpose of debugging and restoration for a maximum of 60 days. This means that any data freenode holds, will be purged 60 days after the date at which you last connected to the freenode network or deleted your freenode account.
173
174 freenode policies are updated from time to time, and the latest version of policy will be published on this page.
175
176 This Website (‘freenode.net,’ ‘freenode.live’), its owners freenode Limited, Company Limited by Guarantee (collectively, ‘We,’ ‘Us,’ or ‘freenode') wish to define and inform you of any and all of the instances in which your personal data and information may be saved and how it may be used by freenode, how it may be shared, and the level of protection we use to safeguard your personal information.
177
178 ## TABLE OF CONTENTS
179
180 * Personal Information we Collect
181 * Uses of Personal Information Collected by freenode
182 * Disclosure of Personal Information
183 * Data Retention
184 * CalOPPA Statement
185 * Maintaining the Security of Your Personal Information
186 * How We Transfer Personal Information Collected Internationally
187 * COPPA Disclosure
188 * How to Access and Control your Personal Information
189 * Changes to this Privacy Policy
190
191 ### PERSONAL INFORMATION WE COLLECT
192
193 #### From Clients of our Service:
194
195 * E-mail Address for the purposes of account management and protection from abuse.
196 * Internet Protocol (IP) Address for the purposes of account management and protection from abuse.
197 * Your user ID or “nick” for the purposes of account management and protection from abuse.
198 * In the case of Group Contacts, freenode may also collect project/organisational affiliation and real names in connection with the initial registration for verification and to prevent abuse.
199
200
201 #### From the Website(s) and Email
202 * Cloudflare analytics data (this data is anonymized). Cloudflare may also store a cookie. You can find the Cloudflare cookie policy [here](https://www.cloudflare.com/cookie-policy/), which also outlines how to opt out.
203 * Google reCaptcha. Google may also store a cookie. You may opt out [here](https://tools.google.com/dlpage/gaoptout).
204 * freenode #live ticket sales are managed by a third-party; TicketTailor and their privacy policy can be found [here]( https://www.tickettailor.com/gdpr).
205 * freenode #live CFP submissions are collected using [TypeForm](https://www.typeform.com/help/gdpr-compliance/) and managed via [Trello](https://trello.com/privacy)
206
207 ### USES OF PERSONAL INFORMATION COLLECTED BY US
208 * E-mail address is used to confirm account ownership, and for account management purposes such as password resets.
209 * Cloudflare analytics data is used to improve our website and delivery of our content.
210 * Google reCaptcha is used to prevent spam and abuse of the webchat service and to improve delivery of our content.
211 * Webserver logs are regularly pruned and are created by the webserver. No usernames or passwords are ever logged by the webserver.
212 * Compliance with valid legal process
213 * Group Contact affiliation and names are used for verification and abuse prevention purposes.
214 * Names, e-mail addresses, project affiliation, etc., collected in connection with freenode #live registrations and submissions are used for verification and security (venue) purposes, and to issue participants with tickets.
215
216 freenode does not collect or log private or public chat. However, users may log their own chats privately. Be careful about disclosing any personal information in a channel or private message because that information may be logged by a third party, which is beyond the control of freenode.
217
218 ### DISCLOSURE AND USE OF PERSONAL INFORMATION
219 freenode may be required to provide your personal information to law enforcement in the event of a criminal investigation, criminal prosecution, or civil subpoena. freenode will comply with legal instruments that follow proper procedure and are sufficiently narrow in their scope as to not infringe on the civil liberties of others.
220
221 ### DATA RETENTION
222 We retain all account information and data indefinitely unless a user deletes their account (/msg nickserv drop <yournick>), in which case the data is purged from our systems in accordance with our general data retention policy of thirty (30) days. We retain login activity for a period of thirty (30) days after which the data is purged from our system. We do not maintain any logs of user chat activity.
223
224 ### CalOPPA STATEMENT
225 The State of California requires us to post specific language related to our privacy policy. By default, freenode does not share your private information with any third parties aside from the disclosures already made in this privacy policy. However, if you wish to inquire into how freenode does not share our users' personal information with third parties for direct marketing purposes, you may contact: policy@freenode.net.
226
227 ### MAINTAINING THE SECURITY OF YOUR PERSONAL INFORMATION
228 Your personal information is safeguarded by freenode. You may access your personal information maintained by freenode via a services command (/msg nickserv info <yournick>). Personal information stored by freenode can also be made accessible to other third-parties on the freenode network on an opt-in basis only. All personal information maintained by freenode is encrypted and stored on a server located in the European Union.
229
230 ### HOW WE TRANSFER PERSONAL INFORMATION COLLECTED INTERNATIONALLY
231 We collect information globally and primarily store that information in the European Union. If we transfer your personal information from the European Union we will request your consent.
232
233 ### COPPA DISCLOSURE - About Children’s Online Privacy
234 The Children’s Online Privacy Protection Act (COPPA) was passed to give parents increased control over what information is collected from their children online and how such information is used. The law applies to websites and services directed to, and which knowingly collect information from, children under the age of 13. Our online services are not directed to children under the age of 13, nor is information knowingly collected from them. For additional information on COPPA protections, please see the FTC website at: https://www.consumer.ftc.gov/articles/0031-protecting-your-childs-privacy-online
235
236 Please note that freenode, while providing a service globally, is registered in the UK and complies with the age requirements as set out at: https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/applications/children/
237
238 ### HOW TO ACCESS AND CONTROL YOUR PERSONAL INFORMATION
239 You may delete your personal information at any time via a services command (/msg nickserv drop <yournick>). You may also change the email address associated with your account via a services command.
240
241 For access to information and requests for erasure, please e-mail policy@freenode.net.
242
243 ### CHANGES TO THIS PRIVACY POLICY
244
245 BY CONTINUING TO USE THIS WEBSITE AND/OR SERVICES, YOU AGREE THAT YOU CONSENT TO THIS MOST RECENT PRIVACY POLICY. FROM TIME TO TIME, FREENODE WILL MAKE CHANGES TO ITS PRIVACY POLICY AND SUCH CHANGES WILL BE COMMUNICATED VIA MOTD AND THIS WEBSITE.
246
247 freenode will not share user's personal information with third parties for direct marketing purposes.
248
249 For all civil or law enforcement requests, please contact policy@freenode.net. If you have a request that requires mailing or courier, please use the information below:
250
251 freenode Limited
252 71-75 Shelton Street
253 Covent Garden
254 London, WC2H 9JQ
255 UK
256
257 While freenode agrees to accept service of law enforcement requests based on the above method listed above, freenode does NOT waive any legal rights based on this accommodation.
258
259 Last revised July 30, 2018
260
261
262 This policy page was last updated on: 25 May 2021
263
264 If you have any questions about freenode policies, please e-mail policy@freenode.net.
265
266 In addition to these policies, you may wish to read our [Catalyst Guidelines](https://freenode.net/catalysts), [Channel Guidelines](https://freenode.net/changuide), [Philosophy](https://freenode.net/philosophy), [Group Registration Information](https://freenode.net/groupreg) and [this KB article on Conduct](https://freenode.net/kb/answer/conduct).