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 analyse content performance through the use of cookies, which you can turn off at any time by modifying your Internet browser’s settings.

When commenting on each blog post, information such as your email address and IP address is provided to us. The information provided is only used in the instance of blocking users who wish to misuse the comments section. This information is stored within WordPress and by commenting you consent to providing that information to us. Should you want to not have this information shared with us, please contact us through the Contact Page to have this information removed. This will also remove any and all comments you have made on the page as well.

When using the contact form, again your email address and IP is shared with us. The information is only stored for as long as any correspondence goes on.

We are not responsible for the republishing of the content found on this blog on other websites or media without our permission. This privacy policy is subject to change without notice.


Some advertisements on this website are served by third-party advertising companies. Please note that our advertisers may also use cookies, and/or, web beacons to collect aggregate and non-identifying information about our users. We do not have control over third-party advertisers’ technologies or how they may be used. If you have any questions, you should contact the responsible advertiser directly.


Web beacons, also known as pixel tags are electronic images contained on a website that permit us to count users who have visited those pages and for other related website statistics. Web beacons are not used to access your personal information on our website and are only used to compile aggregated statistics concerning use of our website.

Please also see WordPress and Automattic’s Privacy Notice for all other guidance relating to this site, and it’s compliance with GDPR.