Basically, the General Data Protection Regulation (GDPR) is a good thing: taking data collectors on their promises, give users a bit of their autonomy on data back, recollect a sense of privacy. But, like so often, the baby has been thrown out with the bath water: many reports about GDPR are misleading, and not a single one misses these €20M penalty (or the 4% of total turnover) which just adds fear and sensation mongering to the discussion. Even the text generators offered by helpful persons are missing the point, because the texts they’re spitting out tend to be longish and try to cover any data-driven detail. The chance that I miss a detail is rather high and doesn’t prevent anybody from suing me against this very detail. I’m already fed up with it a bit. It won’t stop scammers and spammers from harassing you and me.
I won’t go that far and close this blog. That’s not the way to go IMHO, because the web is far more interesting than what facebook & Co. have to offer. The legal uncertainty (Thanks, government!) has to be answered, though, so here I present you what measures I’ve taken to be reasonably GDPR-compliant. In simple words, just as the law text is demanding it.
The data collected with this blog and its underlying mechanisms are for maintaining the website and simple reach measurements only. This includes the data collected by the webserver which is stored in common logfiles. These data are composed of your IP address (at the moment of access), your browser, your referrer, and other technical data like the file transferred, its size, the http answer code, the timestamp etc. Since this blog is a private endeavour, there is no purpose for these logs other than measuring the site’s popularity. Logfiles get deleted after a couple of months.
Until the end of the aforementioned legal uncertainty, I have disabled all methods of submitting comments here. (There weren’t that much comments in the past, anyway.) There is also no contact form where you would be able to leave your personal data. This site is connected to Akismet, but no spam filtering will happen until the day I’m going to enable commenting again.
This is a WordPress-driven site and it uses Jetpack for various reasons, including statistical analysis of user access to this site. Automattic uses cookies for enabling so. If you don’t want cookies from my site, please configure your client accordingly. If you follow linked material, including the sharing buttons at the end of each article, you are using the site of the respective owner.
This website is hosted on premises of a US web provider. That means all data transmitted from my site to your client and back is leaving the legal space of EU, in some circumstances. There is not much that I can do. Since there is no other personal information but your IP address I assume that you accept this fact implicitly.
