Trust & security
Bank statement data needs clear handling rules.
Bank2Excel is built for sensitive financial PDFs. The current product is early-stage, so we state exactly what exists today and what is on the compliance roadmap.
Encrypted storage
Uploaded PDFs are stored in a private Supabase Storage bucket and are not publicly accessible. Application access checks require the owner session or matching anonymous fingerprint.
AI processing disclosure
PDF contents may be sent to the configured AI extraction provider only to parse statement rows and balances. PDF passwords are used only for the current conversion request.
No model training
Bank2Excel does not use uploaded statements to train its own models. We also document the configured AI provider so customers can review that provider's data policy.
User-controlled deletion
Dashboard delete removes the stored PDF and cascades extracted transaction rows for that document. This is the default way to remove sensitive conversion artifacts.
Reconciliation checks
When opening and closing balances are available, Bank2Excel checks opening balance plus included transactions against the closing balance and flags mismatches before export.
Compliance roadmap
SOC 2, audit logs, IP allowlisting, and SSO are not claimed today. They belong on the roadmap once the product has enough B2B demand to justify the operational cost.