Synthetic on purpose
It talks to no authenticated endpoint. It describes the shape of what can be collected, not anything that was collected.
PRIVACY MANIFEST
The privacy manifest, as the software enforces it.
This synthetic explorer describes the allowed schema. It contains no customer, tenant, device, or telemetry instance.
Trust version 2026.11.3 · generated 2026-11-14T09:12:04Z
Proof
What this page is for
This explorer describes the allowed schema. It contains no customer, tenant, device, or telemetry instance.
You can read a field, see its classification, see which plans persist it, and see the release in which it appeared or changed. There is no live data behind it and no way to make it show any.
On this page
What you get from this
Release privacy diff
Version over version: fields added, removed, or reclassified. A release with no collection change says so.
Generated from the schema
The field list on this page is not a description of the software. It is generated from the schema the software enforces.
Collection boundary
The boundary
We observe here
Byte and packet counts, protocol, an encryption indicator, destination country, network operator, registrable domain, the app or browser that opened the connection, timestamps, and direction.
We never collect here
Communication content, URLs, paths, query strings, DNS names beyond the registrable domain, headers, cookies, tokens, files, screenshots, form data, keystrokes, usernames, email addresses, hardware serial numbers, or precise location.
Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.
Availability across plans
Personal
Included
Pro
Included
Team
Included
Enterprise
Included