If you've read our Privacy Policy and our guides on chat history and data after leaving, this page is the short version — one table, the same accurate information, nothing new to read through if you just want the quick answer.
| What | Why | How long |
|---|---|---|
| IP address | Required for the connection to work, and used for abuse prevention if a report is filed | Security logs kept up to 30 days, then deleted |
| Browser / device type | Compatibility — making sure the video call works properly on your specific browser | Session only, not stored afterward |
| Room or language chosen | So you're connected with the right room — Tamil, Telugu, Hindi, or wherever you picked | Session only |
| Report details (if filed) | Category selected, session identifier, timestamp — used for moderation review | Kept until the case is resolved, then removed |
| Cookie consent choice | So we don't ask again every time you visit | Stored in your browser, not on our servers |
| Anonymised analytics (if consented) | Page views and general usage patterns, via Google Analytics | Aggregated, not tied to an individual |
That's the complete list. There's no row for a device fingerprint, a hardware hash, or a persistent tracking ID, because none of those exist here.
Video and audio aren't in the table above because they're never collected at all — they travel directly between the two devices in a call and never reach our servers in a form we could even log. It's not that we collect it and discard it quickly; there's no point in the data's path where Chatzyo could capture it in the first place.
Chatzyo doesn't sell any of this to advertisers — covered in more detail in our Ad Disclosure. The only circumstance where information is shared outside the company is cooperation with law enforcement for credible threats, child safety concerns, or other serious illegal activity, as described in our Terms of Service. That cooperation is based on whatever IP and report data we actually have — not a hardware identifier, since one doesn't exist to share.
Mainly for abuse prevention — if a restriction needs to be applied or a pattern of reports needs context, the IP address is the only thing tying a session to an enforcement action, since there's no account to attach it to instead. After 30 days, it's deleted regardless of whether it was ever used for anything.
Only that you picked that room, for matching purposes during the session. It's not stored afterward or tied to anything else about you — it's functionally the same as picking a tab to open, not a profile setting that persists.
The analytics row in the table above simply doesn't apply to you — Google Analytics never activates without consent, governed by Consent Mode v2. Everything else in the table (IP, browser type, room choice) still applies regardless, since those are functional necessities for the platform to work at all, not optional tracking.
No. Analytics, when active, reports aggregated patterns like total page views or which rooms are visited most — it isn't cross-referenced with report history, session details, or anything tied to a specific person, because there's no identity for it to be tied to in the first place.
This page is intentionally short. For the fuller explanations behind each row in the table above, our other privacy guides go deeper: why conversations aren't stored, what happens the moment you disconnect, and the complete legal version in our Privacy Policy itself.