Privacy Policy

File contents

The contents of transferred files never touch any server of ours. The transfer happens directly between the sender's browser and the receiver's browser, via WebRTC. We do not store, access, analyze, or hold any copy of what is transferred.

Signaling data

For two browsers to connect peer-to-peer, they must exchange technical connection metadata. This data temporarily sits in our Firestore (Firebase) during the session:

• SDP (Session Description Protocol) — describes the connection configuration.
• ICE candidates — possible network routes between the devices.
• callId — a short code identifying the session for the other side to join.

This data reveals nothing about the file contents. After the transfer (success or failure), the corresponding documents may be deleted — exact retention will be documented once the cleanup cycle is defined.

Accounts and signup

Senddfile requires no signup, login, or personal information. There are no user accounts, so no name, email, password, phone number, or profile is stored anywhere.

Cookies and analytics

We don't set tracking cookies. To understand — in aggregate — whether people use Senddfile and which transfers fail, we use Google Analytics in a cookieless mode: it stores no cookies and doesn't identify you, sending only anonymous, aggregated signals (page views, plus transfer events labelled with the role, a coarse file-size range, and an error code). We never send your file's name or content, the transfer code, or your IP tied to an identity. Local preferences (language, theme) may be saved in your browser's localStorage — that data never leaves your device.

Your rights

Since we don't store identifiable personal data, there's no user database to look up, change, or delete. If you identify any personal data of yours being handled in a way incompatible with this policy, please get in touch.

Contact

For privacy questions or about this policy, write to us at: