If you are seeing this, your browser cache is holding incorrect data and needs to be cleared

After clearing the cache this message will disappear

If not please contact us

GDPR implementation and Web-Stat

Learn how to make your site GDPR-ready with Web-Stat

or click here for our own GDPR info and statement
Disclaimer:
It is your responsibility to ensure that Web-Stat services are permitted and abide by your local laws. Any information presented below is not legal advice and you should not rely upon it as such. The GDPR is a complex regulation: we recommend that you seek legal advice to understand it and prepare for it.

On May 25th 2018, the General Data Protection Regulation, known as the GDPR, came into effect. Its purpose is to protect the personal data of all EU citizens. Whatever the location of your business, if you own a website with EU visitors, or if your marketing campaigns target EU citizens, these changes affect you.

Basically, the regulation means that you have to go through all of your personal data processing activities and make sure that they comply.

Data processing activities on websites are usually of two types:

  1. Contact forms, email subscriptions, etc. where personal data is explicitly requested and submitted directly by the user.

  2. Cookies and online tracking, where information is collected without explicit user knowledge

With the enforcement of the GDPR, you have to evaluate what data you are gathering in both these situations, whether you really need this data and why, how you are keeping it secure and inform/get consent from the user.

The first item is related to your own site and we are not involved in this part

The second item, 'Cookies and online tracking', directly concerns Web-Stat and your use of our service.

By default, Web-Stat collects the IPs of visitors in order to geo-locate them approximately (country and city). However, the IP does not identify a natural person. We know that a visitor was on a site, we know what he did on that site, we know if he was there before, but we don't know 'who' this visitor is: we have no way of identifying him or her personally.

If needed we provide the option to anonymize all IPs collected from the Settings Panel

Regarding cookies, thee are two possibilities. Please select one:

  My account is using the default configuration

  I have set my account for cookieless tracking in the Settings Panel