Envelope, not contents
Protocol and an encryption indicator are in the allowlist. Payloads are not.
ENCRYPTION IN TRANSIT
What transport metadata can tell you.
An encryption indicator and protocol describe the connection envelope. They do not reveal the communication inside it.
Context
The situation
People hear “encrypted” and assume the destination question is settled. Encryption describes the envelope. It does not name the country.
An encryption indicator and protocol describe the connection envelope. They do not reveal the communication inside it, and they do not replace destination evidence.
On this page
What you get from this
Encrypted still goes somewhere
A TLS session still has a destination country and a registrable domain.
No certificate authority
Precyz does not intercept or re-encrypt traffic.
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