Privacy Policy

Who we are

Our website address is:

What personal data we collect and why we 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.

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: After approval of your comment, your profile picture is visible to the public in the context of your comment.


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


Please see our Cookies Policy


We embed a Facebook widget to allow you to see number of likes/shares/recommends and “like/share/recommend” our webpages. This widget may collect your IP address, your web browser User Agent, store and retrieve cookies on your browser, embed additional tracking, and monitor your interaction with the widget, including correlating your Facebook account with whatever action you take within the widget (such as “liking/sharing/recommending” our webpage), if you are logged in to Facebook. For more information about how this data may be used, please see Facebook’s data privacy policy:


We use a Twitter Tweet widget at our website. As a result, our website makes requests to Twitter’s servers for you to be able to tweet our webpages using your Twitter account. These requests make your IP address visible to Twitter, who may use it in accordance with their data privacy policy:

Linkedin Share official button

We use a Linkedin Share widget at our website to allow you to share our webpages on Linkedin. These requests may track your IP address in accordance with their data privacy policy:

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 tracking your interaction with the embedded content if you have an account and are logged in to that website.


Who we share your data with

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.


We use Webpushr to handle our notifications. If you have opted in to receive notifications, Webpushr will store the following information on its servers for each Subscriber:

They do not store any data related to your site visitors that have not opted to receive push notifications. Webpushr is not able to determine end-user identity with the current data it stores.

dateThis is the date when the subscribers opts to receive push notifications from your site.
endpointThe endpoint takes the form of a custom URL and associated encrypted keys pointing to a push server.
timezoneSubscriber’s local timezone.
device_typeMobile or Desktop.
operating_systemMac OS, Windows, Android, etc.
browserChrome, Firefox, Opera, Edge, etc.
ip_address change settingSubscriber’s IP Address.
cityGeographic Location: City
stateGeographic Location: State
countryGeographic Location: Country
session_dateDate corresponding to the last session

Webpushr – cookies


Webpushr JavaScript snippet use HTTP Cookies to “remember” what a user has done on previous pages / interactions with the website. These cookies are used to control the opt-in prompt behavior on the site, based on user specifications.

_webpushrPageViewsWe only store this cookie if the publisher (you) set the prompt (Custom Prompt) to show after x page visits.This cookie tracks the number of page visits on publisher’s site. If the publisher (you) decide to select native opt-in prompt then this cookie is not set.
_webpushrSubscriberIDThis is set for non-https sites ONLY to check if the user is subscribed or not
_webpushrPromptActionThis cookie is stored if the user declines to receive push notifications and dismiss the custom prompt. This helps us remember that decision.
_webpushrEndPointThis cookie stores a unique URL associated with the user’s push subscription. It is only stored if the user accepts to receive push notifications.
_webpushrLastVisitThis cookie stores timestamp associated with the user’s last visit on the site. It is only stored if the user accepts to receive push notifications. This helps us successfully manage and send push notifications.

Webpushr – Data Retention

Webpushr stores subscriber data indefinitely unless the subscriber unsubscribes from receiving push notifications. Webpushr automatically deletes all subscriber data from it’s servers when a user unsubscribes