In this day and age, opting out of cookies has become the default and tracking tools switching to cookie-less alternatives has become the fashion. Thankfully, the HockeyStack team follows the fashion trends.

The HockeyStack snippet that you receive when you sign up by default is modified for cookieless tracking:

<script async data-apikey="YOUR_API_KEY" data-cookieless src="<>"></script>

The data-cookieless attribute runs the script under cookieless tracking and removing that would automatically switch you to cookie-based tracking.

But then how do you track unique visitors?

Although we can't disclose all the details, we use a fingerprint generated at the server and hashed (sha256) with a unique salt so that it would be impossible to obtain the original data from the fingerprint.

To create this fingerprint, we use data such as but not limited to:

All this data is gathered through the browser, and its variety ensures that the fingerprint created is as unique as possible.

<aside> 💡 It is important to note that HockeyStack does not in any way store IP addresses or other PII (personally identifiable information) to create this fingerprint.

The validity of the fingerprint relies on the combination of all these different datapoints. When hashed, it gives no one, including HockeyStack itself, to attain any further information about the visitor.

ec5d7eb1-4c2b-4da0-a214-c7059f1fa9e6 This is an example user id that was generated from the system. As you can see, it is impossible to decrypt but gives you an opportunity to record unique traffic.