Evidence, not adjectives
The trust centre publishes the privacy diff, the subprocessor register, deletion commitments, and the real status of every certification — including the ones we do not hold.
FOR SECURITY LEADERS
Answer the jurisdiction question without starting a log project.
Build an organisation-level record of observed destinations, conformity, coverage, and source evidence.
Context
The situation
The board, a regulator, or a customer asks where your data goes. You need a defensible answer in days, not a six-month logging programme.
Build an organisation-level record of observed destinations, conformity, coverage, and source evidence. Enterprise quotes dedicated hosting, a retention policy, and compliance triggers without changing the collection boundary.
On this page
What you get from this
A new agent is new risk
So the client's interfaces are named, its resource budget is measured against a published method, and its permission set is justified item by item.
Quoted, not packaged
Enterprise is custom quoted. There is no implied floor, and no implied EU establishment.
Collection boundary
The boundary
We observe here
Deploying Precyz does not create a new content-bearing data store. The collection allowlist is closed and published. Tenant scope is derived server-side and is never trusted from client input.
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
Not the fit
Pro
Not the fit
Team
Shared workspace without dedicated hosting
Enterprise
The fit, quoted