Simple, privacy respecting
website analytics

After you integrate tinyvisits on your webpage and after a new visitor arrives on one of your pages, the visitor is shown a cookie consent banner to either confirm or deny consent to collecting page view events. If the visitor agrees and gives consent, a cookie with anonymous cookie ID is stored on visitor's device and pageview events are sent to tinyvisits. If the visitor denies and rejects consent, a small local cookie is created to remember this preference to avoid showing the cookie consent banner during subsequent page browsing, and subsequently the pageviews are not collected.

If your webpage visitor initially consents to collecting page view events, but later decides to withdraw the consent, tinyvisits provides an option to do so. If the visitor withdraws consent, tinyvisits deletes previous visitor's collected page view events based on visitor's anonymous cookie ID.

tinyvisits only uses anonymous visitor cookie IDs for storing page view events. There is no computation, collection or storing of consent-less user fingerprints, which are typically computed by hashing (IP address + user agent + website + salt) by other "Privacy friendly analytics" solutions . The consent respecting cookie ID approach enables tinyvisits to properly provide your website visitors an option to withdraw consent and delete previous events associated with the cookie ID.

By not computing nor storing consent-less user hash fingerprints and by always requiring visitor consent before start of page view event processing, we avoid an unintended consequence of other consent-less page view analytics solutions of identifying visitor activity on multiple websites during a single day. Why? Since the so called "Privacy friendly analytics" rotate a unique salt identifier used for creating user fingerprints only once per day, at the end of the day, such consent-less user fingerprinting analytics are able to answer, if a given IP address + user agent have visited any websites or pages, where such analytics are installed.

In contrast, collected events in tinyvisits are always stored only for those visitors / cookie IDs, where explicit and free user consent was obtained. Followingly, to further minimize processing of personally identifiable data (even with the consent given by webpage's visitor), tinyvisits automatically masks the last 3 digits of the IP address during the start of processing of each collected event. Even then, the masked IP address is just temporarily used to perform a geo-location lookup, and the actual event is only stored using the anonymous cookie ID. Finally, the masked IP address is only processed dynamically and in memory on the tinyvisits servers, and only the anonymous cookie IDs are persisted in tinyvisits database storage.

We don't directly access your data or otherwise analyze your visitor data trends in any way. We can only directly access or analyze your data trends if you explicitly permit us to do so - such explicit permission might typically happen in relation to discussing potential new product features, updates, optimisations, data exports or issue troubleshooting and so on.