A video chat privacy checklist built for the minute before entry.
Privacy improves when checks happen before the camera opens. These twelve decisions cover what the other person sees, what the device shares and what you will do under pressure.
WHO CAM / WHOCAM.LIVEAbout this guideChecklistPractical guide
On this page
1
Frame and identity
Use a background without mail, certificates, family photographs, house numbers, workplace details or a readable window view. Choose a display name that is not reused across public social accounts.
Turn off notification previews and tell people nearby that the microphone may be live. Headphones reduce local spill but do not control the remote screen.
2
Permissions and capture risk
Confirm only the needed camera and microphone are enabled for the site. Close duplicate tabs and check the activity indicator after leaving.
Assume a remote participant could capture the screen with software or a second device. Do not show anything that would create serious harm if copied.
3
Links, payments and incident readiness
Do not open shortened links, download files, send verification codes or move money to prove trust. Read the current checkout before any product purchase and save the receipt.
Know where Stop, report and block are. If harm occurs, end exposure first and preserve only the minimum useful report details.
4
Shared devices need an extra pass
A browser profile can retain site permission, account state, autofill and recent pages after the camera is off. Sign out when the account is yours, remove permission you do not want retained, and close private material before another person uses the device.
Do not clear an entire shared browser without permission from its owner. Use the smallest change that protects your session, and prefer a personal browser profile next time.
5
Check 1–2: domain and browser profile
Confirm that the address is whocam.live before allowing media or entering account information. A similar-looking domain can present a different operator and policy. Open the site in a full supported browser rather than an embedded view with unclear permission controls.
Use a personal browser profile where possible. A shared profile may retain account state, autofill, permissions and recent pages. Private browsing changes some local history behaviour but does not make the device, network or service invisible.
6
Check 3–4: display name and connected identity
Use a display name that is not copied from a public social account when separation matters. Searchable reuse can connect a temporary call to photos, contacts, employer and location history even if the legal name never appears in WhoCam.
Review any connected account before entry. Google sign-in is an authentication route, not a promise that the next participant sees no identity information or that the service holds none. The current privacy policy controls formal data handling.
7
Check 5–6: camera edges and notification previews
Inspect the entire local preview, not only the face. Remove mail, badges, school or work material, readable windows and reflective surfaces. A virtual background can reduce room detail but may expose edges during movement.
Enable a focus or do-not-disturb mode that hides message, calendar and banking previews. A notification can reveal a real name or one-time code in a fraction of a second. Closing unrelated apps also reduces accidental screen and audio activity.
8
Check 7–8: people nearby and live location
Tell nearby people when camera and microphone are active and keep them outside the frame unless they agree to appear. Headphones stop the remote voice from filling the room; they do not prevent the microphone from transmitting local conversation.
Use broad location language. Avoid a current station, street, employer, school or repeated routine. The conversation rarely needs real-time precision, and a request for proof is a reason to disclose less rather than show the surroundings.
9
Check 9: camera and microphone permission
Allow only the devices needed for the selected mode and verify the correct inputs. Site permission and operating-system permission are separate layers. Close duplicate tabs and meeting apps before treating a busy camera as product failure.
Know how to revoke access later, while understanding its limit: permission removal changes future browser access. It does not withdraw media already shown or automatically delete account and transaction records.
10
Check 10: consequence of remote capture
Assume the other screen can be captured with software or a second device even if WhoCam displays no recording button. Do not show anything that would create serious harm if copied. A rule or report route cannot guarantee prevention.
If recognition itself creates unacceptable risk, choose another communication format or do not enter. A mask, blur or alias may reduce some clues without removing voice, room, account linkage and off-screen capture.
11
Check 11: links, codes and external payment
Decide in advance not to open unknown links, download files, provide one-time codes or move money for a participant. Find any legitimate service independently instead of using the supplied URL. A live face does not authenticate the request.
Official WhoCam purchases belong in current checkout with package, currency and total. Gift cards, transfers, cryptocurrency and mobile top-ups sent to another person are outside the product regardless of the explanation.
12
Check 12: exit, report and after-call state
Locate Stop, Next, report and block before matching. Stop ends the active route, Next handles an ordinary mismatch, and reporting addresses conduct. Harmful media should be ended before evidence gathering or explanation.
Afterwards, verify media indicators are off, close opened links and sign out on a shared device. Keep only the identifiers required for support or a report. A privacy checklist is complete when the session can also end cleanly.
13
Apply the checklist again when context changes
A safe setup on a personal laptop does not automatically carry to a work computer, public network or phone opened inside another app. Recheck domain, browser profile, permission and visible surroundings whenever device or location changes.
Do not turn completion into a permanent privacy score. The checklist reduces avoidable exposure for one session. Current product policy, participant behaviour and external capture remain outside a twelve-item guarantee.
14
Use the result to choose a mode, not force video
If several checks cannot be satisfied—recognisable workplace, no private audio space, managed camera or high consequence of capture—do not treat video as mandatory. Use text or audio when the current product offers them, or postpone the session.
The checklist exists to support a decision before media starts. It should not shame a visitor into accepting risk for the sake of completing a match. WhoCam’s live-video positioning remains honest when the guidance also explains when not to enable the camera.
Save the checklist as a repeatable routine, not a record of participants. It needs no face, username or screenshot. The useful output is a ready device and a clear decision about what this session may transmit.
Repeat it whenever the device or surroundings change.
Checklist
Twelve privacy checks
1Neutral background.
2Private notification previews.
3Unlinked display name.
4No live location or routine.
5Correct camera.
6Correct microphone.
7No duplicate media tabs.
8Screen-capture risk accepted.
9No unknown links or files.
10No codes or identity documents.
11Current checkout verified.
12Exit and report controls located.
Sources
Further reading from official sources
These references provide context, not an endorsement of WhoCam.
Questions
Before you enter
No. It reduces avoidable exposure but cannot control another participant or every platform process.
Avoid it when you want to reduce cross-platform identification.