Privacy Policy

Who I am

My website address is: http://www.grootersnet.nl/sysblog.

What personal data I collect and why I collect it

Comments

When visitors leave comments on the site I collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

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.

Contact forms

Simply: There is none. You can reach me by standard email, and messages may be saved – including the email address used for sending the address, all headers and all contents – for my own use and reference. Private data will never be shared.

Cookies

If you leave a comment on my 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, I 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, I 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.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracing your interaction with the embedded content if you have an account and are logged in to that website.

Analytics

Who we share your data with

If you enter a comment on the site, you explicitly agree it may be shown on the site, including your login name. If you do not want to comment to be shown, send your comment by email….

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 registered on my website, I 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). As website administrators I 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

Contact information that you supplied will be stored locally, invisible for other users. As website administrator, I can see and modify this information, if needed, I will only use it to contact you in case there is a need to.

Additional information

How we protect your data

This site is hosted on a system that is secure by design (OpenVMS – as you may expect). Local access is limited to myself, as site owner and system manager. Your data (except the comments you have entered) cannot be accessed by other visitors.

What data breach procedures we have in place

In order to monitor access, all IP traffic is logged by the router by which you access the local network, and any component you are using. These logs contain date and time of access, IP address from where access is attempted, , protocol used, and, if applicable, the page(s) or files you are requesting. I used this data to trace attempts to break into the system, bypass security and other malicious behaviour. The data is not shared in case of suspicion of malicious access; If the address is a hosting company or ISP, they will be informed of the attempt; If required, the data will be shared with law enforcement. In some cases – at my discretion – the name of the owner of the address may me mentioned in a post.
Access to the system and all data is only possible by the software I am using to allow you to access the site, or by my own programs that cannot be accessed without local access with insufficient privilege. Such local privileged access is restricted to the site administrator and system manager: myself.
If a data breach is suspected from an external source, the IP address – or, if required, complete subnet – of the perpetrator is denied access to the local network. All external users will be notified.

What third parties we receive data from

The software I use is OpenVMS 8.4 ( the WASD webserver, a basic WordPress installation. The database used is Mark Berryman’s port of MariaDB, and I used his PHP port as well.

What automated decision making and/or profiling we do with user data

Industry regulatory disclosure requirementsNone. I’m on my own 🙂