Last updated: June 23, 2026
1) The short version
- OmeChat does not require a user account for normal chat use.
- We process IP addresses, browser-generated fingerprints, session and client identifiers, interests, language metadata, country preferences, reports, moderation data, security logs, and operational metrics to run the service safely.
- We do not keep full chat transcripts as a normal product feature.
- We do not keep permanent video recordings as a normal part of the service.
- Video chat includes a local browser 18+ confirmation. We do not collect your birthdate, ID, or account details for that confirmation.
- Moderation screenshots are kept for about 14 days by default unless they are retained for safety, fraud prevention, or legal reasons.
- Other moderation records are kept for about 30 days by default unless they are retained for safety, fraud prevention, or legal reasons.
- Because video chat is peer to peer with STUN, the other participant may be able to infer your IP address.
2) Who controls the data and how to contact us
OmeChat controls the data.
Privacy contact: [email protected]
If you are using the service without an account, include as much detail as you can when you contact us so we can find the right records.
3) What data we process
Depending on how you use the service, we may process the following types of data:
- Your IP address and basic connection metadata.
- A browser-generated fingerprint used for matching, abuse prevention, and ban enforcement.
- Session IDs and client IDs used to connect chat sessions and route messages.
- Your chat mode, such as text or video.
- Your interests and other matching preferences.
- Browser language metadata used to present the service and support matching.
- Your selected or detected country preference, if country matching is enabled.
- Normalized referrer host data used to classify traffic as direct, search, referral, or internal without storing the full referrer URL.
- Reports, report reasons, and optional report notes.
- Moderation snapshots and their encrypted image files.
- Video-quality moderation signals, if they are used, to help detect abuse, broken sessions, or poor-quality video.
- Limited two-sided WebRTC failure diagnostics for failed video connections, including public peer IPs, retry counts, signaling and candidate summaries, and connection metadata used for troubleshooting, but not raw SDP or raw ICE candidate strings.
- Security and moderation logs, including login attempts and moderation actions.
- Aggregate operational metrics such as active user counts and service health data.
4) What we do not store as a normal product feature
- We do not store full conversation transcripts as a normal product feature.
- We do not keep permanent video recordings as a normal part of the service.
- We do not use video-quality moderation signals for face recognition or identity matching.
Other participants can still record, screenshot, or copy what happens on their own device. We cannot prevent that, so please treat every chat as potentially copyable.
5) Why we process data and what legal basis we rely on
We use the legal basis that best fits the activity and the law that applies to the request. In practice, that usually means the following:
| Purpose | Typical legal basis |
|---|---|
| Service operation and matching | Contract performance or legitimate interests |
| Abuse prevention, rate limiting, and bans | Legitimate interests |
| Reports, moderation, and safety review | Legitimate interests and, where required, legal obligations |
| Admin and security logs | Legitimate interests |
| Optional local preferences and matching settings | User choice and legitimate interests |
| Legal compliance requests | Legal obligation |
6) How long we keep data
We keep data only as long as we need it for the reason we collected it, to comply with law, or to protect the service and its users.
| Data | Retention |
|---|---|
| Join tickets | Short-lived, about 2 minutes |
| Live presence and queue state | Short-lived, about 1 hour |
| Moderation snapshot images | About 14 days by default unless retained for safety, fraud prevention, or legal reasons |
| Reports and other moderation records | About 30 days by default unless retained for safety, fraud prevention, or legal reasons |
| STUN failure diagnostics | Rolling cap of the newest 100 WebRTC diagnostic snapshots |
| Ban records | Until expiry or as long as needed for enforcement |
| Security login attempts | Currently no automatic cleanup is defined in the app; kept as long as needed for security review and lockout support |
| Aggregate anonymous metrics | May be kept longer if they are truly aggregated and no longer identify a person |
7) Your data rights
Depending on where you live, you may have the right to ask us to access, delete, correct, restrict, or object to our processing of your data. You may also have the right to data portability where applicable.
If you think we processed data incorrectly, you can contact us and ask us to review it. You also have the right to complain to your local data protection authority or supervisory authority.
8) Anonymous-use limitation
We do not use accounts for normal chat use, so we sometimes need identifiers, timestamps, IP addresses, or short matching windows to locate the right records. If you ask us for access, deletion, or another privacy request, please include the approximate date, chat mode, report reference, client ID, or other details you have so we can find the right data.
9) Processors and third parties
We may use third parties that help us run the service, such as:
- Hosting and infrastructure providers that help us run the application.
- Delivery and security providers, if they are part of the deployment.
- Monitoring, logging, and observability providers, if they are used.
10) International transfers
Some providers may process data in countries outside your own. Where required, we use safeguards such as contractual protections or comparable transfer mechanisms so the data stays protected at a reasonable level.
11) Automated moderation
We may use automated systems and rule-based checks to help with spam prevention, abuse detection, moderation triage, and service reliability. Those systems support human review rather than replacing it completely. When practical, serious enforcement actions should involve human review.
If we use video-quality moderation signals, they are for safety, reliability, and abuse detection. They are not used for face recognition or identity matching.
12) Children and adults only
OmeChat is for adults only. You must be 18 or older to use this service. If you believe a minor has used the site or shared personal information here, contact us immediately.
13) WebRTC and IP exposure
Video chat on OmeChat uses direct peer-to-peer WebRTC connections with STUN servers. Because of that, the person you are matched with may be able to infer your IP address as part of the connection. If you do not want that risk, do not use video chat.
14) Contact
If you have privacy questions or want to use your rights, contact [email protected].