Security
Read-only by design
Provider connections exist to read: bank activity, invoices, bills, payroll summaries. Midbench uses read-only scopes wherever the provider offers them, and it does not initiate payments or write back to your providers. The books are maintained from what the connections read.
Credential handling
- Credentials are entered on a dedicated capture page over TLS — never in chat, email, or a support ticket.
- They are encrypted immediately at capture and stored only as ciphertext.
- They are never displayed back to anyone — including Midbench operators.
- Revoking a connection stops reads immediately. You can revoke at Midbench or at the provider.
A tamper-evident record
- The books are an append-only journal: entries are never edited in place; corrections are new entries.
- The journal is hash-chained, and its anchors are written to write-once (WORM) storage.
- Each month closes into a seal; sealed statements re-read byte-identical afterward.
- Independent witnesses re-verify the record on a schedule: chain verification, anchor read-back, and attestation reproduction.
Infrastructure
Midbench runs on Amazon Web Services and ClickHouse Cloud, which process data on our behalf under their own security and confidentiality commitments. Data is encrypted in transit and at rest.
What we don't claim
Midbench is in early access, and this page lists only what is shipped. There is no SOC 2 report yet; if that changes, it will be stated here with the date.
Reporting
If you believe you've found a security issue, write to info@midbench.com. Reports are read by the people who can fix them.