Method and limits together
Geolocation is advisory. Coverage may be incomplete. The document says so.
EVIDENCE AND AUDIT READINESS
Evidence needs scope, method, and limits.
A useful artefact states when it was generated, which devices and dates it covers, where its records came from, and what the method cannot establish.
Context
The situation
A dashboard is not evidence. A useful artefact states when it was generated, which devices and dates it covers, where its records came from, and what the method cannot establish.
Precyz reports and exports carry scope, generation time, retention window, and limitations on the face of the document. Generated evidence is never itself an authority.
On this page
What you get from this
Not a pass/fail certificate
An auditor can sample the record. Precyz will not sell the record as a compliance opinion.
Staleness is visible
Every generated artefact is marked when it is stale.
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