Back to Home

    Security

    Last updated: 17 August 2026

    You're handing us a credit card statement, so it's fair to ask what happens to it. Here's the plain version — only what we actually do, with no badges or certifications we haven't earned.

    What we never ask for

    • No bank logins. We don't connect to your bank and never see your online banking credentials.
    • No card numbers you type in. Whatever appears on the statement PDF is what we read — nothing more.
    • No payment details. The app is free; there's nothing to charge.

    Who can see your data

    Every table that holds your data has row-level security switched on, with rules tied to your account id. A request carrying someone else's session simply returns nothing — the filter runs in the database, not in the app code, so a bug in the interface can't leak rows.

    Uploaded files sit in a private bucket. There are no public links. When you open a statement, the app mints a signed link that expires in minutes.

    Encryption

    Traffic between your browser and our servers is encrypted with TLS. Data at rest — the database and the file storage — is encrypted by the hosting platform.

    We don't do end-to-end encryption of transaction fields, and we won't claim otherwise. The server has to read your transactions to categorize them, total them, search them, and apply your rules. Encrypting those fields so only your browser could read them would break every one of those features.

    What the AI sees

    To categorize transactions we send the transaction text — merchant description, date, amount — to a model provider. Your name, email, and account id aren't part of that request. Statement files are parsed and the extracted raw text is discarded once transactions are written.

    Your data isn't used to train models. If you turn on crowd categorization in settings, only the normalized merchant name and the category are shared — never amounts, dates, or anything tied to you. It's off unless you switch it on.

    Sessions and passwords

    • New passwords are checked against known-breached password lists at sign-up.
    • Signing in ends your other sessions, so an old device stops working.
    • The app signs you out after a period of inactivity — you choose how long in settings.
    • Signing out wipes the cached copy of your financial data from the browser.

    Keeping and deleting

    Your statements and transactions stay until you remove them. You can set uploads to be deleted right after processing, and original files are cleaned up automatically after six months either way.

    You can export everything and delete your account yourself from Settings. Deletion removes your files, every row of your data, and the account itself. It can't be undone and it doesn't go through a queue.

    What we haven't done

    We're not SOC 2 certified, not ISO 27001 certified, and haven't had an external penetration test. When that changes, this page changes. Until then, judge us on what's above.

    Reporting a problem

    Found something that looks wrong? Email security@bimuna.com with the details and steps to reproduce. We'll reply. Please don't test against other people's accounts.

    For what we collect and your rights over it, see the Privacy Policy.