security
Security at VitalSend.
Encryption is done in the browser. The decryption key never reaches the server. The file is destroyed after one download. These three pages document how.
Compliance
GDPR by design
GDPR governs the personal data a company holds. VitalSend holds almost none. Files are encrypted on your device before upload, so our servers never see their contents, and both the file and its transfer record are deleted after one download. The only personal data we keep is what your account and billing require: an email, payment references, usage counters. After a transfer completes there is no file left to leak or to be compelled to hand over.
Architecture
How encryption, key handling, and deletion work.
Plain-language description of the client-side encryption, the URL-fragment key, the upload and download paths, and the deletion guarantees.
Read the architecture →
Threat model
What VitalSend defends against — and what it does not.
Explicit assumptions, in-scope threats, out-of-scope threats, and the security goals the design is built to meet.
Read the threat model →
Irreversibility contract
What VitalSend will not do.
No memory, no recovery, no tracking, no reuse, no exceptions. A plain statement of the constraints behind the product.
Read the contract →
Source
Verify, don't trust
The end-to-end encryption core is open source: the exact code your browser runs, with a test suite of executable security claims, is published at github.com/vitalsend/crypto.
Disclosure
Report a vulnerability
To report a vulnerability, see our disclosure policy /security/disclosure/.