[EN] Snoobi Privacy Manager

The Snoobi Privacy Manager

The Snoobi Privacy Manager, available for any Snoobi account administrator, is a central location in the Snoobi settings that determines how privacy settings are managed for your account.

With the exception of the Visitor ID Checker, they are available on request. The reason for this that most settings are destructive for the information Snoobi Analytics has stored for your account and we need to ensure the validity of the request for security and technical reasons

 The following options are available:

Visitor ID Checker

• Visitor ID Checker works together with the Snoobi website plugin. Visitors may wish to receive information what is stored about them. To ensure the request is valid, they copy and paste information from the Snoobi ID checking tool and send this to the website owner. For this to function, 1st-party cookies should be present since otherwise any data gatering is done completely anonymous. Click on the link to select the function.

Visitor Privacy settings

There are two options for this setting:

• Visitor level: this assumes that 1st-party cookies are enabled. If the cookie is present, Snoobi maintains the unique visitor ID together with the IP-address information. While Snoobi can still not determine private details of the visitor, this is the lowest level of privacy and should only be used when no Personal Identifiable Information (PII) is present in the web page url and there is explicit consent of the user or visitor.
• Account level is the most used Visitor Privacy setting. This option always removes the detailed IP-address information, even when the visitor gives consent for cookies to be stored.

Enforce a certain cookie level

Three cookie levels can be enforced, and they function independently from any setting that was made in the tracking code:

• Enable 1st party cookies: this assumes a cookie consent manager is available, visitors are informed and can provide explicit consent for cookies to be used.
• Enable session cookies only: then Snoobi enables the storage of cookies only during the web site session. Cookies are not maintained outside the current visit, are random and cann be read back to review return visits.
• Block all cookies: then Snoobi doesn't store any cookie in the visitor's browser, for fully anonymous browsing. No visitor can be recognized for a repeat visit.

Don't show organization names

• By default, Snoobi Analytics shows the names of the Internet Service Provider (ISP) or the name of the organization. There are instances where showing organization names is not fully in compliance with local privacy regulations since an organization can also be a single person.
  This setting provides the option to remove the name of the ISP or organization but still maintain other visitor information such as city, region and country.

Analytics session time-out

• Session time-out in Snoobi defaults to 30 minutes; this is a generic web analytics default which is observed by any web analytics tool.
  However there may be a need to increase this time-out, for specific webshops or for instance for the analysis of an intranet or portal.

Allow custom code with Snoobi tracking

It may be needed to add elements to the standard Snoobi Analytics tracking. This setting functions as a Snoobi Tag Manager to include other tracking elements during the Snoobi data collection. This is always a customized solution.
A few examples:

• Web applications, such as maps or complex e-commerce applications may need additional analytics elements beyond the standard url-level events.
• Web portals, intranet or extranet solutions may need to track login behaviour. Note: this level of customization will need a detailed description of the personal elements that are stored in Snoobi Analytics and a Data Processing Agreement (DPA), which also describes how personal data can be removed if a data subject requests removal.
• An additional solution such as Mouseflow or other additional analytics tool may need to be loaded together with the Snoobi tracking code.
• For compliancy reasons, it may be needed to remove personal information from the storage, where the collected url contains a name or an e-mail address.

Support for Cookiebot-specific tracking code.

• With the October 2024 release, we added the option to include Cookiebot (tm) specific tracking code to allow or disallow cookies and to review what cookie levels were chosen.