Note: Judgepedia will be read-only from 9pm CST on February 25-March 5 while Judgepedia is merged into Ballotpedia.
Starting on March 5, all Judgepedia content will be contained on For status updates, visit

Judgepedia:Privacy policy

From Judgepedia
Jump to: navigation, search
Judgepedia policies
Copyright policy
Image use policies
User name policies
Blocking policies
Privacy policies
Criminal behavior & scandal
Writing Guidelines

Privacy Policy

If you only read Judgepedia, no more information is collected than is typically collected in server logs by websites in general. If you contribute to Judgepedia, 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 the wiki and public cata

Simply visiting the website does not expose your identity publicly. When you edit any page on Judgepedia, you are publishing a document. This is a public act, and you are identified publicly with that edit as its author.

Identification of an author

When you make an edit on Judgepedia, you will be identified by the user name you chose when you registered. This may be your real name if you so choose, or you may choose to publish under a pseudonym.


Judgepedia will set a temporary session cookie 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 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, you may wish to clear the browser cache as well.)


Many aspects of Judepedia’s 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.

Private logging

Every time you visit a web page, you send 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 the Judgepedia projects to use this information to keep track of legitimate users. Instead, these logs are used to produce the site statistics pages; the raw log data is not made public, and is normally discarded after about two weeks.

Here's a sample of what's logged for one page view: - - [21/Oct/2003:02:03:19 +0000] "GET /wiki/draft_privacy_policy HTTP/1.1" 200 18084 "" "Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/85.7 (KHTML, like Gecko) Safari/85.5" 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 Judgepedia, including the suspected use of malicious "sockpuppets" (duplicate accounts), vandalism, harassment of other users, or disruption of Judgepedia.

Policy on release of data derived from page logs

It is the policy of Judgepedia that personally identifiable data collected in the server logs or otherwise may be released by the system administrators in the following situations:

  • In response to a valid subpoena or other compulsory request from law enforcement
  • With permission of the affected user
  • To anyone who is responsible 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 vandalizing 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 Judgepedia, its users, or the public.

Judgepedia policy does not permit public distribution of such information under any circumstances, except as described above.

Sharing information with third parties

Judgepedia will not sell or share private information, such as email addresses, with third parties, unless you agree to release this information, or it is required by law to release the information.

Security of information

Judgepedia makes no guarantee against unauthorized access to any information you provide. This information may be available to anyone with access to the servers. A partial list of those people can be found in the developers list.

Mailing lists

If you enter you email address, Judgepedia may contact you from time to time with Judgepedia-related news.

User data

Data on users, such as the times at which they edited and the number of edits they have made are publicly available via lists of users or recent changes, and in aggregated forms published by other users.

Removal of user accounts

Once created, user accounts will not be removed. It is possible for a username to be changed. Judgepedia cannot guarantee that a name will be changed on request.

Deletion of content

Removing text from Judgepedia does not permanently delete it. In normal articles, anyone can look at a previous versions. If an article is "deleted," any user with administrator access on Judgepedia can see what was deleted. Information can be permanently deleted by those people with access to the servers, and this may be done at regular intervals, or in response to a court order or settlement agreement, but there is no guarantee this will.

See also