Sender browser
Creates an AES-256-GCM file key and encrypts file contents before upload.
Technical trust center
This page separates file-content privacy from metadata, explains the actual recovery path, names the infrastructure providers, and states the limits of browser encryption.
01 / Data flow
VaultDrop transports and stores the encrypted form. The sender and recipient devices handle plaintext.
Creates an AES-256-GCM file key and encrypts file contents before upload.
Authorises the request, manages multipart state, and issues time-limited object requests.
Stores encrypted file objects. Jurisdictional restriction applies to the object bucket.
Downloads encrypted bytes and opens the content locally with authorised key material.
Infrastructure reference: Cloudflare R2 jurisdictional restrictions
02 / Visibility
The table below is the practical boundary. It avoids treating file-content encryption as total anonymity.
| Data | VaultDrop access | Why |
|---|---|---|
| File contents | No plaintext access | Encrypted in the sender's browser before upload. |
| Decryption material | Wrapped key or URL fragment | Account file keys are wrapped. Anonymous transfer keys stay in the link fragment, which browsers do not send in HTTP requests. |
| File metadata | Visible to the service | Names, sizes, folder paths, and timestamps are used to operate the workspace and delivery flow. |
| Account identity | Visible to the service | Email, name, authentication state, subscription, and security events are processed for account operation. |
| Network metadata | Visible in limited logs | IP address, browser type, and access timestamps support security, abuse prevention, and audit trails. |
| Share password | Hashed | Password-protected share passwords are stored as a one-way bcrypt hash, not as plaintext. |
03 / Recovery
Registered files at or above 100 MiB use multipart upload. Recovery state remains in the browser for up to seven days.
session statusparts 1, 3 confirmedlocal matchname, size, modified timewrapped keyrestored after unlockupload queueparts 2, 4 onlycompleteone encrypted objectThis is a code-path test, not a claim that every browser, network, or 1 TB file has been certified. The public runbook lets a buyer repeat the interruption test with a real file.
Open the recovery proof and test runbookStorage primitive reference: Cloudflare multipart upload behavior
04 / Providers
No “zero subprocessors” promise. These providers perform specific operational functions.
Application execution, network delivery, security, D1 metadata, transactional account email, and R2 object storage
Encrypted file objects use an R2 bucket configured with the EU jurisdiction.Paid plan checkout, subscription management, invoices, and payment records
Stripe receives billing data, not file contents.Optional sign-in
Used only when a user chooses Google sign-in. VaultDrop does not request Drive, Gmail, or other Google content.05 / Limits
A useful security page includes the boundary conditions.
Malware, an unsafe browser extension, or a person with device access can see plaintext while the file is open.
Anyone who receives a complete non-password share link may possess the key fragment. Verify recipients and use a separate channel for sensitive access details.
Names, sizes, account information, and operational logs remain service data even when file contents are encrypted.
The browser runs code delivered by VaultDrop. This page does not claim an independent cryptographic audit or protection from malicious code served to the browser.
Test the workflow
Create a free workspace, use a representative file over 100 MiB, and follow the public recovery runbook before moving a real client delivery.