ONE PERSON · REAL CONVERSATION
OmeCam conversation portrait for OmeCam Privacy Policy Without the FogA face, not a feed.
You decide when to stay
and when to tap Next.
What the service uses and why

OmeCam Privacy Policy Without the Fog

Starting without a profile form does not mean a service needs no data. This policy explains the information OmeCam uses to create accounts, provide matches, protect the platform, process purchases and answer requests.

  • No public profile form required
  • AI does not analyze call footage
  • Privacy requests via support[at]omecam.net
See the match process

This Privacy Policy applies to omecam.net and the account, matching, communication, analytics and payment features that support it. It describes categories of information and the reasons they are used; it does not make broad claims such as “no data is collected” or “nothing is ever retained.”

Account and contact information

Your first use creates an account automatically without a registration form. The account can hold a service identifier, free-try usage, follows, settings, purchase history and other information needed to provide continuity. You are not required to create a public biography before starting.

If you bind an email, that address can be used for account retention, security and support. Binding is intended to reduce the risk of losing the account, not to publish your address to matches. An account can exist without a public profile because anonymous video chat does not require a public bio.

Device, browser and permission information

The service may process device, browser, operating system, approximate network and technical diagnostic information needed to deliver pages, maintain security and troubleshoot failures. Camera and microphone access is mediated by browser or device permission. You can change those permissions through your browser or operating-system settings.

Your camera shows what you place in frame. Documents, addresses, badges and other people can reveal information even when you do not type it. Review your own preview before a call. Browser permission does not remove your responsibility for what you voluntarily display or say to another user.

Matching, usage and analytics information

We use interaction and journey information to understand product operation: page entry and exit, scroll depth, match-flow stages, format choices, free-try activity, wallet steps, checkout retention and payment outcomes. Analytics helps identify where users leave, which features cause difficulty and whether the activation-to-payment funnel works.

Google Analytics 4 is used for measurement. Analytics events should describe actions rather than capture secrets. Do not enter passwords, verification codes or full payment-card details into support messages or other fields that are not specifically designed for them. Platform-wide connection figures may be reported in content, but individual results are not guaranteed.

Cookies, local storage and similar technology

Cookies and local storage can remember account state, preferences, free-try ledgers, analytics and security information. For example, the Try Free counter needs a daily record so the displayed remainder decreases after use. Clearing browser data can remove local information and may affect access to an account that has no bound email.

Browser controls can restrict or remove stored data, but blocking necessary storage may prevent account, matching or payment features from working correctly. Bind an email before important account history depends on a single browser or device.

Payment and virtual-goods information

When you choose coins or VIP, payment processing requires purchase and transaction information such as product type, status, amount and order reference. Payment providers may process payment credentials under their own terms. Do not send full card details through ordinary support email.

Prices can change and the app displays the current price before payment. Coins and VIP are virtual goods and purchases are non-refundable. Transaction records can be needed for accounting, fraud prevention, support and legal obligations; the virtual-goods agreement contains the purchase rules.

Support messages and report information

When you contact support, we process the information you choose to provide, including the issue description, account identifier, device/browser details, non-sensitive order reference and any attachments. Send only what is relevant. Passwords, verification codes and full card details are not useful support material.

Reports can include the reporting account, reported account, interaction context and moderation outcome. Every report receives a response within 24 hours. That response commitment does not mean every support category has the same guaranteed deadline.

AI-first moderation and disputed human review

Moderation begins with AI review. When a case is disputed, human moderators step in, and human moderation staff are available around the clock. AI does not analyze call footage. This process can require report content, account identifiers, technical signals and review outcomes to assess and enforce platform rules.

We do not claim that every report receives manual handling or that every call is watched by a person. The moderation control explanation describes the same workflow from the user’s perspective and distinguishes Next, Block and Report.

Service providers, legal obligations and security

Information may be processed by providers that support hosting, content delivery, analytics, payment processing, customer support, security and moderation. They receive the information needed for their role rather than unrestricted access for unrelated purposes. Information may also be disclosed when reasonably required by law, to protect users or the service, or to investigate fraud and abuse.

We use reasonable organizational and technical measures, but no online service can promise absolute security. Retention depends on the information’s purpose, account status, dispute needs, fraud prevention and legal obligations. When information is no longer required, it should be deleted, anonymized or otherwise handled according to applicable requirements.

Your privacy choices and deletion requests

Depending on applicable law, you may request access, correction or deletion of eligible account information, or object to certain processing. Send the request to support[at]omecam.net and identify the account appropriately. Verification may be necessary, but do not attach unnecessary sensitive documents before the correct process is confirmed.

Some records may need to be retained for security, fraud prevention, payment, dispute or legal reasons even when other information is deleted. For the practical details to include, use the privacy request checklist. We may update this policy as the service changes; the updated date identifies the current version.

Your next hello

Privacy works better with informed choices

Check your camera frame, account email and support details before you share them.