Privacy by architecture
Your readable content stays on your devices.
file-sharer does not require an account, email address, or server password. Sharing is built around local browser storage and end-to-end encryption.
What stays on your devices
Your message history, readable content, and encryption keys are kept in the browser on your linked devices. Private device keys are never sent to the server; you can optionally export an encrypted recovery file. The app can keep local history available when the network is unavailable.
What the server receives
The service needs ciphertext, public device keys, authentication data, hashes, and delivery metadata to link devices and synchronise content. It does not receive your message or file plaintext as part of the normal sharing flow.
Retention
Messages and files are temporary transport data. Once active recipients acknowledge delivery, they are removed from the server; a scheduled cleanup also removes anything older than 24 hours.
Your control
- There is no account profile to complete or email identity to expose.
- You can leave a space from the app, which removes its local session, history and keys from that device.
- Protect the devices where your local history and keys live. Anyone with access to an unlocked device can access its local data.