Privacy Policy

Last updated: September 29, 2026

This Privacy Policy explains how Omezy (omezy.io) collects, uses, shares, retains, deletes, and protects information when you use our text, voice, and video chat, account, safety, reporting, and moderation features. If you sign in with Google, Section 3 explains exactly which Google user data we receive and what we do with it. Legal requests and the full Data Retention Policy are also described on our Legal Inquiry page.

Our approach: Omezy collects information such as email, name, age or birth date, IP address, country signals, interests, cookies, device data, and safety logs primarily to operate the service, protect users, prevent abuse, enforce our rules, and personalize the experience. Information we receive from Google or another sign-in provider is used only to create, secure, and run your account — it is never used for advertising, never sold, and never used to train AI models.

1. Scope

This Policy applies to Omezy websites, applications, and services that link to it. It does not apply to websites, identity providers, advertising networks, payment providers, or other third-party services that we do not control.

2. Information we collect

Account and identity information

When you sign in, we may collect information from you or your sign-in provider, including your email address, display name, avatar, provider account ID, authentication event data, account status, and session identifiers.

Age, profile, and matching information

We may collect your age confirmation, birth date or age-related profile data, gender where provided, country or region signals, same-country preference, interests, language or regional preferences, and other settings used to connect you with eligible users and enforce safety rules.

Device, network, and cookie information

We may collect IP address, IP-derived location, browser type, device type, operating system, user agent, timestamps, pages visited, referral data, cookies, local storage identifiers, session cookies, security tokens, rate-limit identifiers, and similar technical information.

Chat, report, and safety information

Omezy processes text messages, video signaling metadata, match events, skip events, disconnect events, moderation signals, spam and bot-detection signals, report reasons, report details, moderator actions, reputation events, and abuse-prevention logs.

Text chat is processed in transit and may be included in limited operational logs, safety buffers, report evidence, or moderation records. Video media is not continuously recorded by default, but a report from a video session may include a small still-image snapshot submitted for moderator review.

Communications and support

If you contact us, submit feedback, request help, appeal a moderation decision, or make a privacy request, we may collect your message, contact details, and information needed to verify and respond to the request.

3. Google user data (Sign in with Google)

You can sign in to Omezy with your Google account. This section describes how Omezy accesses, uses, shares, protects, retains, and deletes the Google user data it receives when you do. It applies in addition to the rest of this Policy, and for Google user data it takes precedence over any other section.

What Google user data we access

Omezy requests only Google's basic sign-in scopes: openid, email, and profile. With your permission, Google shares the following with us:

your Google account identifier — a unique ID that lets us recognize you when you sign in again;
your email address, and whether Google has verified it;
your basic profile information: your name (including given and family name) and the link to your Google profile picture, plus your language setting where Google includes it.

We do not request access to Gmail, Google Drive, Contacts, Calendar, YouTube, or any other Google service, and Omezy cannot read, send, change, or delete anything in your Google account. The access token Google issues during sign-in is used once, on our server, to retrieve the information above and is not stored. We do not request offline access or refresh tokens.

How we use Google user data

To create your Omezy account, sign you in, and recognize you when you sign in again.
To show your name and profile picture in your own account and profile settings. We do not show your email address, name, or Google profile picture to the strangers you chat with.
To secure your account, for example by checking that your email address is verified before any sensitive account permission is granted.
To keep the service safe, for example by recognizing an account that was banned for violating our rules, and to handle reports about that account.
To contact you about your account, safety, or legal matters when needed.

We use Google user data only to provide and secure these user-facing features of Omezy. We do not use it for advertising of any kind, including personalized, retargeted, or interest-based advertising; we do not sell it; and we do not use it to develop, improve, or train generalized artificial intelligence or machine learning models.

How we share, transfer, or disclose Google user data

We do not sell Google user data, and we do not transfer it to advertising platforms, data brokers, or other information resellers. We share it only:

with service providers that host and operate Omezy's servers and databases on our behalf, under confidentiality and data-protection obligations, and only as needed to run Omezy;
with authorized Omezy moderators and administrators, only when needed to investigate abuse, review reports, or enforce our rules;
when required by law or valid legal process, or when necessary to protect the safety of users or the public, as described in Section 13;
as part of a merger, acquisition, or asset transfer, in which case it stays subject to this Policy.

How we protect Google user data

Google user data is transmitted only over encrypted connections (HTTPS/TLS) and stored in access-controlled databases on servers operated for Omezy. Access is limited to the systems and authorized personnel that need it for the purposes above, and staff access is logged. Omezy's own session identifiers are stored in hashed form, and sign-in requests are protected against forgery with one-time state values.

Retention and deletion of Google user data

We keep your Google account identifier, email address, name, and profile picture link for as long as your Omezy account exists, so that you can keep signing in. You can delete your account at any time with Delete My Account under Account & security in your account menu, or by emailing [email protected]. Your account is deactivated immediately and permanently erased — together with all Google user data linked to it — 30 days after your request; during those 30 days you can cancel the deletion by contacting us. Copies in backups are overwritten on our normal backup rotation. Records are kept longer only where the law requires it or where an active ban or safety investigation requires it, as described in Section 8.

You can also remove Omezy's access to your Google account at any time at myaccount.google.com/permissions. Removing access stops future sign-ins with Google; to erase the data Omezy already holds, request deletion as described above.

Limited Use disclosure

Omezy's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4. How we use information

We use information for the following purposes:

To create, authenticate, secure, and maintain user sessions and accounts.
To match users by availability, interests, country preference, safety status, and technical compatibility.
To enforce Omezy's age requirement and protect users from ineligible access, exploitation, harassment, spam, bots, scams, and other abuse.
To receive, investigate, prioritize, and resolve reports and moderation actions.
To detect suspicious patterns, rate-limit harmful activity, prevent ban evasion, and preserve evidence where needed.
To improve reliability, debug errors, measure performance, and understand how the service is used.
To personalize the service, recommendations, safety prompts, and advertising based on interests, coarse location, cookie data, and usage signals where permitted by law. Information received from Google or another sign-in provider is never used for advertising (see Section 3).
To communicate administrative, account, safety, legal, and service updates.
To comply with law, legal process, and valid government or law enforcement requests.

5. Cookies and similar technologies

Omezy uses cookies, local storage, and similar technologies to keep you signed in, remember preferences, protect sign-in (OAuth) flows, prevent abuse, measure performance, and personalize content or advertising. Some cookies are necessary for the service to work. Others may support analytics, security, or advertising.

You can control cookies through your browser settings. Blocking cookies may limit sign-in, matching, reporting, moderation protections, or other interactive features.

6. Personalized advertising

Omezy may use limited interest, cookie, coarse location, device, and usage information to show or measure personalized advertising where permitted. We never use Google user data or other information received from a sign-in provider (your name, email address, profile picture, or provider account ID) for advertising, and we never share it with advertising partners. We also do not use sensitive safety report details, private chat contents, or moderation evidence to target ads.

Advertising partners may process pseudonymous identifiers or aggregated audience signals on our behalf. We do not sell your personal information for money. If privacy law treats certain advertising disclosures as a "sale" or "sharing," you may contact us to request available opt-out options.

7. How we share information

We may share information with:

Service providers that help us host, store, secure, moderate, analyze, email, authenticate, route video connections, or operate Omezy.
OAuth or identity providers when you choose to sign in through them. Google user data is shared only as described in Section 3.
Advertising, analytics, and measurement partners subject to legal requirements and partner restrictions.
Moderators, administrators, contractors, and safety reviewers who need access to protect users and enforce our rules.
Law enforcement, regulators, courts, or emergency responders when required by law or when we believe disclosure is necessary to prevent serious harm, child exploitation, fraud, abuse, or threats.
Successor entities if Omezy is involved in a merger, acquisition, financing, reorganization, or asset transfer.

We may also share aggregated or de-identified information that does not reasonably identify you.

8. Data Retention Policy

Omezy keeps operational, security, safety, and moderation data for 30 days, then deletes it automatically from active systems unless a valid legal hold, court order, active safety investigation, active account restriction, or another legal obligation requires preservation.

During that 30-day period, we may store account and authentication data, profile and matching data, device and network metadata, cookies or local storage identifiers, rate-limit and abuse-prevention records, chat and video session metadata, limited text samples, report excerpts, video report snapshots, moderation notes, reputation events, violation counters, ban or restriction reasons, admin audit logs, support requests, privacy requests, deletion requests, appeals, and legal inquiry correspondence.

We do not continuously record video chats by default and do not keep full video streams by default. Active bans or restrictions needed to enforce current access controls may remain while active. Once released or expired, their supporting records follow the 30-day deletion cycle. Backup deletion may take additional time according to backup rotation.

9. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to certain processing of your personal information. You may also be able to withdraw consent where processing is based on consent.

You can update certain profile information in the product where available.
You can request account deletion through the product where available or by contacting us.
You can revoke camera, microphone, notification, location, or cookie permissions through your browser or device settings.
You can choose not to provide certain optional interests or profile details, although matching quality may be affected.
When Omezy lets you save a chat log, the file is saved locally by your browser and is not automatically uploaded to Omezy.

We may need to verify your identity before fulfilling a request. We may deny or limit requests where permitted by law, including when needed to protect other users, preserve safety evidence, comply with legal obligations, or prevent abuse.

10. Children's privacy

Omezy is available only to users who meet our age requirement. You must be at least 18 years old to use Omezy. We do not knowingly allow people under 18 to use Omezy, and we do not knowingly collect personal information from people under 18. If we learn that a person under 18 has used Omezy, we may remove or restrict the account and delete information where appropriate, except where preservation is needed for safety, legal, or child-protection reasons.

11. Security

We use technical, organizational, and access-control measures designed to protect information, including encrypted transport, session controls, restricted staff access, logging, monitoring, and abuse-prevention systems. No internet service can guarantee perfect security, and users should avoid sharing sensitive personal information with strangers.

12. International transfers

Omezy may process and store information in countries other than your own. Where required, we use appropriate safeguards for international transfers.

13. Government, legal, and emergency requests

We review legal and emergency requests case by case. Omezy provides user data only in response to a court order or a valid written request that we can verify and legally process, or in limited emergencies when allowed by law and necessary to prevent death, serious physical harm, child exploitation, fraud, abuse, or threats to Omezy or its users. We may challenge or narrow requests that are invalid, overbroad, or inconsistent with applicable law. See our Legal Inquiry page for request requirements.

14. Changes to this Policy

We may update this Policy as Omezy evolves. The updated version will be posted on this page with a new last-updated date. Your continued use of Omezy after an update means you acknowledge the updated Policy.

15. Contact

Privacy questions, legal inquiries, or data requests can be sent to [email protected].