Voice · video · screen
Not turned into server-side history.
On a direct route, media travels between devices. Connect does not collect it for analytics, advertising or profiling and is not designed as a server-side call archive.
Trust
What passes through Connect — and what does not stay with Connect
Session content is separated from short-lived technical data required to establish network connectivity.
Chat · files
Not turned into a product database.
Messages, file names and file contents are not used as product analytics. On a direct connection they travel between participants and do not become Connect cloud storage.
Coordinator
Only what is needed to make the introduction.
A temporary room ID, network addresses and route parameters may be briefly processed to establish or restore connectivity. Their purpose is connection establishment, not user history.
Updates
No persistent client ID.
Build selection needs the Connect version, channel, platform, architecture and, for staged rollout, only a local bucket 0–99. It is not a unique identifier.
Product metrics
Aggregate connection health.
The coordinator may report aggregate connection attempts, successful connections, connection-time distribution, reconnects and grouped failure reasons. The metrics do not contain session content, room codes or persistent user/device identifiers.
Website · support
A separate context.
The public site does not use advertising trackers or optional analytics in the current configuration. If a user chooses to contact support, only the information they voluntarily submit is handled; that is not app telemetry.