Your conversation. Your choices.
This describes the data handling implemented in this version. The site operator must add their identity and contact details before public launch.
Accounts and sessions.
Accounts store your email, display name, password hash or Google identifier, preferences, and account restrictions. Anonymous sessions use a pseudonymous identifier. Session cookies are used to keep you signed in.
Conversations.
Messages pass through the realtime server. A limited recent text buffer is held in memory so reports can include context. Unreported buffers expire shortly after a conversation ends and are lost when the realtime process restarts. Voice and video are not recorded by this application.
Reports and operational data.
Submitted reports contain a reason, description, participant identifiers, and available text messages. Audit records and usage counters support administration and abuse controls. These records are automatically deleted on the configured retention schedule, shown below. Active account restrictions remain until an administrator removes them.
Your account controls.
Members can update saved preferences and delete their account from the account page. Deletion removes login identifiers and preferences and revokes sessions. A pseudonymous ID may remain temporarily where it is linked to a report.
External services.
If configured, Google supplies basic account information for sign-in. STUN/TURN services process network information to establish calls; TURN relays encrypted call traffic when needed. This application does not include advertising or analytics trackers.
Operator notice.
Before launch, the operator must provide a contact method, identify the operating entity, and review this notice for their deployment and jurisdiction.