Do I need an opt-in to use Trackboxx?
From our perspective, using Trackboxx does not require opt-in consent.
We recognise that some privacy experts take a different view because Trackboxx temporarily processes a visitor’s IP address.
Here is a brief statement from our data protection team:
"Storing personal data does not always require consent. This requirement does not follow from the TTDSG either: Section 25 TTDSG covers cookies and similar technologies. Article 6 GDPR provides the possible legal bases, and legitimate interests may apply to Trackboxx.
Trackboxx processes the IP address solely to anonymise it, or to pseudonymise it for as long as the hash remains valid."
Even so, we want to make Trackboxx as privacy-friendly as possible, so we also provide an opt-out option.
You can find this option in the section on your privacy policy HERE. HERE we also explain how to add the opt-out manually.
Trackboxx provides web analytics without cookies and without storing personal data.
We use the visitor's IP address once, together with a few other non-personal parameters, to generate a hash that recognises the visitor during the current visit. The hash is stored for no more than 24 hours and then deleted automatically, so the visitor cannot be recognised later.
It is not possible to view a visitor’s history or recover an IP address from the hash.
We store only essential analytics data, such as visitor numbers, page views, traffic sources, bounce rate and device type.
Hashing and decryption explained:
We create two hash values: one for the visitor and one for the page being viewed.
User Hash: Signature Hash + IP + User Agent + SiteID + Current Day
Page hash: Signature Hash + IP + User Agent + SiteID + Hostname + Path + Current Day
The signature hash is renewed daily, ensuring that the data cannot be decrypted retrospectively.
Because this topic still causes some uncertainty, here is a brief explanation:
A "cookie banner" or "consent banner" is essentially a way to obtain opt-in consent.
First, a cookie or consent banner informs visitors about the relevant data-processing activities. It then asks for active consent before the corresponding services are loaded or blocked.
