Security isn't just a feature at W9Vault — it's our foundation. We understand that accounting professionals handle some of the most sensitive financial information, so documents are encrypted in the browser before they ever leave it. This page describes what we do today.
Our Security Architecture
Client-Side Encryption
All documents are encrypted in the vendor's browser before upload using TweetNaCl XSalsa20-Poly1305 encryption
Each file gets its own unique encryption key generated with cryptographically secure random number generators
Our servers never receive the unencrypted file. Each file's key is protected by a separate key held on our servers, and only the requester can download the file
The file's encryption key is unwrapped only as part of the authorized upload and download flow
Transport & Storage Security
HTTPS (TLS) encryption for all data in transit
Database storage encrypted at rest by our database provider, Supabase
The key that protects file keys is stored as an encrypted server-side secret and is never sent to browsers
Automatic Data Deletion
All uploaded documents automatically deleted after 30 days (no exceptions)
Secure deletion using cryptographic erasure
No long-term document storage (by design)
Audit logs confirm successful deletion
Application Security
Access Controls
Passwords must be at least 8 characters
Sign-in and sessions are handled by Supabase Auth
Database row-level security: each account can see only its own requests and files