How it works

For anybody who wants to know what is actually happening rather than being told it is safe.

Matching

A queue held by the realtime gateway. When two people are compatible the server mints an opaque per-pairing key and tells each side whether it is the one that opens the connection. That key is not either person's identity and cannot be turned back into it — the server never sends one user to the other.

The video path

Video is peer-to-peer once connected; the server relays only the handshake, with size and rate limits on it. That means we are not in the middle of the stream — which is good for privacy and is exactly why automated checks happen on sampled frames at the edges rather than by us watching a feed.

What a report keeps

The reporting account, the reported account, the triggering material, the transcript of that session, and the time. Held for a stated window, readable by moderators, then deleted. A report after the other person has already left still identifies them, because the pairing is remembered for exactly that reason.

Questions

Is the video encrypted?

WebRTC media is encrypted in transit by design. The handshake is relayed by us; the media is not.

Can you read my conversation?

Not in general. A reported session's transcript is preserved for moderation; an unreported one is not stored at all.