Statemento
Home →Security
What we do to protect your data, what we don't yet have, and how to report a problem.
What we do
- PDFs aren't stored. A statement is read in memory during one request and discarded.
- Encrypted in transit. All traffic uses HTTPS, enforced with HSTS.
- No passwords to steal. Sign-in uses a one-time email code or Google. Card details are handled only by our payments partner.
- Everything has a limit. Pages per file, per day and per month, plus rate limits, bot checks and daily spending ceilings, so abuse can't run up unbounded cost or take the service down for others.
- Locked-down website. A strict content security policy, same-site checks on every form and API call, and signed, replay-protected payment events.
- Account data is isolated. Database rows are protected so one account can't read another's, and server keys never reach the browser.
- Exports are made safe for spreadsheets. Text that could run as a formula when opened in Excel is neutralised.
What we don't have yet
- No SOC 2 or ISO 27001 certification.
- No independent penetration test report yet.
- No private or self-hosted deployment. Statement text goes to a named AI provider; see sub-processors.
Report a vulnerability
Email support@statemento.app or use the Contact page with “Security” in the subject. Tell us what you found and how to reproduce it. We'll acknowledge it, keep you updated, and credit you if you like. Please don't access other people's data, disrupt the service, or run automated scans that load it heavily. Our security.txt has the same details.