OmegleWeb.ONLINE
The data side of OmegleWeb: guest sessions, camera and microphone permission, cookies, moderation signals — and the choices that stay with you.
Start a video chat →OmegleWeb is built on one mechanic: two strangers, one private video call. This policy lays out what the service handles when you read a public page, open a match, or keep a guest session alive. Reading pages like this one — the FAQ, the blog — requires no account and collects nothing personal.
Live video chat runs on two permissions: your camera and your microphone. Both are granted and revoked in your browser, never on our servers. The lens activates only after you allow it, and each call is a closed room for two — no spectators, no public streams, nothing broadcasting you anywhere. Nothing is ever installed on your device.
A live matching service cannot run without ordinary technical data: device and browser basics, server logs carrying IP addresses and timestamps, and aggregated page-usage patterns. Your guest session stores whatever keeps it working — remaining free matches and any coin balance. Coin purchases pass through external payment processors, so full card numbers never touch our servers; the terms of service describe the same arrangement.
Cookies hold your session together mid-match, remember minor preferences, and anonymously tell us which pages get read. A few are strictly necessary — matching cannot function without them. The complete list, with refusal and clearing instructions, lives in the cookie policy.
Tapping report or block can attach session context to a moderation review, giving the team enough to act on abuse. That loop is what pulls repeat offenders out of the matching queue. The rules being enforced are written down in the community guidelines.
Camera on or off, stay or skip, keep a session or wipe it — ending the call is always one tap and closing the tab is always allowed. To correct or delete session data, write to us through the contact page. We never sell personal information. Full stop.