Privacy

Reflects how PeerFlow actually works today, not boilerplate.

File transfer

Files never pass through a PeerFlow server. When you create or join a room, our signaling server relays only connection metadata — a room code, peer ids, and the SDP/ICE messages needed to set up a direct connection — between the two devices. Once that connection is established, files travel straight from one device to the other over an encrypted WebRTC DataChannel. We have no access to the files themselves, and nothing is written to disk on our end.

Room codes

Room codes are generated randomly, held in memory only, and expire automatically — typically within a few minutes if nobody joins. They are not linked to any account or identity.

Accounts

File transfer never needs an account. Chat and calls do: when you sign up we store your name, your email address and the list of contacts you have added. Your password never leaves your device — your browser sends a separately derived login secret, which we store only as a salted scrypt hash. We also store your public encryption key and your encryption keyring, sealed with a key derived from your password that we never have. Your email is used to sign you in and so that people who already know it can add you as a contact. We don't send marketing email.

Chat messages

Every message is end-to-end encrypted on your device (ECDH P-256 key agreement, AES-256-GCM) before it is sent. While you and a contact are both online it travels directly between your devices and never touches our servers. If your contact is offline, the encrypted message waits on the PeerFlow server — which cannot decrypt it — until it can be delivered, and is then deleted. Chat history is kept only on your own devices, encrypted with a key unlocked by your password; logging out locks it, and clearing site data (or closing a private window) deletes it from that device.

Calls and screen sharing

Voice, video and screen sharing are peer-to-peer WebRTC streams, encrypted end to end with DTLS-SRTP. Our server only relays the handshake that sets the call up, and that handshake is authenticated with both people's keys so the server cannot place itself in the middle. Calls and screen sessions never pass through a relay server. Calls are never recorded. Call history is stored encrypted on your device. PeerFlow in the browser can show a screen but cannot control another computer.

Signaling server logs

The signaling server keeps connection state (open rooms, connected peers, who is online) only in memory, and does not persist logs of who connected to or called whom. The only presence information stored is the “last seen” time your contacts see.

Cookies & tracking

PeerFlow does not use tracking cookies or third-party analytics on this site.

Changes to this page

As PeerFlow changes, this page will be updated to match — not the other way around.

Contact

Questions about this policy can be sent through ashwanitiwari.com.