CONTACT / HELP
A verified support email and submission form are not available here yet. Nothing you read on this page sends a request. For a camera problem, an uncomfortable conversation or a purchase question, the guides below explain what you can do now and which details to keep private.
For an active harmful conversation, leave first and use the available report or block controls. A public contact page is not an emergency channel and should not delay a safety action.
For a payment problem, keep the order identifier, timestamp, displayed currency, amount and real result state. Do not send passwords, one-time codes or full card details.
Include the page URL, the sentence or fact at issue, the date observed and a source that supports the correction. A screenshot can help when it does not expose another participant or private account data.
Substantive corrections change the reviewed date. Style preferences may be considered without being recorded as factual corrections.
A working support address is not yet listed here. Do not send a request to a guessed mailbox: without a verified destination, there is no reliable way to know whether anybody will receive it.
No public email address is available here at present. An address belonging to another brand is not a substitute, and we cannot promise a reply time through a contact route that has not been confirmed.
If you cannot close a conversation, close the browser tab and check the device’s camera indicator; do not wait for an email reply. If a payment appears twice, keep the two transaction references and contact the payment provider through its known app or website. This page does not submit either request for you.
For an article correction, keep the page address and the sentence you want checked. There is no working submission form here yet. Avoid posting private account details in a public comment or sending them to a guessed address while a verified support channel is unavailable. A prepared note can wait; an immediate safety concern should not.
A live safety problem, an account-access problem, a payment question, a privacy request and an editorial correction need different evidence and may be handled by different controls. Start by naming the outcome you need. “Something went wrong” is understandable, but the next useful detail is whether exposure is continuing, money moved, an account is locked or a public statement is inaccurate.
If a harmful call is active, end it before preparing a message. If an account may be compromised, secure the relevant login through its official route. Contact becomes useful after the immediate risk is contained. A public mailbox should not be treated as an emergency service or as a substitute for a bank, browser vendor or appropriate local authority.
Include the device type, operating system, browser, selected mode and whether a local camera preview appeared. Say whether the browser asked for permission, whether the operating system showed an activity indicator and whether another app was using the same hardware. These facts separate a permission failure from a network or remote-media problem.
Do not send a participant image to demonstrate that the screen was blank. A written state is usually enough: local preview worked, matching began, remote video never appeared, or the call ended after a named action. Try one change at a time and record what changed. A list of ten simultaneous resets makes the result harder to reproduce.
A useful payment report includes the order or receipt reference, displayed currency, amount, approximate time, account identifier and the final state shown by the product. Explain whether the balance changed and whether a bank or wallet shows the transaction as pending, completed, reversed or duplicated. Screenshots should be cropped to remove unrelated financial information.
Never send a full card number, security code, password, one-time code or complete bank statement. WhoCam cannot settle a charge through a participant and a participant cannot sell an official recharge. If the question concerns a bank-side authorisation or chargeback, contact the financial provider through a channel you independently verify.
Use the in-product report or block control when it is available because the product may attach account and session context that a general message cannot recreate. Choose the closest conduct category and describe what was requested or shown without adding guesses about the person’s identity, nationality or motive.
Record the approximate time, account identifier and exact threat or request when it is safe to do so. Do not remain connected to obtain a clearer image, and do not redistribute private or intimate material as proof. If there is immediate danger, extortion, suspected exploitation or financial loss, the appropriate specialist, financial provider or local authority may need to act alongside the product report.
State whether the request concerns access, correction, deletion, objection, permission, a marketing preference or an explanation of processing. Include the account identifier and country or region needed to route the request, but do not attach identity documents until a verified process specifically requires them and explains how they will be handled.
Removing browser camera permission is different from deleting an account, and ending a call is different from removing stored transaction records. Name the layer you mean. The current privacy policy, product controls and verified support route remain the authority for available rights, identity checks and response periods; this page does not invent a universal deadline.
Provide the page address, heading, disputed sentence, date observed and the strongest source you have. Explain whether the issue is a factual error, outdated product behaviour, broken link, translation problem or unclear wording. A focused correction can be checked faster than a general statement that an article feels wrong.
WhoCam distinguishes material corrections from style changes. A material change to price interpretation, safety guidance, product behaviour or a comparison result should update the review record. Suggestions about tone and readability are still useful, but they do not need to be presented as evidence of factual error.
Publishing an address means the team has confirmed that a message can be sent, received and routed. It does not by itself promise round-the-clock staffing, a fixed response time or a particular resolution. Those commitments should appear only when operations can consistently meet them.
Until a contact route is verified, do not send private information to an address guessed from the domain. Prepare only the details relevant to the problem and keep the note on a device you control. This page can help you organise a request, but it cannot deliver one or confirm that anyone has read it.
Draft a short timeline in a private note: what page or call state you were in, what you expected, what happened, and what result you need. Remove passwords, full payment credentials, unrelated conversations and participant media. A clear copy reduces repeated explanation while keeping unnecessary personal information out of the message.
Send the request only through the verified route once it is published. Do not trust a support address supplied by another participant or an unsolicited direct message that claims it can restore balance, remove a report or guarantee a match.
It will be published only after the whocam.live support route is active and tested.