I try and collect absolutely nothing about the visitors. No tracking, no analytics, even the newsletter, you can sign up with whatever email address you want and unsubscribe at any time. If you listen to the podcast, that service might collect data about devices used and countries but no IPs or any other information. I use a service like 33mail.com to filter out my newsletters so the entities never really have my actual email address. I encourage you to use a VPN, a fake name generator and services like 33mail.com. That way, you get your questions answered but in private.
Who I am (or rather this blog)
See the About Me page
What personal data I collect and why I collect it
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
If you use the contact forms on this site or send an email, that information is used to reply back but we don’t store or export it beyond the ability to reply back.
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
We currently host the podcast on Podbean. While we collect no analytic data from our internal pages, Podbean collects some basic data if you listen through their website, such as country and type of device. We cannot see any detailed information about you such as your name, city, IP address, etc.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
Aweber, the service used to collect emails to be part of the newsletter is a perfect example. That is content that blockers and trackers will pick up.
None! Can you believe it. I do not use Google Analytics or JetPack or anything else to track behavior. I don’t collect usage stats, log your IP indefinitely or anything else.
Who we share your data with
Nobody except Aweber if you sign up for the newsletter. Otherwise, I don’t share, rent or use anything you provide for anything.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Your contact information
How we protect your data
We used TLS encryption for transmission of data from this site to your browser.
What data breach procedures we have in place
Since we collect no data, if breached, my blog stores nothing more than posts and comments. Your email and email addresses are not stored here except in the database if you comment so use whatever email address you want. We don’t collect credit cards or any other payment.
What third parties we receive data from
What automated decision making and/or profiling we do with user data
Industry regulatory disclosure requirements