Privacy Policy

WorkingHardInIT Blog Privacy Policy

We do not share personal information with third-parties nor do we store information we collect about your visit to this blog for use other than to help analyze and fix problems with hosting this blog. Cookies are used minimally where needed, which you can turn off at any time by modifying your internet browsers settings. We are not responsible for the republishing of the content found on this blog on other Web sites or media without our permission. This privacy policy is subject to change without notice when needed to adhere to new or evolving privacy laws.

Measure taken to help protect your privacy

WordPress Plugins

I do not use (or have stopped using) plugins that do or “might” collect personal data other than those that track usage statistics and have proven to be GDPR compliant. Those are:

  • JetPack
  • Google Analytics Dashboard for WP (GADWP)
  • Wordfence

Log files & analytics

We minimize the use of log files and web analytics services. When we do use them gather some information inside the log files. This includes internet protocol (IP) addresses, type of browser, Internet Service Provider (ISP), date/time stamp, referring/exit pages and number of clicks. We use these stats to analyze issues, administer the site and to help secure the site by spotting malicious behavior. IP addresses and other such information are not linked to any information that is personally identifiable.

We use Google Analytics to collect non-personal information, when you use our online site, in the form of various usage and user metrics. These tools and technologies might and can collect and analyze certain types of information, including demographic and interests data, cookies, IP addresses, device and software identifiers, referring and exit URLs, on-site behavior and usage information, feature use metrics and statistics, and other similar information.

You may opt out of Google Analytics by visiting the Google Analytics opt-out page. For more information also check Google’s Remarketing Privacy Guidelines and Restrictions.


Cookies are used minimally where needed, which you can turn off at any time by modifying your internet browser’s settings.

Feedback Form

There is a feedback form that helps protect my e-mail address and requires your name and e-mail address to get back to you if needed.

Comments on articles

You are allowed to leave anonymous comments. You can also provide a make-believe user name, a make-believe or throwaway e-mail address and non-existent website or leave that blank. That’s fine. You can leave your real info and know that your user name will appear publicly on the blog comment as will your website. Your e-mail will not be shown and will never be shared and /or sold.


I do not publish one or will publish one.

RSS Feeds

You can subscribe to the RSS feed on this blog but this will never require personal data. Only normal web service logging occurs when you access an article via the RSS feed.

Blog post and comment subscription

If you subscribe to the blog or to comments on a blog post you provide an e-mail address. This is never used for any other purpose. Consider using a separate non-personal e-mail address for this purpose to help protect your privacy.


If you have Gravatar and use this to like a blog or any other purpose the extent of your disclosure is what you have chosen to be online there.


Backups of this blog are made and kept securely in Azure. These are retained only for recovery purposes for a reasonable time (31 days). Backups are not used for any other purpose.

Privacy by design

We don’t use your e-mail address for anything other than if you request us to get in touch with you.

We get rid of any (potentially) personal data as soon as we can. We have no interest in maintaining it for any longer that needed for the purpose of operating this blog.

We don’t ask for personal data ever, as everything on this blog is free, we don’t need it.

We do not collect data from anywhere else on our visitors (Facebook, Twitter, blog comments, LinkedIn, …)

Technical measures taken to protect our and your information

This blog (WordPress) is well secured and kept up to date. So are the plugins. The blog is hosted on a well maintained, secured OS. The platform components are well secured, they are updated regularly and fast to provide the best possible protection. All this happens on well secured infrastructure that complies with rigorous security requirements (Azure). As such it adheres strictly to privacy laws.

Accept our privacy policy

You must read and accept the privacy policy of this blog. That’s is the consent we need as required by GDPR, for you to read this blog, post comments or submit feedback.

GDPR User information requests & “right to be forgotten”

We provide you with a personal data request and a “right to be forgotten” option. Do note that this might not show or do anything as we keep personal data to a minimum. We can not report or delete what does not exist. This is work in progress and as the tooling for wordpress becomes better and more complete this will be enhanced.

Breach notification

This blog is monitored for security issues and breaches. We don’t want to be hacked and if we ever are we’ll let you know on this blog (if that’s still an option after the hack). Note that as we do everything to minimize having any information on you we cannot notify you personally.