Not legal advice. Last updated 2026-11-07.
Encrypted upload
Your file is encrypted in your browser before upload (AES-256-GCM). We decrypt it only in memory to parse and automatically repair it. No person opens your statement — parsing and repairs are automated. We discard the decrypted file when the job finishes.
Additional engines and repairs
If we need additional engines to verify or repair a new layout, those checks are automated. If automatic repair runs, page images may be sent to a model provider; we prefer a zero-data-retention option. We do not use your statements to train a public dataset, and we do not have a person read them.
The sample button does not upload a file. It shows an illustrative example only.
Google sign-in
When you sign in with Google, we receive your Google account identifier and email address to create or bind your StmtReady account and keep a signed-in session (HttpOnly cookie). We do not receive or store a Google password.
API keys
If you create an API key on a batch plan, we store only a one-way hash of the key. The full key is shown once at creation time.
Contact messages
Messages you send through the contact form are stored so we can respond. You can also email us at [email protected].
Balance check
PASS only means opening + credits − debits matches closing within a small tolerance. It can miss offsetting errors and is not an audit.
Pricing
Everyday individual conversions are free. Batch and API use the $12/month or $120/year plan for 100 pages per month.
Contact: [email protected] · Contact form