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.

Login

The current login screen is a placeholder used to build and test the dashboard layout: it stores only the email you type into your own browser's local storage, and never sends it anywhere. It does not create a real account. When real authentication ships, this page will be updated to describe exactly what account data is collected and why.

Signaling server logs

The signaling server keeps connection state (open rooms and connected peers) only in memory, for as long as a transfer session is active, and does not persist logs of who connected to whom.

Cookies & tracking

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

Changes to this page

As features like real authentication, chat, and calling are built, this page will be updated to match — not the other way around.

Contact

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