CFAA's CMP : Wrapup

For the past month I've been running a series on actions provoked by Google's Adsense. Here are the relevant posts:-

• 2023-08-18: Adsense on CFAA++ • 'I need to catch up with new actions from Google'; CFAA++ means my web site and blogs
• 2023-08-25: Adsense and the GDPR • GDPR = General Data Protection Regulation
• 2023-09-01: Adsense and the CMP • CMP = Consent Management Platform
• 2023-09-08: Adsense and CFAA's CMP
• 2023-09-15: CFAA's Consent Management

In that last post, I wondered,

What happens if a visitor to my site doesn't grant consent? No ad is shown. Since I routinely use two different devices, I'll grant consent on one and withhold it on the other. That way I'll be able to monitor both sides of Google's consent management.

It turns out that wasn't a useful strategy. I automatically delete cookies when I close a browser. The consent appears to be stored in a cookie, so I routinely lose the consent cookie and have to go through the process each time I access my own site. [NB: Confirm this.] In that same post, I also wondered,

What's next? I need to improve my own privacy policy to answer the questions that Google says I'm answering. To do that, I'll summarize the current series and point to that summary.

The most important question is 'How can I change my choice of consent?'. Since Google is constantly tinkering with its software, I'll describe the procedure as it is today. After going through the consent procedure, the following image attaches to the left side of a page on my site.

That's what it looks like near the bottom of the page. To re-open the consent procedure, click on the blue text. Near the top of the page, the image collapse into the icon displayed in the upper left (a check mark on a shield). Clicking the icon expands to the image shown above. This procedure is sure to change in the future, but I'll try to keep up with it.

As for CMP on my blogs, I'll follow Google directives for them. All of the blogs are managed using Google's services. For the moment, ads aren't being displayed on this current blog or on my two other chess blogs (WCCB, C960; accessible via my Blogger.com profile). The non-chess blog is showing ads. Since ad revenue is near zero on all of the blogs taken together, I really don't care if no ads are displayed.

***

Later: On my page, World Chess Championship : Site map, under the first section, titled 'Privacy statement', I added a link to this blog post. That statement applies equally to another large portion of my domain, the pages accessed via Welcome to 'Chess for All Ages'.

One other non-trivial change is worth mentioning. The old version of the 'Site map' ended with:-

For more information on Internet and Web privacy, see www.truste.org.

That site now returns the message, 'can’t connect to the server at www.truste.org'. What happened to it? A Google search points to TrustArc (wikipedia.org), which starts,

TrustArc Inc. (formerly TRUSTe) is a privacy compliance technology company based in Walnut Creek, California. The company provides software and services to help corporations update their privacy management processes so they comply with government laws and best practices. Their privacy seal or certification of compliance can be used as a marketing tool.

Archive.org stops showing the truste.org domain at the end of 2017. Whatever the reason for the name change, with comply/compliance we're all talking the same language. When a powerful government talks, nobody walks. They run. Even Google runs.