When visitors leave comments on the site we collect the data shown in the comments form via Disqus (https://www.disqus.com), a third-party application, and also the visitor’s IP address and browser user agent string to help spam detection. Information shared with this site via Disqus to be used within their application. Please refer to Disqus support (https://disqus.com/support/) as to how to view your data there.
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.
When entering information via the contact form, you are releasing your name, email address, and data in form of text to be sent to the owner of this website. The information will be used for communication purposes and may be retained for an infinite amount of time. However, the information will not be used for marketing purposes unless it’s stated within the form.
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.
If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
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.
This site uses two types of Analytics. One is with WordPress.com via Jetpack, which will track which pages you visit, but without any information attached to them. The other is Google Analytics, which will track the pages you visit and depending on your settings, may tie your IP address to it.
Who we share your data with
The information shared with me may be used for marketing purposes. However, it will be anonymized and thus, can’t be traced back to any one individual unless they share a comment via the Disqus application. Within the Disqus application, that data is shared with the general public within the website. Comments may also be shared on the website with/without permission to help bring in traffic.
How long we retain 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 will be checked through an automated spam detection service via the Disqus application. Data collected in contact forms are sent to us via email and maybe retain on the server as a backup.
Last updated: May 28, 2018