Safe is a thing you build in stages, not a verdict you take from a website. Start with a dummy-sized upload, watch how the app behaves, then widen only if it earns it. The stages below take a few evenings and cost nothing but patience.
Stage one: a single page
Pick the shortest slice of a statement you can: a week, or even a day. Say that week holds A$38 of coffee, A$126 of groceries and A$54 of fuel. That is A$218 in three lines. Upload only those rows, ideally from a CSV with the header cleaned. You are checking three things: did it read the rows right, did it ask for anything beyond a file, and what does it say about AI.
- Rows: dates, descriptions and amounts match the original.
- Access: no bank login requested, only a file you chose.
- AI: you can see whether it is on, and you can turn it off.
Stage two: a month, with a proper review
Now upload a full month for one account. Read every row before saving, because import screens usually let you edit first. Correct a few categories and see whether the app learns. Look for a duplicate warning by uploading an overlapping week, which tells you how it guards against double entries.
| Check | Pass looks like | Fail looks like |
|---|---|---|
| Overlap upload | Possible duplicates flagged | Rows quietly doubled |
| Correction | Fix reused next time | Same error returns |
| Failure message | Clear notice if import fails | Silent partial import |
Stage three: delete on purpose
Before trusting the app with a year, practise leaving. Delete the test transactions. See whether there is a recycle bin and for how long. Find the setting for document retention. Find out how to schedule deletion of the entire account, and whether a short waiting period protects you from a misclick.
What should I understand about AI sorting?
A cautious setup works in layers: your own rules, then history, then a model only for leftovers, sent as a cleaned merchant name and a rough amount range rather than your name, account number, balance or the full text. You should be able to switch it off, cap it, or let unmatched rows wait. Features that read an unfamiliar layout may process the whole document, so treat that as a separate choice.
Where does my own app fit in this comparison?
SpendixAI is built around India and INR, so it is not aimed at Australian accounts, but its stated design makes a reasonable measuring stick: statement files only, no banking logins, AI limited as described above, and owner-controlled export and deletion. Hold any app you consider to that bar.
How often should I revisit the settings?
Put a note in your calendar three months after you start. At that point, look at who has access, whether AI settings are still what you chose, and whether old uploaded documents are still being kept longer than you want. Apps change, and so do your habits. A ten-minute review each quarter keeps the arrangement honest, and it is also a good moment to delete anything you no longer need, since data you do not hold cannot be exposed.
When to widen the upload
- The week and month tests read correctly.
- You found the delete and export controls.
- You understand what the AI receives.
- You are comfortable with who can see the workspace.
- You keep originals of every statement yourself.
Bank terms and privacy protections vary, so read your own bank's terms about sharing statement data, and ask them if something is unclear.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


