Privacy, in plain language.
This notice describes the implemented data flow. Operator details, the final retention schedule, and jurisdiction-specific rights must be reviewed before a public launch.
Information used to operate chat
The service processes an adult-consent confirmation, a random browser device identifier, a short-lived session token, your selected mode, interests, and country preference. Country preference is self-selected rather than verified location. OpenTalk matching may connect you with another Omegleweb visitor or an OpenTalk visitor in the same mode.
Connection data is processed to run the service. Omegleweb operational records include session outcomes, platform attribution, aggregate request and connection metrics, and device restrictions. The application does not persist raw IP addresses in those records. Hosting or network providers may separately process request information under their own configuration.
Conversation content and media
Text messages are relayed through the shared OpenTalk service to the current conversation partner. Omegleweb does not write message content to its local operational database; handling by OpenTalk is subject to the applicable service operator information. Omegleweb does not persist SDP or ICE signaling content or record audio or video.
Video media travels directly between browsers using WebRTC with STUN-assisted connection discovery. There is no TURN relay: the other participant may learn your network address, and restrictive network rules can prevent media from connecting. The other participant can copy messages or record their screen; the service cannot prevent or retract those copies.
Browser storage and identifiers
Browser storage may retain your theme preference and a random device identifier. Session credentials are short-lived; they are not a public account. A device identifier is not a fingerprint or verified identity and can be cleared by the user.
Clearing browser storage removes local preferences and identifiers but does not automatically erase already-retained operational records. There are no payment forms or advertising trackers included in this implementation.
Reports, retention, and access
When OpenTalk matching is in use, reports are submitted to the shared OpenTalk service with a reason and session metadata, not a transcript or media recording. The OpenTalk service and its operators handle those reports; submitting one does not guarantee immediate review or a particular outcome.
Report handling, access, and retention are governed by the applicable service operator's published terms and privacy information. Check that information before relying on a retention period or a particular review process. This page does not promise a retention period for OpenTalk reports.
Questions and requests
Use the contact page for privacy questions and requests about operational information. Describe the approximate time and nature of the request without sending passwords, session tokens, private media, or identifying information about another participant.
The service has no permanent account identity or chat transcript to search. An operator may need limited additional information to assess a request, and may be unable to identify every record associated with you. Applicable legal rights depend on the operating jurisdiction.