🔑 Data collected

Neglecting to gather any data would be impractical for a tool designed for analytics. We do gather the essential data to provide you with straightforward insights. However, compared to other analytics platforms, we limit our data collection to only what's essential. Below, you'll find a breakdown of what we do and don’t accumulate from your site's visitors.

Refer to our metrics overview to see a comprehensive breakdown of the data we gather.

🍪 Cookies

Your visitors' privacy is paramount to us. Cookies, which can monitor users across different pages or even sites, are not used by us. The same principle applies to other technologies, such as local storage, session cookies, digital fingerprinting, and hashing of IP addresses.

The Need for Consent in Online Cookies

Web analytics tools, such as Google Analytics, depend on cookies to gather and track personal data. Their software inherently uses cookies. By its standard configuration, Google Analytics employs several cookies to recognize users over various browsing instances and across different sites. This method of data collection is the reason behind legal mandates insisting that website proprietors seek user agreement through cookie alerts or pop-ups. These sometimes-irritating notifications consume precious screen real estate and compel users to acknowledge and permit the accumulation and retention of their data.

👨‍💻 IP address

We only collect the IP address to determine the country and city, and nothing beyond that. We do not transmit your IP through our servers, nor do we have access to it or any means to store it.

⏰ Timestamp

We employ time markers to produce the charts displayed on your dashboard, enabling you to assess shifts in your website's activity across different time spans.

🎛 User Agent

We understand the importance of user privacy. While we do collect the User Agent to enhance the functionality and user experience of our platform, we take steps to ensure this data is completely anonymized. We don’t use User Agents for fingerprinting, only for counting operating systems, device types, and browsers in your dashboard.

What is a User Agent?

A User Agent is a string that browsers send to websites, which describes the type of browser, operating system, and device being used. For example, a typical User Agent might look like:

Mozilla/5.0 (iPad; U; CPU OS 3_2_1) AppleWebKit/531.21.10 (KHTML, like Gecko) Mobile/7B40598

How do we anonymize it?

To maintain privacy while still gaining essential insights, we strip out specific details from the User Agent. For instance, the above string becomes:

Mozilla/5.0 (iPad; U; CPU OS 3_2_0) AppleWebKit/531.21.0 (KHTML, like Gecko) Mobile/7B40000

As illustrated, detailed version numbers are replaced with generic zeros, ensuring individual users can't be precisely identified based on their device's unique configurations.

Why do we collect the User Agent?

The anonymized User Agent allows us to understand the diversity of devices and browsers accessing our platform, helping us optimize for a wider range of users without compromising on individual privacy.

📹 Session Replay

The session recording on Fullog uses the MutationObserver API to capture events (click, scroll, etc). We allow you to reproduce these videos in order to contextualize the bugs and understand the user’s behavior.

🛤 URLs

We partially collect and partially store URLs

Overly detailed URLs can clutter your data interpretation. For clarity, we hone in on the primary elements of a URL. For instance, if you have a URL like https://mywebsite.net/page.html?query=term#section (opens in a new tab), our platform would only retain https://mywebsite.net/page.html (opens in a new tab).

This mainly encapsulates the secure protocol (https), the domain reference (mywebsite.net), and the file path (/page.html).

🚜 Referrers

Referrers help trace the pathway a visitor took to land on your website. Our system employs a dual approach to pinpoint a user's origin.

For most scenarios, browsers forward the link of the prior site as a referrer. This referrer information is saved in alignment with our URL processing methods (referenced earlier). Your analytics overview showcases a curated list of the most frequent sources of referral.

On another note, we also tap into UTM parameters to decode a guest's originating point.

🛵UTM-parameters

UTM parameters are textual additions to a URL, delivering extended insights to Fullog and other analytical platforms about the link's context. To give you an idea, consider this format:

https://webexample.org/feature-page?utm_source=brand-z&utm_medium=digital-release&utm_campaign=april-launch.

We archive every UTM parameter, not limiting ourselves to just the utm_source. These parameters are deemed non-intrusive to privacy since they cater to categorizing visitor cohorts rather than pinpointing individual users.