Controls
What is in place today.
Hosting
The application runs on Vercel. The database and file storage run on Supabase, on AWS. All data is processed and stored in the United States.
Encryption in transit
Every connection uses HTTPS. The app sends a Strict-Transport-Security header, so browsers will not connect over plain HTTP.
Encryption at rest
The database and file storage are encrypted at rest. Digital Safe contents and MFA secrets are encrypted again by the application with AES-256-GCM.
Passwords and payments
Passwords are stored only as salted one-way hashes. Card numbers go directly to Stripe and never reach Bancroft.
Backups
The database, stored documents and Digital Safe files are backed up regularly to separate private storage. Digital Safe files stay encrypted in backups.
Vendors
Every provider that handles personal data is on the subprocessor list, with its purpose and location.
Digital Safe encryption
Vault credentials and files use AES-256-GCM envelope encryption, with a separate key for each entry.
Multi-factor authentication
Accounts support authenticator-app codes and recovery codes. MFA is required for Bancroft administrator and attorney accounts, and firms on the Firm plan can require it for every member. MFA secrets are encrypted before storage.
Session revocation
Password resets and security-sensitive account changes trigger session revocation checks across devices.
Role-based access
Household access is checked against account roles, firm membership and advisor assignments.
Audit records
Account, document and administrative activity is recorded for review, and the audit records are designed to make alteration detectable.
Server-side document generation
Document assembly runs on the server. Access to generated documents is subject to account and household authorization checks.
Secure development
Changes are tested and dependencies are checked before release.