PsiDriveUse the standard encrypted link through a private channel and rely on normal expiry.
Encryption protects the stored file. A password adds an access check.
PsiDrive uses client-side encryption for transfer contents and offers an optional password for additional authorization. These controls are related, but they are not interchangeable.
The practical difference.
| Control | Purpose | What the recipient needs |
|---|---|---|
| Browser encryption | Transforms the filename and file chunks into authenticated ciphertext before upload. | The complete transfer link containing the client-side key. |
| Optional transfer password | Adds an application authorization step before download. | The complete link and the separately communicated password. |
| Delete after first download | Limits reuse after one successfully finalized download. | Access before another recipient consumes the transfer. |
Why the complete link still matters.
The URL fragment carries the encryption key and is not normally included in HTTP requests. That separation keeps the backend from storing the transfer key, but it also makes the complete link sensitive. A password should not be treated as permission to post the link publicly.
For stronger separation, send the link and password through different private channels. Use a unique password that is not reused for an account or another transfer.
Which combination should you choose?
Add a unique transfer password and communicate it separately from the link.
Combine a private link, optional password, and delete-after-first-download.
No combination can protect plaintext on a sender or recipient device that is already compromised. Endpoint security and careful recipient verification still matter.