No proxy
Traffic does not flow through Precyz. There is nothing to re-encrypt.
METADATA-ONLY ARCHITECTURE
Observe connection metadata without a content path.
On-device reduction removes page addresses and other content-bearing details before a record can be sent.
Context
The situation
A content path is a choice. Precyz does not have one. Observation happens at documented metadata interfaces, and reduction happens on the device.
On-device reduction removes page addresses and other content-bearing details before a record can be sent. The allowlist is enforced by the schema, and the schema is published.
On this page
What you get from this
No certificate authority
The client does not install a root that would let it read contents.
Published schema
The field list is generated from what 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