Privacy

• The file itself — not a copy, not a cached piece, not a temporary one.
• The file name, its size, or its type.
• The key in your share link, which stays in the part of the URL browsers never send.

File names travel directly between the two devices so the recipient knows what they are accepting. That exchange happens over the connection between you, not through us.

• A random session ID, which is what identifies the transfer.
• The network details the two browsers exchange to find each other.
• Whether each side is currently connected.
• A one-way fingerprint of each access key — enough to check a key is valid, not enough to reconstruct it.

All of this lives in memory and is deleted when the transfer ends or the session expires. There is no database. Nothing survives a server restart.

There is no sign-up, so there is no email address, no password and no profile. We do not set advertising or analytics cookies, and there is no third-party tracking on these pages.

Ordinary server logs record that a session was created and that peers connected, along with the session ID and timestamps. Access keys are never written to logs. Your IP address is visible to our server while you are connected to it, as it is to any website you visit.

Your IP address is also visible to the person you are transferring with. That is inherent to a direct connection — the two devices have to know where to find each other. If that matters for who you are sending to, it is worth knowing before you start.

A link that nobody opens stops working after ten minutes. Once a transfer is under way the session stays alive while data moves, and is destroyed when it finishes. An expired link cannot be revived.