Security at Bizable

Bizable reads the records a business runs on, so it's built to read safely, act only when a person allows it, and keep a record of everything it does.

Your data

• Encrypted in transit: every connection to Bizable uses TLS 1.2 or higher, and our iPhone app pins the certificate authority it trusts.
• Encrypted at rest: databases, files and backups are encrypted. Secrets such as connection tokens are also encrypted with a key unique to each business, wrapped by AWS Key Management Service.
• Isolated by business: every business's records carry its own identifier, and the database itself (Postgres row-level security) refuses to return one business's rows to another, even if application code asks.
• Sensitive fields kept apart: payroll, personnel and private compliance details sit in separate storage with their own access rules. People who can't see an amount don't see it in a summary or notification either.
• Card numbers masked wherever text enters Bizable, including email and uploaded documents.
• Hosted in the United States on Amazon Web Services, with nightly encrypted backups and regular restore drills.

Bank connections

Bank and card accounts connect through Plaid. You sign in to your bank in Plaid's window, so Bizable never sees or stores your bank credentials. Bizable reads accounts, balances and transactions only, and can't initiate payments or transfers. Disconnecting stops access at once.

Control over what Bizable does

• Every action Bizable can take comes from a fixed, reviewed list. Actions it must never take, such as moving money, refunding or voiding payments, submitting payroll, deleting records or signing documents, aren't in the list at all.
• Each action is checked three times against your rules before it runs: when it's proposed, when it's approved, and just before it's sent, along with a check that the record hasn't changed in the meantime.
• Anything involving money always asks a person first. Agents earn the right to act on their own only after a long clean record, and that change needs a second person's confirmation.
• Any owner can stop an agent, an action or all of Bizable at once.

Accounts and access

• No passwords. Sign-in uses passkeys, Sign in with Apple or Google, or a one-time code.
• Sensitive changes ask you to confirm with your passkey or a fresh code.
• Roles decide what each person sees, down to the field.
• Bizable staff can't read a business's records unless the business turns on support access. Access to production is limited to a few people and every session is logged.

A record you can trust

Every business change is written to an audit log where each entry is linked to the one before it by a cryptographic hash. The chain is anchored nightly to storage that can't be altered for seven years, so any tampering would show.

AI and your data

Bizable uses Anthropic's models, which don't train on your data. Text from outside, like email and documents, is read as information, never as instructions, so a message can't tell Bizable to do something. Model-written text is checked against your records before you see it.

Reporting a vulnerability

If you think you've found a security issue, email security@bizable.ai. We'll reply within two business days and keep you updated while we fix it. Please don't access other people's data or disrupt the service while testing.