Can the server read my files?+
No. Files are encrypted in your browser with AES-256-GCM before upload. The decryption key is part of the link fragment (after the #), which browsers never send to the server. The server only stores encrypted blocks and does not know the file name, its type or its content.
Do I need an account to receive a file?+
No. Opening the link is enough: the file is downloaded, decrypted and verified in your browser.
How long are files kept?+
The sender chooses an expiry (from 1 hour to 7 days) and a number of allowed downloads. The encrypted data is erased as soon as the last download completes or the expiry passes, whichever comes first. The sender can also delete it at any time.
What does the optional password add?+
The password is combined with the key in the link (PBKDF2-SHA-512), so both are needed to decrypt. Share it through a different channel than the link. A wrong password is detected locally and does not use up a download.
How do I know the file was not tampered with?+
Each 4 MB block is sealed and numbered. Any modification, reordering or truncation makes decryption fail, and the download stops before anything corrupted is saved.
Who can send files?+
Invited accounts, protected by a password and mandatory two-factor authentication (TOTP), can send files and follow or delete them from the 'My transfers' page. Sending without an account may also be open, with smaller limits.