An app can get your transactions in three broad ways: by logging in as you and reading the screens (screen scraping), by receiving a limited view of your data through an approved connection (read-only access, often through an API), or by taking a file you download yourself. They differ mainly in what you hand over and how much you have to trust the app.
For most people, file import is the simplest to reason about, and consent-based read-only access can be reasonable when it is genuine and can be withdrawn. Login sharing is the one to avoid.
What does each method hand over?
| Aspect | Screen scraping | Read-only access | File import |
|---|---|---|---|
| What you provide | Your login, sometimes a code too | Approval of a data request | A statement file you chose |
| Who does the work | The app, acting as you | A provider that connects to the bank | You, once a month or so |
| Scope of access | Whatever the login allows | Limited to what you approved, if designed well | Only what is in the file |
| Can you withdraw it? | By changing credentials | Usually by cancelling the approval | Delete the file and the app's copy |
| Freshness | As frequent as the app logs in | Can be frequent | As recent as your last download |
What can go wrong with screen scraping?
The app holds your credentials, so a breach at the app is a breach of your bank access. The login is not limited to viewing, and code requests train you to enter codes in the wrong places. Banks commonly advise customers never to share these details, and your own bank's terms may say what happens if you do.
What can go wrong with read-only access?
- The word read-only is a promise from the provider. Check what data is requested, for how long and for what purpose.
- The provider holds a copy of your data, so you are trusting their security as well as the app's.
- Approvals that are broad or long-lived can be forgotten and left running.
- If the app also asks for your login or a code, it is not truly read-only.
What can go wrong with file import?
The main risks are about the file itself. It may sit in Downloads, email or chats after you finish, and a statement carries your name, address and account number. There is also a reading risk: the app can misread dates, amounts or merchants, especially with unusual layouts, so you need to review the rows.
Which is best for an ordinary user?
| If you are | Lean towards | Why |
|---|---|---|
| Cautious about leaks | File import | Nothing but a file leaves your hands, and you can trim dates |
| Want near-live data and understand consent | Read-only access, if genuine and revocable | You can approve and cancel; check the provider |
| Offered an app that wants your login | Say no | It acts as you, and the risk grows with every extra permission |
Where does SpendixAI sit?
SpendixAI uses file import. You upload bank or card statements as PDF, CSV or Excel, and it has no bank connection, asks for no net-banking logins and does not read SMS. The cost is that new transactions appear when you upload, not in real time.
Whichever route you pick, the habits around it matter as much as the method. Use a strong, unique login for your bank, keep your phone updated, and treat any prompt that asks for more than a document or a limited approval as a reason to stop and read.
Questions to ask any app
- Do you ask for my bank login or any one-time code?
- Is the access limited to viewing, and can I see and cancel it?
- Who stores my data, and for how long?
- Can I delete everything, and how?
- What happens to the copy if I stop using the app?
Useful ideas start with a clearer picture of your own spending.
Explore your reports
