Privacy & Security
Last reviewed: September 1, 2026
Bitment runs the sensitive parts of a CPA firm's business: client records, financial data, tax documents, and increasingly, AI agents that act on your firm's behalf. This page explains, in plain language, how we think about protecting that data. For the formal legal terms, see our Privacy Policy. For the full technical detail, see Compliance & Security.
Our principles
- Your firm gets its own isolated environment. We do not run one shared database for every firm on Bitment. Each paying firm gets its own dedicated infrastructure, described below.
- You choose which AI provider sees your data. Bitment does not force your data through a single AI vendor. You connect the provider you trust, and only that provider sees what you send it.
- Humans approve AI actions. When an AI agent wants to change your data, it proposes the action. A person on your team approves or rejects it before it happens.
- Connections are yours to revoke. Every integration, from Google to your bank, is something you turned on. You can turn it off, and disconnect and purge synced data, whenever you want.
- We do not sell your data, and we do not train AI models on it.
How your environment is built
Every paying firm runs on its own dedicated stack in AWS, not a shared multi-tenant pool.
| What | How it protects you |
|---|---|
| Private application server | Your app server has no public IP address. It cannot be reached directly from the internet. |
| Private database | Your database sits in a private network segment, unreachable from outside your stack. |
| Encryption at rest and in transit | Your database and file storage are encrypted at rest, and all traffic to and from Bitment is encrypted in transit. |
| Web Application Firewall and CDN | A firewall and content delivery network sit in front of your environment, filtering malicious traffic before it reaches your app server. |
| No inbound SSH | Bitment engineers never open a direct SSH port to your server. Access, when needed, goes through AWS's audited Session Manager. |
| Secrets Manager | Application credentials live in AWS's dedicated secrets service, not in configuration files. |
| Encrypted credential storage | Sensitive credentials your firm connects, such as OAuth tokens (and 2FA secrets once two-factor ships), get an additional layer of application-side encryption on top of the infrastructure encryption above. |
Bitment also runs one stack of the same design purely for its own internal testing. No customer firm is provisioned on it and it holds no customer data.
Who can see what
| Role | What they see |
|---|---|
| Firm owner | Full access to their firm's data and team management |
| Team members | Scoped by role and by any specific resource grants an owner or admin assigns |
| Clients (portal) | Only the files, signature requests, forms, and bookkeeping data your firm has explicitly shared with them |
| Operators working across multiple firms | See only the firms they actually belong to, resolved from their memberships each time, not from a single logged-in session |
| AI agents | Only what a proposal-and-approval flow lets them touch. Data-changing actions require a human to approve before they take effect |
| Bitment support engineers | Nothing, by default. Only if you personally opt in to Diagnostics can support view your workspace as you, and you can revoke that at any time |
AI and your data
- Bring your own provider. Your firm connects the credentials for the AI provider it wants: Anthropic, AWS Bedrock, OpenRouter, or your own self-hosted Ollama instance for firms that want to keep inference entirely on hardware they control.
- In-environment code execution. Where AI agents run code as part of a task, it runs in a sandboxed execution environment scoped to that task.
- A token ledger, for transparency. Every AI request records which model handled it and what it cost, so your firm can see exactly where AI usage and spend are going.
- No training on your data. Bitment does not use your conversations, files, or client data to train any AI model.
Integrations and consent
You choose what to connect, and nothing connects itself. When you link an account, whether it is Google, Microsoft, QuickBooks, or a bank through Plaid, you grant that specific connection and can revoke it at any time. Disconnecting an integration stops new data from syncing, and you can purge previously synced data for messaging integrations.
Signal and Telegram connections are review-before-sync: messages are staged for your review rather than flowing straight in, so you decide what becomes part of your firm's record.
Digital asset data
Bitment never holds, transfers, or controls your or your clients' funds or digital assets. All bank, exchange, wallet, Lightning, and payment-processor connections are read-only. Bitment never holds private keys, seed phrases, or spending credentials, and cannot initiate a transaction on your behalf. You give Bitment public addresses or extended public keys (xpubs), or connect your own node or exchange account, and Bitment reads balances and transaction history from that information. Payments on invoices you send are processed by the connected payment processor under its own terms.
Backups and resilience
- Your database is backed up automatically every day, with 7 days of backups available at any time.
- Your file storage volume is protected by a snapshot schedule.
What we log
Bitment keeps standard system logs (informational, warning, and error messages) to keep the platform running and to diagnose problems. Network-level flow logs are kept for 30 days. We do not currently maintain a complete audit trail of every individual data interaction; see the roadmap note below.
How to report a security issue
If you believe you have found a security vulnerability in Bitment, please report it to contact@bitment.co. We ask that you give us a reasonable opportunity to investigate and address any issue before public disclosure. We will not pursue legal action against researchers who act in good faith, avoid privacy violations and service disruption, and give us reasonable time to remediate, and we will acknowledge a report within 5 business days.
Roadmap: in progress
We would rather tell you where we are today than overstate it:
| Item | Status |
|---|---|
| SOC 2 | Audit in progress. The report will be available to customers on request once issued. |
| Full permission-change audit log | In progress. Today, Bitment records who granted each permission. A complete history of every permission change, viewable by firm owners, is on our roadmap. |
| Audit trail for support "view as" | In progress. Diagnostics access is opt-in and revocable today, but does not yet produce its own detailed audit log. |
We will update this page as these items move from "in progress" to complete.