Privacy is a boundary you can inspect.

What another participant can learn

A live call can expose a face, voice, surroundings, routine, language, time zone and details shared in conversation. A one-to-one layout limits the immediate room; it does not stop recognition, screenshots or a second device.

Treat the visible frame as publishable. If an object, person or location should remain private, remove it before the call rather than relying on a blur at the edge.

For readers in the UK, the UK video chat privacy guide connects these questions to local privacy resources and practical location clues. It does not imply that a country page limits who can appear in a call.

What the service may process

Account access, security, device operation, abuse prevention, purchases and customer support can involve different data. Device and browser information may be processed during sign-in and startup, separately from camera permission. The Canada video chat privacy guide adds local context; the privacy policy is where to check the stated purposes, retention and your available choices.

Some matching and call settings support capturing still images. A still image is not a continuous recording, but it can still reveal a face or surroundings. Do not assume that a two-person call or the absence of a Record button means no image can be collected. This overview does not establish which capture settings apply to your session or how long an image is retained.

Camera and microphone access can be allowed, denied or removed in browser settings. That controls future device access, not deletion of information already sent. Closing a page should release media tracks; an active indicator means you should check what still has access.

What WhoCam will not say without evidence

WhoCam will not claim end-to-end encryption, no recording, verified identity, zero retention or complete anonymity unless the current product and policy provide precise evidence for that exact statement.

When a policy or product state is unclear, the public page should narrow the claim or remain unpublished rather than filling the gap with reassuring language.

Separate permission from consent

Browser permission answers whether the site may use a camera or microphone. It does not give another participant permission to demand a wider view, personal information, a recording, or continued contact. Those decisions remain yours throughout the call.

Revoking site access after a session changes future device access. It does not withdraw something already shown to another person or automatically delete account and payment records, which is why pre-call choices still matter.

Separate what the participant sees from what the service processes

The remote participant can see and hear transmitted media plus any account details the interface displays. The service may process different information for account operation, security, payments and support. These audiences and purposes should not be collapsed into one vague statement about privacy.

This guide helps you think about what you reveal during a conversation. For information about data the service collects, why it uses it and how long it keeps it, read the current privacy policy. A private-looking call screen does not mean that no account or service records exist.

Treat the camera frame as combined information

A single object may seem harmless, but a face, voice, delivery label, transit card, window view and notification can combine into identity and location. Review the edges of the preview, silence sensitive notifications and keep documents outside the transmitted area before matching.

A virtual background can reduce room detail while leaving voice, movement and account links intact. It is a presentation tool, not a complete privacy boundary. If recognition would create serious harm, live stranger video may be the wrong format for that session.

Understand exactly what browser permission changes

Allowing camera or microphone lets the site request media from that device under browser and operating-system controls. Denying access prevents the intended live mode from using it. Revoking permission later changes future device access but does not recall media already shown.

Permission also does not determine retention of account or payment records. Those are policy and support questions. Use the camera help page for the technical control and the privacy notice for service data instead of expecting one switch to solve both.

Keep participant consent distinct from device permission

A browser Allow button does not give another person permission to demand a wider view, recording, document, social profile or continued contact. Human consent applies throughout the conversation and can change after media begins.

When a refusal is negotiated repeatedly, end the call. Do not treat previous disclosure as permission for the next request. WhoCam can keep Stop and reporting controls visible, but only the participant can decide which voluntary information to add.

Assume remote capture remains possible

Even without a visible recording feature, another person may use operating-system capture or a second camera. A product rule can prohibit conduct and a report route can respond afterwards, but the interface cannot guarantee that visible media never leaves the other screen.

Share according to the consequence of copying. Do not show identity documents, payment details, passwords, one-time codes or material that could create serious harm. If threatened with publication, stop contact rather than sending more or paying for a promise of deletion.

Reduce cross-platform linkage deliberately

An alias provides little separation when it matches a public username, portrait or biography. Avoid connecting a temporary WhoCam encounter to social accounts unless continuity is a deliberate choice. A move to another app can expose contacts, old posts and location patterns.

This is not a guarantee of anonymity. Face, voice, product account and operational data can remain identifying. The goal is to remove unnecessary links, state the remaining limits and let the user choose whether the live format fits the consequence.

Read payment privacy by relationship

A purchase connects your WhoCam account with a payment handled through the checkout provider. Read the provider name and privacy notice before continuing. The person in your call does not need your card details or a one-time code, and using an alias in conversation does not make the billing process anonymous.

Keep receipts private but retain the order identifier for support. On shared devices, do not save payment credentials and sign out after checking the balance. A transaction record and the video persona serve different purposes and should be explained separately.

Make a data request through a verified route

A formal access, correction or deletion request needs the current privacy contact and enough information to locate the relevant account. Do not send passwords, full card details or unrelated participant media. A public social post is not a substitute for an authenticated request.

The WhoCam support email is not yet confirmed as operational. Do not send identity documents or account details to an address guessed from the site name. Check the contact information in the current privacy notice before sending a request; this guide does not promise a response time or a particular outcome.

Use privacy settings before the next match, not after regret

Review display name, connected accounts, notification previews, camera frame and retained site permission before pressing Start. These are the privacy choices WhoCam can make visible at the moment they still reduce exposure. A footer policy link alone is not enough if the interface encourages disclosure first.

After a session, you can reduce what you reveal next time, but you cannot withdraw what another participant already saw. Before returning, check your camera frame and saved permissions again. If something felt too personal to share, choose a different setting or leave that detail out of the next conversation.

Make the choice while it can still matter.