Documentation menu

Data Collection and your Customers' Privacy

Wide Angle Analytics was created to allow your business to analyze traffic in a kind and respectful manner. We take special care of your customers' data.

We are transparent about the data we collect. Here you will find a compiled list of all the data points collected and stored by the service.

Please consider using this information to create relevant disclosures for your End Users as necessary.


By default, our tracking code neither uses nor transmits cookies.

In the Site settings, you can enable Cookie Support. When this setting is activated, the tracker code will create an HTTP(S)-only, SameSite restricted cookie valid for 24 hours since the last activity.

The cookie stores the visitor's identifier, which improves tracking of unique visits over a short period.

Because the cookie is HTTP(S) only, your browser is instructed not to share it with other scripts that you might be using on your site.

Moreover, the SameSite policy tells the browser never to send the cookie to any third party.

These restrictions ensure that the cookie is used solely for improving tracking on your website and not across third-party sites. Additionally, the tracking identifier is never shared outside of Wide Angle Analytics.

Session Identifier

The uniqueness of a page view can be determined based on the request and can be augmented with browser information. We use one of three ways to create a session Identifier.

Request-Based Identifier

A default setting. To satisfy the strictest privacy regulations, this approach to tracking visitors uses only the information sent via the default HTTP request. The service captures the visitor's IP Address and browser's User-Agent, and generates an obfuscated, non-reversible identifier of the session. This identifier is further anonymized using random, transient values and information about the current site.

This weak session identifier is not a fingerprint in the regulatory sense. It is not durable and is both session and site-specific.

Client-Based Identifier

The code running in the browser generates the browser's unique identifier using its characteristics. This creates a good approximation of visitor uniqueness but does not guarantee it.

Statistically speaking, in most cases, the fingerprint generation will be repeatable and consistent for the same device with each visit.

It's worth noting that we do not store generated fingerprints verbatim. We believe this would result in Wide Angle Analytics creating a long-term record of Personally Identifiable Information. Therefore, the fingerprint, when stored, undergoes non-reversible obfuscation.

This fingerprinting technique leverages access to intrinsic browser details. Depending on the jurisdiction, this can constitute data requiring user consent.

This option is disabled by default.

Service-Based Identifier

The site can be configured to use a service-based Tracking ID. In this approach, the script on your website will inquire Wide Angle Analytics for a unique ID for an unknown session. The generated ID will be used to represent the current visitor's activity.

The outcome of in-browser fingerprinting is ignored when this feature is activated.

By default, this ID is not persisted in the visitors' browser. Therefore, when a visitor reloads a browser page, the ID will be forgotten and requested again.

Due to the limitation mentioned above, the Service-Based Identifier is effective in the following two scenarios:

  1. In Single Page Applications (SPA), where visitors rarely refresh the browser window/tab, or
  2. When the Site Cookie setting is enabled, thus allowing the service Tracking ID to be stored in the browser cookie.

Want to learn more?

The Cookieless Tracking section of our knowledge base dives deeper into technical aspects of various tracking methods available to you.

Data sharing

Input Objects GmbH, the company behind Wide Angle Analytics, never shares your visitors' data with third parties. Your visitors' data is used solely to present you with analytics about your site traffic.

The content of this page is not legal advice.
Always consult your Data Protection Officer or a data privacy lawyer.

Still need help? In that case please contact our support via, email or chat.