Security and privacy: what we do with your data

What we never ask for

Home Budget Analytics works from statement files you upload yourself, so it doesn't need the keys to your bank.

• No bank connection. The app has no open-banking or aggregator integration, so there is no standing link to your accounts.
• No bank login, card number or PIN. You download a statement from your bank and upload the file; your bank credentials never reach us.
• No access to move money. The app only reads the transactions in the files you give it - it cannot pay, transfer or change anything at your bank.

What happens to your statement files

When you upload a statement, we read the transactions out of it and store those transactions in your account. By default, the original file is deleted from our server as soon as the import succeeds. If you prefer to keep the originals (for example to re-import later), there is a setting for that in Settings; you can also delete the stored files of past imports there.

The one exception is a file we can't read yet. If an import fails and you choose to send the statement to us so we can add support for your bank, that file is kept until support for that format has been added, and it is opened only by the developer for that purpose. While such a request is open, you can't delete the file yourself, because we'd lose the sample we need to build the parser. If you'd rather not send a file, simply don't - nothing is sent unless you ask for it.

How your account and data are protected

• Passwords are stored hashed, never in plain text.
• Your data is private to your account. Every request is checked against the signed-in user, and asking for another user's record returns "not found".
• Signing out ends the session on the server, not just in your browser. Resetting your password signs out every other device and sends you an email saying your password was changed.
• Registration, sign-in, password reset and the contact form are protected by Google reCAPTCHA against automated abuse.
• The stored statement files are kept outside the public web root, and the web server is configured to refuse direct requests for application files.
• The site is served over HTTPS.

No AI reads your transactions

Categorization is rule-based: the first time a merchant appears you confirm a category, and that rule is applied from then on. Insights, recurring-payment detection and budgets are calculated with plain arithmetic on your own data. Your transactions are not sent to an AI service to categorize or summarize them.

Who processes what

What we don't claim

We are a small, independent product, not a bank. We don't hold a security certification such as SOC 2 or ISO 27001, and we don't want to imply otherwise. Our promise is the narrower one above: less data collected, original files removed by default, no bank access, no AI in the loop.

You can ask us to delete your account and everything in it at any time - there is no self-service button for it yet, so use the contact form and we'll do it. The full details are in the [privacy policy](/privacy).