The controlling entity, its address, and how to reach it about data.
What is held for a Member — email, name, authentication credentials and session records — and that identity is managed by our identity provider rather than stored ad hoc.
That payment details are held by Stripe and not by us; we retain a customer reference and processed webhook events. Should be explicit that we never see card numbers.
Device records, room bindings, and the identity snapshot retained for each connected peer so that session participants can still be resolved after a device is renamed or deleted.
Session records and the tiers of connection telemetry collected for billing and quality reporting — raw samples, derived rates, and end-of-session aggregates — and how long each tier is kept.
That streamed audio and video is relayed, not recorded, and what transits a relay when a direct peer-to-peer path is unavailable.
Service logs, retention period, and the fact that they are held for operating and securing the platform.
The session cookie and anything else set. Must be revisited the moment analytics is introduced — that is the change that creates a consent obligation.
The third parties involved — payments, identity, relay, hosting — and where they operate.
Where data is stored and processed, and the basis for any transfer.
How long each category above is kept, and what deletion means for data already aggregated into billing records.
Access, correction, deletion, portability and objection — and how to exercise them.
How changes are notified and when they take effect.