Privacy

This site uses cookies from Google and potentially also third parties to deliver services, to analyse traffic and to serve adverts. Your IP address and user agent are shared, together with performance and security metrics, to ensure quality of service, to generate usage statistics, to facilitate advertising, and to detect and address abuse.

CONVENTIONAL COOKIES

Cookies are text files or (more likely in the 2020s) database entires, containing small pieces of information from a website. They are stored on, and read from your computer or device.

This blog is hosted on Google's Blogger (.blogspot) platform, which is covered by Google's cookie policy, accessible via the link below...

Cookie Policy

The Administrator of this blog, as a separate entity, does not collect, or attempt to collect, any personally identifying information relating to blog visitors who make no effort to specifically provide it. This applies across all devices, including mobile phones.

ANALYTICS

As of 23 December 2021, this blog no longer uses Google Analytics to measure visitor stats, so Google Analytics cookies will no longer be used.

However, the Blogger platform still natively delivers its own general usage statistics to the Administrator. The statistics delivered do not pinpoint detailed information such as a visitor's specific location (beyond their country), visit times or page view durations, and cannot realistically be used by the Administrator to identify visitors or micro-analyse their behaviour.

ADVERTISING AND COOKIES

Additionally, this blog may serve you with advertisements through the Google Adsense programme. This involves the use of cookies.

Google's use of advertising cookies enables it and its partners to serve ads to you on this site and potentially also other sites on the Internet. By default, Google serves personalised adverts, which means that known elements of your past internet history are used to determine the relevance of the adverts you will see.

However, the enhanced privacy policies in some regions - namely Europe (including the UK) and California - have forced Google to provide a choice as to the type of ads displayed. In Europe, there's a choice between personalised ads, and non-personalised ads which are based only on the subject matter of the content being read in the moment - not previous internet use. In California, there's an option for restricted data processing, which includes non-personalised advertising along with restricted use of personal identifiers. I have set up the maximum level of privacy available for visitors from these regions - by default.

For the region of Europe, I have disabled personalised ads by default. You don't need to change any settings at your end in order to see NON-personalised ads if you're recognisably visiting from Europe or the UK.

For the region of California, I have set up Restricted Data Processing, which includes non-personalised ads by default. You don't need to change any of your settings in order to see NON-personalised ads if you're recognisably visiting from California.

For the region of Brazil - which also has enhanced privacy law - Google ads do not provide any publisher-selectable privacy options, but Google will only share ad requests with Ad Technology Providers that have been certified for LGPD with Google. A list of those providers with links to their privacy policies, is available here.

Visitors should, however, know that even with non-personalised ads and restricted data processing, from 15th January 2022 Google will begin sending bid requests to third-party bidders that participate in Google’s unified auction. Visitor identifiers will be dropped from the bid requests when the visits are recognised as coming from Europe or California. Anonymised data is exempt from the disclosure requirements under both GDPR and CCPA. Short of disabling ads altogether, there is nothing I can do as administrator to make the ads served any more respectful of privacy. I would make all ads non-personalised and more respecting of privacy, for everyone, if it were possible. But unfortunately, Google only sees fit to provide that choice where the law says it has to. Never let it be said that we don't need laws to improve Big Tech's behaviour.

OTHER COOKIES

You may encounter Twitter widgets on this blog, which display content from Twitter. In accordance with this, you'll find the relevant privacy information in Twitter's privacy policy.

AddtoAny sharing facilities may be incorporated into this site, to enable the convenient sharing of post links to other platforms. AddtoAny has a separate privacy policy, which can be found here.

BLOCKING COOKIES AND ATTAINING BETTER PRIVACY

You are not obliged to accept cookies, and you can still use this site if you choose to block them. Nearly all browsers allow the blocking/disabling of all cookies, or the blocking of third party cookies only, or a selective arrangement in which you choose which specific sites or domains you want to allow to place/read conventional cookies. It's easy to find instructions on how to block or disable cookies for specific browsers in a simple web search.

You should know that blocking cookies in your browser (rather than using on-site consent forms) is a much better, more comprehensive and more reliable way to reduce your trackability, since it also helps to block technologies such as "dark storage". There's an insight into how the technologies overlap here. I would also suggest reading the Privacy Guide on Popzazzle if you're serious about making deep changes to your general trackability, rather than the superficial changes provided by individual consent form opt-outs.

EXTERNAL CONTENT

This blog incorporates hyperlinks, both text-based and pictorial, to other websites. The Administrator of this blog accepts no responsibility for content you may find on the third-party sites you access via hyperlinks. Separate sites will also have their own privacy policies, which are a separate agreement between you and them, and are not covered in this notice.

CONTACT

The Contact Page allows visitors to message the blog administrator. The Contact form requests a name and an email address, and the message can contain any information the sender wishes to submit. Users of the Contact facility are advised never to submit any sensitive information.

If a reply to a Contact message is warranted, The administrator will use the name and email address provided, and the content of the message, for the purpose of replying. Personal information submitted will not be retained by the administrator for any longer than it is needed for its original intended purpose. The sender's IP address is integrated into the message and will be received by the administrator as part of the email.

Senders of Contact messages should be aware that most email transmission falls into the hands of large tech companies, who make money through the collection of data.

The administrator will not publish or pass on the contents of any Contact message unless one or more of these conditions applies...

  • The sender explicitly states that the message is for publication.
  • The message contains information which the administrator believes could put any party at risk.
  • The content of the message relates to an illegal act.

PRIVACY STATEMENT

The Administrator of this blog does not collect any personal information from or about visitors who do not deliberately provide personal information. If visitors do deliberately provide personal information, it is handled in accordance with GDPR - strictly confined to the exact purpose for which it is interpreted to have been provided, and only retained for as long as it takes to fulfil that purpose.

Last updated 23 December 2021.