Direct when possible
Media travels directly between participants whenever a direct WebRTC connection can be established.
Privacy-first conversations
Start a free room in your browser. No account, no download, and no call recording by PrivateCall.
Encrypted WebRTC media
Less data. More conversation.
Media travels directly between participants whenever a direct WebRTC connection can be established.
PrivateCall does not record or view your call content. Your room exists for the conversation, not for a profile.
Create a code, share the clean link, and talk. There is no account form, installation, or payment step.
Clear technical privacy
Your encrypted media goes directly between participants whenever a direct WebRTC connection is available. When a network prevents that, a TURN relay may forward encrypted WebRTC media packets. The relay cannot decrypt or view the media or call content.
We use the minimum signaling information needed to connect a room. PrivateCall does not record or view call content.
Read the plain-language privacy detailsThree simple steps
Open a private room with one click.
Send the room link or short code.
Allow camera and microphone access, then join.
Free for people
PrivateCall is free. Future company sponsorship may support the service through clearly labeled, contextual placements on the landing page or room lobby. There is no behavioral advertising, no third-party trackers, and no sponsor inside an active meeting. We do not use call content for advertising. We never sell call content or participant data.
Questions, answered plainly
Yes. Create, share, and join rooms without a subscription, card, or account.
A TURN relay can forward encrypted WebRTC media packets between participants. Relaying does not give PrivateCall the ability to decrypt or view the media.
No. A website cannot prevent operating-system screenshots, browser capture, or somebody filming a display. A dynamic session watermark helps deter capture and make a leak attributable. It does not contain or use personal information or PII.
Camera preview
Plain-language policy
This page explains what the service does, what it does not do, and where browser technology has real limits.
Encrypted media travels directly between participants whenever a direct WebRTC connection can be established. Some networks require a TURN relay. In that case, the relay forwards encrypted WebRTC media packets, but it cannot decrypt or view the media or call content.
The service uses the minimum connection and signaling information needed to establish a call and put participants in the correct room. PrivateCall does not record or view call content. We do not ask for an account, phone number, or real name.
While a room is active, temporary room and signaling state is held in server memory so participants can find one another and negotiate the connection. The infrastructure also necessarily processes IP addresses and basic request and security metadata to route traffic, protect the service, and operate it reliably.
If you choose a display name, it is stored locally in your browser for convenience. You can use a nickname; PrivateCall does not require a real name.
A website cannot prevent operating-system screenshots, browser capture, or someone filming a screen. The active meeting uses a dynamic session watermark to deter unauthorized capture and make a leak attributable. The watermark does not contain or use personal data or PII; it displays a random session-specific identifier and the current UTC time.
Standard campaign parameters may be kept only in your browser session so PrivateCall can preserve the inbound context while you navigate. They are not added to room invitation links.
PrivateCall may use future company sponsorship that is contextual and privacy-respecting. There is no behavioral advertising, no third-party trackers, and no sponsor in an active call or meeting. We do not use call content for advertising. We never sell call content or participant data.