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 publishes logs, always make sure to obtain permission from the channel owner before you start publishing logs, and ensure that there is an easy way for projects to opt-out later and to request removal of previously published logs.
+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.
freenode collects and uses certain information about users in order to provide services and enable certain functions.
freenode may collect the following information:
-<ul>
- <li>Nickname/handle on the freenode network</li>
- <li>E-mail address</li>
- <li>IP address/hostname</li>
- <li>Name and project affiliation</li>
-</ul>
+
+* 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:
-<ul>
- <li>To improve the provided services.</li>
-<li>To enable you to reset your password/recover your account.</li>
-<li>To contact you in relation to group registrations and associated channel namespace management.</li>
-<li>To respond to a specific enquiry made via e-mail or the support system.</li>
-<li>To provide information in connection with conference registrations, sponsorship enquiries and similar relating to the freenode network and freenode #live conference.</li>
- </ul>
-
+* 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 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: 23 December 2017
+This policy was last updated on: 30 December 2017
If you have any questions about freenode policies, please e-mail policy@freenode.net.
projects / irc / freenode / web-7.0.git / blobdiff