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.
LEARN
Understand where connection metadata can take you.
Practical guides cover data sovereignty, destination evidence, transport metadata, and the limits of observation.
Context
The situation
Connection metadata can answer questions that contracts only describe. These guides stay on the evidence side of that line.
Practical guides cover data sovereignty, destination evidence, transport metadata, and the limits of observation.
On this page
What you get from this
Data sovereignty
Policies describe intent. Observed destinations supply a dated record.
Where data goes
A destination-country view makes activity legible without reading content.
Country traffic posture
Document expected locations and compare observations deterministically.
Encryption in transit
An encryption indicator describes the envelope, not the communication inside it.
Evidence and audit readiness
A useful artefact states scope, method, and limits.
Metadata-only architecture
On-device reduction removes page addresses before a record can be sent.
Collection boundary
The boundary
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