- 1 Advertising policy
- 1.1 General Disclaimers
- 1.2 Have you found a problem with Cookipedia?
- 1.3 TL,DR;
- 1.4 Summary
- 1.5 Publishing on Cookipedia and public data
- 1.6 Private logging
- 1.7 Sharing information with third parties
- 1.8 Security of information
- 1.9 User data
- 1.10 Deletion of content
Google's use of advertising cookies enables it and its partners to serve ads to visitors to this website based on their visit to this website and/or other sites on the Internet.
Have you found a problem with Cookipedia?
Please click here and let us know, we will do everything we can to resolve it.
Cookipedia retains no user's information, has never, and never will pass any information to third parties and regularly deletes information that would enable identification of visiting users.
If you only read Cookipedia, no more information is collected than is typically collected in server logs by web sites in general.
If you contribute to Cookipedia, you are publishing every word you post publicly. If you write something, assume that it will be retained forever. This includes articles, user pages and talk pages. Some limited exceptions are described below.
Publishing on Cookipedia and public data
Simply visiting the web site does not expose your identity publicly (but see private logging below).
When you edit any page in Cookipedia, you are publishing a document. This is a public act, and you are identified publicly with that edit as its author.
When you publish a page in Cookipedia, you may be logged in or not.
If you are logged in, you will be identified by your user name. This may be your real name if you so choose, or you may choose to publish under a pseudonym, whatever user name you selected when you created your account.
If you have not logged in, you will be identified by your network IP address. This is a series of four numbers which identifies the Internet address from which you are contacting Cookipedia. Depending on your connection, this number may be traceable only to a large Internet service provider, or specifically to your school, place of business, or home. It may be possible that the origin of this IP address could be used in conjunction with any interests you express implicitly or explicitly by editing articles to identify you even by private individuals.
It may be either difficult or easy for a motivated individual to connect your network IP address with your real-life identity. Therefore if you are very concerned about privacy, you may wish to log in and publish under a pseudonym.
When using a pseudonym, your IP address will not be available to the public except in cases of abuse, including vandalism of a Cookipedia page by you or by another user with the same IP address. In all cases, your IP address will be stored on the Cookipedia server and can be seen by Cookipedia's server administrators and by users who have been granted "CheckUser" access. Your IP address, and its connection to any usernames that share it may be released under certain circumstances (see below).
If you use a company mail server from home or telecommute and use a DSL or cable Internet connection, it is likely to be very easy for your employer to identify your IP address and find all of your IP based Cookipedia contributions. Using a user name is a better way of preserving your privacy in this situation. However, remember to log out or disconnect yourself after each session using a pseudonym on a shared computer, to avoid allowing others to use your identity.
Cookipedia will set a temporary session cookie (PHPSESSID) whenever you visit the site. If you do not intend to ever log in, you may deny this cookie, but you cannot log in without it. It will be deleted when you close your browser session.
More cookies may be set when you log in, to avoid typing in your user name (or optionally password) on your next visit. These last up to 30 days. You may clear these cookies after use if you are using a public machine and don't wish to expose your username to future users of the machine. (If so, clear the browser cache as well.)
Many aspects of the Cookipedia community interactions depend on the reputation and respect that is built up through a history of valued contributions. User passwords are the only guarantee of the integrity of a user's edit history. All users are encouraged to select strong passwords and to never share them. No one shall knowingly expose the password of another user to public release either directly or indirectly.
Every time you visit a web page, you send a lot of information to the web server. Most web servers routinely maintain access logs with a portion of this information, which can be used to get an overall picture of what pages are popular, what other sites link to this one, and what web browsers people are using. It is not the intention of Cookipedia to use this information to keep track of legitimate users.
Log data may be examined by developers in the course of solving technical problems and in tracking down badly-behaved web spiders that overwhelm the site. IP addresses of users, derived either from those logs or from records in the database are frequently used to correlate usernames and network addresses of edits in investigating abuse of Cookipedia, including the suspected use of malicious "sockpuppets" (duplicate accounts), vandalism, harassment of other users, or disruption of Cookipedia.
Log data is permanently and irrecoverably deleted every few months.
Policy on release of data derived from page logs
It is the policy of Cookipedia that personally identifiable data collected in the server logs, or through records in the database via the CheckUser feature, may be released by the system administrators or users with CheckUser access, in the following situations:
- In response to a valid subpoena or other compulsory request from law enforcement
- With permission of the affected user
- To the chair of Cookipedia, his/her legal counsel, or his/her designee, when necessary for investigation of abuse complaints.
- Where the information pertains to page views generated by a spider or bot and its dissemination is necessary to illustrate or resolve technical issues.
- Where the user has been vandalising articles or persistently behaving in a disruptive way, data may be released to assist in the targeting of IP blocks, or to assist in the formulation of a complaint to relevant Internet Service Providers
- Where it is reasonably necessary to protect the rights, property or safety of Cookipedia, its users or the public.
Cookipedia policy does not permit public distribution of such information under any circumstances, except as described above.
Sharing information with third parties
Except where otherwise specified, all text added to Cookipedia is available for reuse under the terms of the GFDL.
Cookipedia will not sell or share private information, such as email addresses, with third parties, unless it is required by law to release the information.
Security of information
Cookipedia makes no guarantee against unauthorised access to any information you provide. This information may be available to anyone with access to the servers.
You may provide your e-mail address in your Preferences and enable other logged-in users to send email to you through Cookipedia. Your address will not be revealed to them unless you respond, or possibly if the email bounces. The email address may be used by Cookipedia to communicate with users on a wider scale.
If you do not provide an email address, you will not be able to reset your password if you forget it. However, you may contact one of the Cookipedia server administrators to enter a new mail address in your preferences.
You can remove your email address from your preferences at any time to prevent it being used.
Data on users, such as the times at which they edited and the number of edits they have made are publicly available via "user contributions" lists, and in aggregated forms published by other users.
Deletion of content
Removing text from Cookipedia does not permanently delete it. In normal articles, anyone can look at a previous version and see what was there. If an article is "deleted", any user with "administrator" access on Cookipedia, meaning almost anyone trusted not to abuse the deletion capability, can see what was deleted. Information can be permanently deleted by those people with access to the servers, but there is no guarantee this will happen except in response to legal action.