* incitement to religious hatred
or any other behaviour meant to deliberately put upon a person harassment, alarm or distress.
-We do NOT endorse or encourage discrimination on the grounds of e.g. race, religion gender or sexual preference and
+We do NOT endorse or encourage discrimination on the grounds of e.g. race, religion, gender or sexual preference and
operate with a zero-tolerance policy for libel and defamation.
While we believe in the concept of freedom of thought and freedom of expression, freenode does not
Public Logging
=============
-If you're considering publishing channel logs, think it through. The freenode network is an interactive environment. Even on public channels, most users don't weigh their comments with the idea that they'll be enshrined in perpetuity. For that reason, few participants publish logs.
+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.
-If you're publishing logs on an ongoing basis, your channel topic should reflect that fact. Be sure to provide a way for users to make comments without logging, and get permission from the channel owners before you start. If you're 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.
+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.
+
+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.
+
+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.
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.
+Privacy Policy and Data Retention
+=============
+This section describes how freenode makes use of the information you provide when you use the freenode network, freenode.net and freenode.live websites (hereinafter collectively referred to as 'freenode services').
+
+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.
+
+freenode collects and uses certain information about users in order to provide services and enable certain functions.
+
+freenode may collect the following information:
+
+* Nickname/handle on the freenode network
+* E-mail address
+* IP address/hostname
+* Name and project affiliation
+
+Collecting the above data helps freenode deliver its services to you.
+
+Specifically, freenode may use data:
+
+* To improve the provided services.
+* To enable you to reset your password/recover your account.
+* To contact you in relation to group registrations and associated channel namespace management.
+* To respond to a specific enquiry made via e-mail or the support system.
+* To provide information in connection with conference registrations, sponsorship enquiries and similar relating to the freenode network and freenode #live conference.
+
+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.
+
+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.
+
+freenode policies are updated from time to time, and the latest version of policy will be published on this page.
+
+This policy was last updated on: 30 December 2017
+
+If you have any questions about freenode policies, please e-mail policy@freenode.net.
+
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).
projects / irc / freenode / web-7.0.git / blobdiff