The phone is not being observed
The app reads the same data your account already holds, over the same authenticated API.
MOBILE COMPANION
Read your posture on a phone. The phone is not being observed.
The iOS and Android companions are read-and-notify only. They capture no connection metadata and contain no map.
Context
The situation
A companion app for a product that watches network activity raises an obvious question before it raises any other: is it watching this device too?
The mobile companion is read-and-notify only. It renders posture, notices, and reports for the signed-in principal and delivers notifications. It is not an observer.
On this page
What you get from this
Permissions, item by item
The requested permission set is published in the store listing and on this page, with the reason for each.
Any future change would be a new decision
Observing a phone would require a new architecture decision and a published impact assessment before it shipped.
Collection boundary
The boundary
We observe here
Nothing about your phone. The mobile app captures no traffic metadata on iOS or Android. It has no network extension, no VPN profile, and no packet path.
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