Privacy
What you can expect from us.
We hate spam. We hate spyware. You will not receive spam from us. We do not incorporate spyware into Diddlefinger. Read on for what you can expect from us.
Cookies
Diddlefinger requires you have cookies switched on for some elements of the site to work correctly. We set several cookies.
The "mapstatus" and "welc" cookies handles simple preferences - whether or not the sidebar window is open, for example.
The "biglips" cookie contains information about any markers and associated notes you have saved. This cookie is saved to your computer. If you make a marker and save personal information with it, it will be retained on your computer. It is not saved to our server. If you save markers on a public computer, other people using that computer will be able to see them and read any notes you saved.
The "PHPSESSID" cookie contains a session identifier that allows various aspects of the service to work.
We may set other cookies as the need arises.
Address Search
If you do an address search in English, we save the result on our server. The reason for this is that finding a location from an address is quite resource intensive, so we do it only once for each address, and cache the result (In detail: we store the address you searched for, the date (but NOT the time), whether the address lookup was successful and, if so, the latitude and longitude.) We do not store any information associating a particular address lookup with you.
Log-file
In addition, we record standard "logfile" information such as the data displayed or clicked on (including user interface elements, ads and links) and other website log information such as your browser type, IP address, date and time of access, referrer URL and so on.
Advertisers
We may provide advertisers only aggregated non-personal information such as the number of times one of their ads was clicked.
Circumstances in which we WOULD share information.
We do not sell, rent or otherwise share your personal information with any third parties except in the following limited circumstances: a) to satisfy any applicable law, regulation, legal process or enforceable governmental request, (b) to enforce applicable Terms of Use, including investigation of potential violations thereof, (c) to detect, prevent, or otherwise address fraud, security or technical issues, or (d) to protect against imminent harm to the rights, property or safety of Diddlefinger, its users or the public as required or permitted by law.
This privacy policy may be amended from time to time to take account of new site features.