This article will explain the primary mission and purpose of Burst Statistics: To follow best practices for your user’s privacy while still being able to have meaningful data to improve your business or personal blog.

What is Privacy-Friendly?

Privacy-Friendly does not mean it’s always permitted before consent. Depending on your region and guidelines, Burst Statistics might need consent. An example is the United Kingdom, where any Analytics tool needs consent, independent of the configuration.

In Germany, for the DSGVO, Burst Statistics can be set before consent because it meets the requirements of anonymization, minimization and hosting the data locally, instead of a third-party, e.g., Google Analytics, for example.

Privacy-Friendly for Burst Statistics is minimizing data, anonymization, and keeping data locally, while being flexibile with Consent Management integrations.

A misunderstanding about Cookies

Although we will soon release an option to implement Burst without cookies. Cookies are not the issue, per se. Cookies are controllable and easily removed by the end-user. They can be removed by third-party browser extensions and make the web user-friendly. But some cookies contain personal data and relationships between your device and you as a user and can be stored on your device without consent.

Some cookies do not require consent. These cookies do not interfere with the user’s privacy in any way, or the user’s privacy is overruled by the function of a cookie. These cookies are rare and solely used to protect the user against fraud and theft, for example, a cookie from a payment provider. There’s an alternative approach, but is it any good?

A misunderstanding about Cookieless Tracking

Of course, why even bother with a discussion about cookies if you can remove them altogether? Besides the technical implementations and implications, there are two reasons to consider using cookies in the future:

  1. Privacy Laws are not about cookies. Cookies are just a medium for collecting data and tracking. In Europe, cookies are referenced in the ePrivacy guideline, but the “General” Data Protection Regulation has a much more comprehensive range regarding data collection and sharing. “Cookieless Tracking” still has “Tracking” to worry about.
  2. As mentioned earlier, cookies are easier to control, remove and understand by the public. If all tracking is pushed towards server-side API calls, the end-user has no say in collecting and sharing their data if the website operator does not comply with the privacy law.

If a website doesn’t not ask consent for cookies. You can always remove the cookies. If the website does not ask consent for cookieless tracking, there’s now way for you to remove the stored data.

Developed by Complianz from Really Simple Plugins

Burst Statistics is the newest member of Really Simple Plugins to meet the needs of everyone dealing with privacy guidelines while working with third parties to collect statistics, e.g. Google Analytics, Matomo Cloud, Yandex, Clicky etc. We want to offer a statistics tool that is built for privacy and ease of use for everyone. In the beginning, it will offer the essential metrics and flexibility to configure your metric calculation with everything owned by you. Burst Statistics is not a processor or third-party.

The aim is to collaborate with our users to build the best alternative for your current statistics tool without worrying about privacy or complicated integrations with native WordPress plugins like WooCommerce. Please leave a feature request and keep using Burst Statistics to start collaborating!

Hessel de Jong

Hessel de Jong

Hessel is the Developer & Co-Owner of Burst Statistics

Table of Contents