Trust
Data & privacy
What Gauss collects, how it counts visitors without cookies, and where the data lives. This page describes how the system works. The legal terms are in the Privacy policy and the DPA.
What we collect
The full list of fields in an event. It is generated from the event schema, so it always matches what the system actually stores.
| Field | Type | What it contains | Example |
|---|---|---|---|
ts | Date and time (UTC) | Time the server received the event, in UTC. | 2026-10-25T10:42:17.381Z |
site_id | Integer | Internal number of the site in Gauss. | 1042 |
name | Text | Event name, such as page_view or generate_lead. | page_view |
page_path | Text | Page path without query parameters. Email addresses and phone numbers are replaced with [redacted]. | /blog/how-to-choose |
page_host | Text | Domain of the page. | shop.example |
page_title | Text | Page title, up to 200 characters, cleaned the same way. Sending it can be turned off in site settings. | How to choose a coffee machine |
content_group | Text | Page category, only if the site marks it up itself. | blog |
prev_page_path | Text | Previous page on the same site, without query parameters. | /blog |
is_entrance | Yes / no | Whether this is the first page of the visit. | true |
referrer_host | Text | Domain the visit came from. The full external address is not stored. | t.me |
channel | Text | Traffic channel: search, paid, social, email, referral or direct. | social |
utm_source | Text | UTM source of the visit. | telegram |
utm_medium | Text | UTM medium of the visit. | social |
utm_campaign | Text | UTM campaign of the visit. | oct_promo |
utm_term | Text | UTM term of the visit. | — |
utm_content | Text | UTM content of the visit. | — |
ad_click | Yes / no | Whether the visit started with an ad click. The click ID itself is not stored. | false |
country | Text | Country, determined from the IP address in memory. | TR |
region | Text | Region, only if the site owner turns it on. | — |
device_type | Text | Device type: desktop, mobile, tablet or other. | mobile |
browser | Text | Browser name. | Safari |
browser_major | Integer | Major version of the browser. | 18 |
os | Text | Operating system. | iOS |
visitor_id | 64-bit hash | Daily visitor identifier: a hash that is valid for one site and one day. | 9f2c41d07ab35e18 |
session_id | 64-bit hash | Visit identifier, valid within one day. | 4b7e90c1d2f3a456 |
session_seq | Integer | Order of the event within the visit. | 1 |
persistent_id | 64-bit hash | Reserved for the optional consent-based mode (planned). Always 0 unless the site owner enables that mode and the visitor consents. | 0 |
site_date | Date | Date of the event in the site's time zone. | 2026-10-25 |
retention_months | Integer | How many months the detailed event is kept under the site's plan. | 3 |
params | Key–value pairs | Event parameters, up to 25, such as form_id. This includes the values of query parameters that the site owner explicitly allows in site settings, such as a site search query (stored with the key q_<name>). Text values are cleaned, and keys that look personal are dropped. | {"form_id":"callback"} |
engagement_ms | Integer | Time the page was visible, in milliseconds, from the page-leave event. Used for time on page. | 42000 |
scroll_depth_pct | Integer | How far the page was scrolled: 0, 25, 50, 75, 90 or 100 percent. | 75 |
value | Number | Conversion value, if the site sends one. | 40 |
currency | Text | Currency of the value. | EUR |
transaction_hash | 64-bit hash | Keyed hash of the order ID, used to count an order only once. The ID itself is not stored. | — |
items | List | Products in an e-commerce event, in the GA4 format: ID, name, brand, category, variant, price, quantity, coupon. | [{"item_id":"CM-200","price":189.9,"quantity":1}] |
What we don't collect
- No cookies, localStorage, sessionStorage or other browser storage.
- No fingerprinting: no canvas, WebGL, audio or font detection.
- No stored IP addresses. The IP address is used in memory to compute the visitor identifier, determine the country (and the region, if the site owner turns it on), filter out traffic from data center networks and limit request rates, then discarded.
- No stored user agent string. Only the browser and its major version, the operating system and the device type are kept.
- No form field values, phone numbers or email addresses from contact links.
- No ad click IDs. Only the fact that an ad click happened is stored.
How visitors are counted
We don't store IP addresses or user agents. When an event arrives, they are used to compute an identifier that is valid only for one site and one day. The key for this calculation is deleted every day, after which the identifier can no longer be linked to an IP address.
Personal data cleaning
Before storage, email addresses and phone numbers in international format (starting with +) in page paths, page titles and event parameters are replaced with [redacted]. Parameters with names such as email or phone are dropped. Sending page titles can be turned off in site settings.
Hosting
We will state here the country where visit data and its backups are stored before any data is collected. Service providers that process other data, such as email, and the countries where they do it are listed on the Subprocessors page.
How long data is kept
Detailed events: 3 or 13 months depending on the plan. Daily reports: 25 months. When a site or account is deleted, all its data, including backups, is deleted within 30 days.
This website
gausslab.io uses the Gauss tracker itself and sets no cookies. There are two exceptions. When you switch the site language with a regular click, the place you were reading (the page address, the section and how far you scrolled in it) is kept in this tab’s sessionStorage under the key gauss:lang-scroll and deleted as soon as the next gausslab.io page opens in this tab, so you continue reading at the same place. And only after you click the theme switch, the chosen theme (light or dark) is saved in localStorage under the key gauss:theme so the site opens in it next time. Nothing else is stored, and you can remove it by clearing site data.
Country detection
The country, and the region if the site owner turns it on, is determined from the IP address in memory, using the free DB-IP Lite database. The IP address is also checked in memory against a database of networks (ASN) to filter out traffic from data centers and hosting providers. It is not stored.