Documentation

How does inSites ensure that user data remains anonymous?

For each visitor who triggers an event, a unique hash is calculated based on several pieces of info (including shortened IP, user agent). However, we do not store the actual IP. To ensure that this hash is unique, but cannot be traced back to the visitors, we also use a randomly generated string ("salt") when calculating the hash. This string is not stored permanently at any time and is regenerated every eight hours. This means that every visitor who revisits your site and whose last visit was more than eight hours ago will receive a new hash, even if the IP and user agent remain the same.

At least for inSites you don't need a cookie banner. inSites works completely without cookies.

However, it's best to check if you use other services that use cookies and require cookie warning or consent.