How does Zero-Knowledge bank statement conversion work?

Unlike legacy cloud converters that upload your bank statements to external cloud servers, StatementToExcel compiles PDF parsing logic into client-side WebAssembly and Web Workers. The PDF bytes are read directly into your local browser RAM via HTML5 FileReader. Not a single row of transaction data, bank balance, or account number ever leaves your device.

How does StatementToExcel verify statement reconciliation math?

StatementToExcel implements double-entry verification math: Starting Balance + Total Inflows (Deposits) - Total Outflows (Withdrawals) == Statement Ending Balance. If any OCR misread or missing line causes a discrepancy, StatementToExcel highlights the exact row and displays the math variance in real-time.

What formats can I export to?

You can export in 1 click to: (1) QuickBooks Online 3-column CSV (Date formatted MM/DD/YYYY, Description, Amount), (2) Xero CSV (*Date, *Amount, Description, Reference), and (3) Universal Excel (.xlsx) featuring both formatted transaction ledger and an executive reconciliation summary tab.

Which banks are supported?

StatementToExcel supports statements from all major institutions including JPMorgan Chase, Bank of America, Wells Fargo, Citibank, Silicon Valley Bank, Mercury, Brex, Capital One, American Express, PNC, US Bank, Barclays, HSBC, and standard regional credit unions.

Is there a free trial?

Yes! You can convert up to 3 pages completely free without creating an account or entering a credit card. Authenticated users get 5 pages free every month. Paid plans start at $19/mo for 150 pages.

Back to Home

Cryptographic Zero-Knowledge Privacy Architecture

Privacy Policy

Last Updated: November 1, 2026 • Compliant with GDPR Article 25 & SOC2 Type II

100% In-Browser Isolation Guarantee

Your bank statements, transaction lines, payee descriptions, account numbers, and balances are never uploaded to any server, database, or cloud AI model. Text extraction, coordinate clustering, and spreadsheet generation occur exclusively inside your device's volatile RAM via WebAssembly.

1. Zero-Knowledge Document Architecture

When you drop or select a bank statement PDF in LedgerVault, our client-side WebAssembly parser extracts characters and 2D spatial coordinates directly from the in-memory array buffer. Once you close your browser tab, all financial records and PDF buffers are completely purged from volatile memory.

2. Information We Collect

Because statement processing happens 100% locally on your machine, our servers only collect the minimal information required to manage customer support and subscription quotas:

Account Identifiers: If you subscribe, we store your email address and authentication token.
Local Storage Quotas: We record anonymous page usage counts locally in your browser storage (`localStorage`) to enforce freemium quotas.
Payment Records: Payment processing is managed by our Merchant of Record, Paddle.com. We never store or view credit card numbers on our servers.

3. Payment Processing via Merchant of Record (Paddle)

Our order process is conducted by our online reseller and Merchant of Record, Paddle.com, who also handles order-related inquiries and returns. Paddle processes payment data in compliance with PCI-DSS Level 1 standards and applicable global data protection regulations.

4. Zero Third-Party Advertising Cookies

We do not sell user data, nor do we employ behavioral advertising trackers or third-party marketing pixels. Browser storage is used solely for remembering your dark/light theme choice and your local page conversion counts.

5. Contact Us

If you have any questions about this Privacy Policy or our client-side cryptographic security architecture, please contact our team at support@ledgervault.com.