Not a compliance opinion
It holds up as evidence about observed destinations over a stated window, on the devices in scope. It is not a compliance opinion and we will not let you cite it as one.
FOR CONSULTANTS
Produce transfer evidence a client will accept.
Create dated, scoped evidence with its method and limitations stated on the document.
Context
The situation
When a client asks you to show where their data went, you need something dated, scoped, and defensible — not a screenshot and a paragraph.
Record observed destinations for the devices in scope, compare them to the expected-location record you built with the client's own documentation, and generate a PDF and an accessible HTML report that state their scope, retention window, and limitations on the face of the document.
On this page
What you get from this
Personal cannot produce reports
Pro is the fit for a consultant who needs a dated artefact.
Read the sample first
Read a synthetic sample, including its limitations page, before you commit to it in a statement of work.
Collection boundary
The boundary
We observe here
The report cannot contain a field the collection allowlist does not contain. Geolocation is advisory and the report says so; a city is never presented as standalone evidence.
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 included
Pro
Included
Team
Included
Enterprise
Included