Security
Our intake architecture is intentionally designed around data minimization, segmented onboarding, least-privilege access, and auditable handling of taxpayer information.
Encryption at rest and in transit
All data encrypted with AES-256 at rest. TLS 1.3 in transit. Document uploads stored in encrypted S3-compatible storage.
OTP-verified access
Clients verify identity via one-time password before viewing engagement documents or uploading files. No shared passwords.
Role-based access control
Intake staff cannot view SSNs or documents. Preparers access only assigned clients. Admins control audit logs and retention.
Data minimization by design
Public intake forms cannot collect SSNs, DOBs, bank info, or tax documents. Sensitive data only enters the system after engagement.
Infrastructure security
Secrets managed through encrypted environment variables. Database access restricted to application layer. No direct database exposure.
Immutable audit logging
Every state-changing action is logged with timestamp, user, IP, and user agent. Logs cannot be deleted or modified.
Subprocessors
We use the following third-party services to operate the platform:
| Provider | Purpose | Data Accessed |
|---|---|---|
| Wasabi / MinIO | Document storage | Encrypted files only |
| Amazon SES | Email delivery | Email addresses, notification content (no PII) |
| Stripe | Billing | Firm billing information (no taxpayer data) |
| PostgreSQL (managed) | Database | All application data (encrypted at rest) |
| Redis (managed) | Job queues, sessions | Temporary session data only |
Questions about our security practices? security@auditable.tax