Security
Your clients’ statements, kept private.
A bank statement carries an account number, an address and a month of someone’s life. This page says where yours are stored, who can open them, and what we do not claim.
How documents arrive
- Upload the files
- Forward by email
- Client upload link
- Bank loginNever asked
No bank logins
You upload or forward the files. No credentials, no aggregator.
- harbour-checking-sep.pdfLarkspur Candle Co.
- Stored on
- Cloudflare R2, private
- At rest
- Encrypted
- Public links
- None
Private on Cloudflare R2
Private storage, encrypted at rest, with no public links.
Settings · Data
Delete after readingKeep the transactions, not the fileClear all dataDeleted when you say
Delete each document once it is read, or clear everything.
Saved credentials
- PDF passwordAES-256••••••••
- API keyHash onlybnfw_••••7f3a
AES-256 for credentials
PDF passwords and tokens are encrypted; API keys are kept as hashes.
Where your documents are stored
Every statement, receipt and invoice you upload or forward is stored in Cloudflare R2, in a private bucket under a path that belongs to your account. R2 encrypts every object at rest with AES-256. Nothing in that bucket has a public link: a document is read only by the app on behalf of the signed-in account that owns it.
Everything travels over TLS: uploads, forwarded email once it reaches us, exports and every page of the app. The application and its database run on Railway.
Who can open them
You, and the people you sign in as. Beyond that:
- Not our team. Our admin tools cannot open your documents or the text read from them. If we need to see a page to fix a problem you reported, we ask you to send it.
- AI providers, only to read the document. Google (Gemini) and OpenAI read the pages during processing, to extract the transactions you asked for. Bankflow does not use your documents to train models.
- Nobody else. We do not sell data, share it for advertising, or show it to other customers.
What is encrypted, and how
- In transit: TLS 1.2 or later on every connection.
- At rest: Cloudflare R2 encrypts stored documents with AES-256.
- Saved PDF passwords, and the tokens that connect Dropbox, Google Drive, OneDrive and Gmail, are encrypted again by Bankflow with AES-256-GCM before they are written, with a key kept apart from the database.
- API keys are stored only as SHA-256 hashes. We cannot read yours back; a lost key is replaced, not recovered.
How long we keep things, and deleting them
- Delete the original after processing. Turn this on in Settings and each source document is deleted as soon as its transactions are read. Otherwise it is kept until you delete the statement or the account, so you can open it again.
- The parser’s working text is removed after 30 days. Reading a statement leaves a plain-text copy for checking the result. It is deleted automatically, so there is no second copy of every statement sitting in the database.
- Delete on your terms. Settings has separate controls to delete stored documents, reset statements and transactions, or wipe your application data.
Sign-in and account protection
- Sign-in is handled by Clerk, with email codes or Google sign-in. Bankflow never sees or stores your password.
- Every request is checked against the signed-in account, and every query is scoped to it.
- Rate limits on every API route, and stricter ones on the expensive ones.
- Each export, whether a file, a full account download or an API export, is logged with who ran it and when.
- Card details go to Dodo Payments, which is PCI DSS Level 1. Bankflow never sees or stores a card number.
The providers we run on
Each of these is independently audited. The attestations are theirs, not ours: they cover the infrastructure your data sits on.
| Provider | What it does for Bankflow | Attestation |
|---|---|---|
| Cloudflare R2 | Stores uploaded documents; receives forwarded email | SOC 2 Type II, ISO 27001 |
| Railway | Runs the application servers and the database | SOC 2 Type II |
| Vercel | Serves the web app | SOC 2 Type II |
| Clerk | Sign-in and sessions | SOC 2 Type II |
| Google (Gemini) and OpenAI | Read documents during processing | SOC 2 Type II |
| Dodo Payments | Card payments | PCI DSS Level 1 |
The full list of service providers, including email, error monitoring and analytics, is in the Privacy Policy.
Where we are on SOC 2
Bankflow has not completed a SOC 2 audit of its own. We would rather say that than let a provider’s badge suggest otherwise. What we can offer today is this page, a published Data Processing Agreement, and straight answers to your firm’s security questionnaire.
Questions, and reporting a vulnerability
For a security review, a questionnaire or a question this page does not answer, write to security@bankflow.app. Report a vulnerability to the same address; we investigate every report and will tell you what we found.
Try it with one statement.
Upload a statement, check the result, and delete it from Settings when you are done.