Privacy Policy
Last updated: August 9, 2026
Short version: We do not store your video, audio, or chat messages. We do not require registration. We collect only the minimum technical data required to operate the service, and we do not sell your data to third parties.
1. Overview
This Privacy Policy explains how OmeTalk ("we", "us", "our") collects, uses, and handles information when you use our anonymous video chat service ("the Service").
We are committed to collecting as little data as possible. This service is designed to be ephemeral — conversations are not stored, recorded, or retrievable after they end.
2. Information We Collect
2a. Information you provide
We do not require you to create an account. The only information you voluntarily provide includes:
- Gender — selected on the landing page to enable matching preferences. Not stored beyond the session.
- Interests — optional tags you add to improve match quality. Not stored beyond the session.
2b. Information collected automatically
When you connect to the Service, our server automatically receives:
- IP address — used to enforce per-connection rate limits and prevent abuse. Held only in server memory while you are connected; discarded on disconnect.
- WebSocket connection metadata — timestamps, connection state, queue position. Held in memory only; not written to any database.
- Server logs — our hosting provider may retain standard access logs (IP, timestamp, HTTP method) for a limited time for operational purposes. We do not control these logs.
2c. What we do NOT collect
- Video or audio streams — these are transmitted peer-to-peer (WebRTC) and never pass through our servers
- Chat message content — messages are relayed in real time and not stored
- Name, email, phone number, or any identifying personal information
- Device fingerprints or browser tracking identifiers
- Location data beyond coarse IP geolocation
3. How Your Video and Audio Work
Video and audio are transmitted using WebRTC (Web Real-Time Communication), a peer-to-peer technology built into modern browsers. This means your video and audio stream goes directly from your device to your partner's device — it does not pass through our servers.
To establish this peer-to-peer connection, we use:
- STUN servers (Google's public STUN) — help your browser discover its public IP address. Your IP is shared with Google's STUN infrastructure momentarily during connection setup.
- TURN servers (if configured) — act as a relay when a direct peer-to-peer connection cannot be established due to firewalls or strict NAT. If a TURN server is in use, encrypted media packets pass through it, but the content remains end-to-end encrypted.
4. Cookies and Tracking
We do not use cookies for tracking, advertising, or analytics purposes. The Service does not use any third-party analytics (e.g. Google Analytics) or advertising networks.
Your browser may store session state (e.g. your selected gender/interests) in memory during a page session. This data is cleared when you close the tab or navigate away.
5. Data Sharing and Third Parties
We do not sell, rent, or trade your personal information to any third party.
Data may be shared only in the following limited circumstances:
- Hosting providers — our server and frontend infrastructure providers (e.g. Koyeb, Netlify, Render) may process connection data per their own privacy policies.
- Legal requirements — we may disclose information if required by law, subpoena, court order, or to protect the rights, property, or safety of users or the public.
6. Data Retention
We do not operate a database. All session data (IP address, queue state, room assignment) exists only in server RAM and is discarded when your WebSocket connection ends.
There is no data to delete because no data is persistently stored. If you disconnect, all associated information is gone.
7. Children's Privacy
This Service is not intended for anyone under 18 years of age. We do not knowingly collect any information from minors.
If you are a parent or guardian and believe your child has used this Service, please contact us immediately. We will take appropriate action to the extent possible given the ephemeral nature of the platform.
8. Security
All connections between your browser and our signaling server use TLS (HTTPS/WSS) encryption. WebRTC peer-to-peer streams are encrypted using DTLS-SRTP, the standard security layer for WebRTC.
However, no method of transmission over the internet is 100% secure. We cannot guarantee the absolute security of data transmitted through the Service.
9. Your Rights
Because we do not store personal data, most data subject rights (access, correction, deletion, portability) are satisfied automatically — there is nothing to access, correct, delete, or export.
If you have specific privacy concerns or requests, you may contact us through the platform's public GitHub repository.
10. Changes to This Policy
We may update this Privacy Policy from time to time. The "Last updated" date at the top of this page will reflect the most recent revision. Continued use of the Service after any changes constitutes acceptance of the updated policy.
11. Contact
For privacy-related questions or concerns, please reach out through the platform's GitHub repository or any publicly listed contact channel.