What data I collect and why I collect it
My blog and all the advice is all available for free. There are no banner ads and sponsored posts. I don’t try and sell you anything. I don’t even collect your email address and have reduced the amount of tracking and external scripts to the minimum.
The quick summary is that I have not, don’t and will not sell any information you give me. Read more about me.
I have removed all the Google Analytics and other tracking
One thing I have worked on is to reduce the number of external scripts. You would not believe how many external calls a simple WordPress design theme can make. Fonts, icons, analytics, pixel trackers and advertising banners.
I have removed all the Google Analytics tracking scripts. I do not know if anyone is reading this blog.
It all now loads faster. It saves you data and time. Your adblocker has nothing to block on my posts.
All this has made my blog GDPR compliant which means that I don’t need to bother you with those GDPR or cookie law notices either.
If you send me a message using my contact form
You need to fill in your name and email address when contacting me using my contact form. This is in order for me to be able to read your message and respond back to you.
I do not collect your IP address and I do not use your message, your name or your email for any other purposes other than to reply back to your message.
If you visit a page with embedded content from other websites
Even with all this effort, there are still a few places with some external calls. These are the posts where I embed podcasts or videos from other sites. YouTube supports no-cookie embedding so I use that when embedding videos.
I have reduced the number of embedded content to a minimum but some articles on this blog may still include embedded content (YouTube videos, audio podcasts, embedded tweets and such).
Embedded content from other websites behaves in the exact same way as if you visited the other website.
If you try to log in to my private admin area
In order to check login activity and potentially block fraudulent attempts, the following information is used for users who try to log into my admin area:
- attempting user’s IP address,
- attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process),
- and all IP-related HTTP headers attached to the attempting user.