Security & Data Handling

Last updated: 24 July 2026

Bank statements are sensitive. This page explains, in plain terms, how ScanStatement handles your documents and data.

In-memory processing

Your PDF is received over an encrypted (TLS) connection, held in memory only while we process it, and never written to disk or stored in a database. It is discarded as soon as your result is returned.

What we store — metadata only

We keep summary metadata for your analysis history: bank name, the last four digits of the account, statement period, page and transaction counts, reconciliation status and timestamp.

We do not store the extracted transactions, and we never store the full account number — only its last four digits.

Encryption

Data is encrypted in transit with TLS. Data at rest (your account and metadata) is encrypted by our database and hosting providers.

Where your data goes

The uploaded PDF is sent to Mistral AI purely to perform OCR and structuring, and is not retained by us afterward. Account and metadata are held in Supabase; payments are processed by Stripe; the application is hosted on Vercel.

Access controls

Row-level security ensures you can only ever see your own account and analyses. Administrative credentials are held server-side only and are never exposed to the browser.

Your controls

You can delete individual analyses, close your account, or ask us to erase your data by emailing support@scanstatement.com.

Reporting a vulnerability

If you believe you have found a security issue, please email support@scanstatement.com so we can investigate promptly.