and when to tap Next.
Contact OmeCam With the Details That Move Things Forward
Tell us what you tried to do, what happened instead and when it happened. The right details help support investigate without exposing passwords, verification codes or full payment information.
- support[at]omecam.net
- Technical, account and payment help
- Privacy and report follow-up
A message that says “help, it does not work” starts a second round of questions before anyone can investigate. A message that says “camera stayed black after I allowed permission in Chrome on Android at about 9:30 UTC” already points somewhere useful. You do not need technical language—just the action, result and context.
OmeCam support is available at support[at]omecam.net. For common camera, counter and account issues, the symptom-led troubleshooting matrix may solve the problem without waiting. For anything account-specific, use the relevant checklist below and leave sensitive information out.
The OmeCam support email and what to put in the subject
Write to support[at]omecam.net with a subject that names the area: Camera access, Matching issue, Account recovery, Payment status, Privacy request or Report follow-up. Include the approximate time with a time zone, your device and browser, and the action you took immediately before the issue.
If an error message appeared, copy its non-sensitive text exactly. A screenshot can help when it shows the problem without exposing personal conversations, addresses, payment details or another person’s image. One clear example is usually more useful than a long sequence of repeated attempts.
For camera, microphone or matching problems
- Your device model, operating system and browser version when you know them.
- Whether the browser asked for permission and what you selected.
- Whether another camera or conferencing app was open at the same time.
- Whether you were on Wi-Fi or mobile data, without sending your network password or precise location.
- The stage that failed: camera preview, matching, first connection, sound or video during the call.
Across the platform, 50% of matches connect in about 10 seconds and 90% within 15 seconds, but individual attempts vary. Mention whether the stall happened once or repeatedly. The connection timing explanation distinguishes aggregate platform figures from a device-specific fault.
/avatar/18591872/22e43fa41f65a82ac705fb587db8a111.png)
For account access and free-try questions
Explain whether you bound an email, changed devices, cleared browser storage or created more than one account. Include the bound address if it is necessary to identify the account, but never include its password. Describe what the free counter showed before and after the action, and whether you were looking at a marketing badge or the live Try Free counter.
The marketing badge is fixed at Free × 10 because it describes the daily allowance. Try Free shows your actual remainder and decreases after use. Account/device limits can also affect eligibility. The free counter and account rules help identify which situation applies before you write.
For coin or VIP payment questions
Include the product type, approximate payment time and visible status. If you have a non-sensitive order reference, include it. Do not send the full card number or security code. Avoid making repeated payment attempts while the first result is uncertain.
Prices can change and the app shows the current price before payment. Coins and VIP are virtual goods and purchases are non-refundable. Support can investigate a payment status, but the virtual-goods purchase rules remain part of the agreement.
For privacy requests and report follow-up
For a privacy request, state whether you are asking about access, correction or deletion and identify the account appropriately. Do not email extra documents “just in case.” The privacy choices and data categories explain how account, device, analytics, payment and support information is handled.
Every user report receives a reply within 24 hours. If you are following up, include the original report context and approximate time rather than submitting repeated reports. Moderation is AI-first, with human review for disputed cases and staff available around the clock; AI does not analyze call footage.
What response timing applies
The confirmed 24-hour commitment applies to user reports. We do not invent a guaranteed response deadline for every technical, payment or privacy email. Give each request the details it needs, use one thread for the same issue and avoid sending duplicates that split the context.
Contact and support questions
Write to support[at]omecam.net. Include the issue, approximate time, device and browser, but never passwords or full payment-card details.
Say whether permission appeared, what you selected, whether another camera app was open and whether the failure happened before or after matching.
Include product type, time, visible status and a non-sensitive order reference if available. Never include full card details or security codes.
The confirmed response window is for user reports. We do not claim the same guaranteed deadline for every other support category.
Start with a clear description
Use the checklists below, then contact support[at]omecam.net if you still need help.
/moment/14481486/44587e1f86cd8c378bcb7a68edf765bf.jpg)