Security
What we have in place today (✓) and what's planned (○). Updated November 16, 2026.
Sign-in and accounts
- ✓Every user signs in with a password and an authenticator-app code (MFA), managed by AWS Cognito
- ✓Passwords of at least 12 characters; email verified at sign-up
- ✓Each sign-up gets its own new firm; nobody joins an existing firm without an invite
- ✓Only owners and accountants can invite people
Keeping each firm's data separate
- ✓Row-level security in the database: a user can only read and write their own firm's data
- ✓Every request runs under a restricted database role, so those rules always apply
- ○Separate database login for the app, not the admin account
- ○Automated test that tries to read another firm's data and must fail
Database (AWS RDS Postgres)
- ✓Encrypted at rest with our own AWS KMS key
- ✓Daily backups with point-in-time recovery (7 days) and deletion protection
- ✓Encrypted connections only, with certificate verification
- ✓Network access limited to the app servers and approved admin addresses
- ○First backup restore test
Files (AWS S3)
- ✓Private bucket, encrypted with KMS, HTTPS only, versioned (earlier versions kept 90 days)
- ✓Uploads and downloads use short-lived signed links, stored per firm
Secrets and encryption keys
- ✓Database login and Plaid keys stored in AWS Secrets Manager
- ✓Encryption key rotates every year
- ✓Each Plaid access token is encrypted with KMS and tied to its own client
- ○App's AWS access key limited to what it needs, rotated every 90 days, with alerts on unexpected use
Cloud account (AWS)
- ✓Root login has MFA and isn't used day to day; admins use single sign-on with MFA
- ✓Every action in the account recorded in CloudTrail, with log integrity checks
- ✓Budget alerts
- ○Threat detection (GuardDuty) and configuration checks (Security Hub)
Plaid and bank data
- ✓Bank connections through Plaid Link; Countful never sees anyone's bank login
- ✓Transactions sync from Plaid into encrypted storage
- ✓Before Plaid Link opens, you see and agree to what's shared and what it's used for
- ✓Disconnecting a bank ends Countful's access at Plaid right away
- ✓Written information security, access control, and data retention and disposal policies
- ○MFA on every admin console (hosting, Plaid, email, domain)
Privacy and deletion
- ✓Privacy policy and terms of service; everyone agrees to them before using the app, and again when they change
- ✓A firm owner can delete a client: bank access revoked, then every file version and record deleted
- ✓Deletion requests completed within 30 days; database backups expire within 7 days
- ✓We never sell your data
AI and prompt injection
- ✓The AI proposes fixes; nothing changes in the books until a person approves it
- ✓The AI never sees passwords, bank logins or access tokens
- ○Text from bank feeds, statements and uploaded files is treated as data, never as instructions to the AI
- ○The AI's tools run with the signed-in user's permissions, limited to their own firm's data
- ○No AI tool can send data outside Countful (email, web requests) without a person approving it
- ○AI replies shown as plain text: no auto-loaded images or links that could leak data
- ○Every AI tool call logged for review
- ○Prompt-injection test cases run before each release
Website and network (Cloudflare)
- ○Minimum TLS 1.2 and HSTS enforced at the edge
- ○Web application firewall and DDoS protection
Development and operations
- ✓Private code repository; versioned database migrations; security checklist before each release
- ✓Monthly dependency vulnerability scan
- ✓Incident response plan, risk register and vendor list
- ○Automatic dependency alerts (Dependabot)
- ○Confirm our AI provider doesn't retain or train on customer data
- ○Logs kept for at least 90 days
- ○Company laptops: disk encryption, screen lock and automatic updates
Questions, or need our information security policy? Email team@joincountful.com. See also our Privacy Policy and Terms of Service.