Connecting an assistant to a read-only view of your finances is a reasonable thing to do, provided you can answer four questions: who holds the connection, what exactly it can reach, whether it can change anything, and who is accountable if it goes wrong. Connecting an assistant to anything that can move money is a different decision entirely, and today almost nobody should be making it. The distinction is not a detail. It is the whole question.
The honest answer is “it depends what you mean by connect”
The question gets asked as though there is one thing called connecting your bank account to an assistant. There are at least three, and they carry completely different risks.
The first is pasting: you copy a statement, or export a CSV, and drop it into a chat window. No connection exists at all. The data is now in that conversation and wherever that provider stores conversations, and it goes stale the moment you paste it.
The second is reading: an assistant is given permissioned, read-only access to a live view of your financial data. It can see. It cannot touch. This is the arrangement most people mean, and it is the one this article is mostly about.
The third is acting: an assistant is given the ability to do things — move money between accounts, make payments, cancel a subscription, change a setting. This is the arrangement that sounds most useful in a demo and is the least defensible today.
Lumping these together produces bad decisions in both directions. People refuse a read-only connection because they picture an assistant with a debit card. Others enthusiastically hand over payment powers because they enjoyed a read-only experience. Separate them and the question becomes answerable.
Four questions to ask before you connect anything
These are the questions worth putting to any product that wants access to your financial life, whether or not an assistant is involved. If a provider cannot answer all four clearly and in public, that is itself the answer.
1. Who actually holds the bank connection?
There is a meaningful difference between an assistant that connects to your bank, and an assistant that connects to an app that connects to your bank. In the second arrangement, the bank connection stays where it already was, under existing regulated permissions, and the assistant only ever sees a downstream view. Your banking credentials are not in play, because they were never shared with anybody in the first place — UK Open Banking authenticates you at your own bank, not at the app.
Ask where the credentials live. The correct answer is “nowhere, because we never see them”.
2. What exactly can it reach?
“Your financial data” is not a specification. A good provider will list what is exposed, item by item, and the list should be shorter than everything. Categorised spending is different from raw transaction descriptions. A net worth total is different from your account numbers. A summary of your subscriptions is different from your card details.
Vague scope is a warning sign for a practical reason: you cannot consent to something you have not been told.
3. Can it change anything?
This is the question that separates the reasonable from the reckless. “Read-only” should mean that no capability to write, move, cancel or amend exists at all — not that such a capability exists and is switched off, and not that the assistant has been instructed not to use it.
The difference matters because instructions can be talked around and switches can be flipped. Absence cannot. Ask whether the mutating capability exists. If the answer is “it exists but is restricted”, you are relying on a policy. If the answer is “it does not exist”, you are relying on the shape of the thing.
4. Who is accountable when it goes wrong?
Nothing is risk-free, so the question is not whether something can go wrong but who answers for it. In the UK there is a concrete test: is the firm authorised by the Financial Conduct Authority, or an Appointed Representative of a firm that is? You can check on the FCA register in about a minute, and you should.
Regulation is not a guarantee of competence. What it gets you is specific and useful: rules about how financial data is handled, obligations under the Consumer Duty to act in your interests, and access to the Financial Ombudsman Service if a complaint cannot be resolved directly. An unregulated app may be perfectly well run, but if it goes wrong your options are commercial rather than regulatory.
What read-only actually guarantees — and what it does not
Read-only is worth a great deal, and it is oversold constantly. Being precise about it is more reassuring than overclaiming, because the claims are checkable.
| Read-only does guarantee | Read-only does not guarantee |
|---|---|
| No money can be moved by the assistant | That what the assistant tells you is correct |
| No payment can be created or authorised | That your conversation is private from the assistant’s provider |
| No account settings can be changed | That the data shown to you is complete |
| No subscription can be cancelled or started | That you should act on what it says |
| Nothing is written back to your bank | That the connection cannot be misused if your account is compromised |
The right-hand column is the one people skip. An assistant reading real numbers can still reason badly about them. It can misread a one-off transfer as recurring income, miss that a category is incomplete because an account is not connected, or produce a confident summary of a period it only partly has data for. Read-only protects your money from the assistant. It does not protect your decisions from a bad answer.
The practical consequence is that a read-only assistant is a good tool for orientation and a poor tool for irreversible decisions. Asking what you spent on eating out last month is exactly the sort of question it should handle. Asking whether to move your pension is not, and no amount of connection quality changes that.
For a read-only connection, the realistic risk is not theft. It is disclosure — your financial position now exists inside a conversation held by a third party — and misplaced confidence in an answer that sounds authoritative. Both are manageable. Neither is what most people picture when they imagine the danger, which tends to be an assistant emptying an account. That specific fear is the one thing a genuine read-only design does eliminate.
Why accountability matters more than assurances
Every provider says its product is secure. The claim carries no information, because no provider says the opposite. What carries information is the structure behind the claim.
Three things are worth more than a security page. The first is regulatory status you can verify independently, on a register the firm does not control. The second is an audit trail — a record of what was accessed and when, visible to you, so that “we would never” can be replaced by “here is what actually happened”. The third is revocation that you control, that takes effect immediately, and that does not require you to contact anybody.
Those three between them convert trust from a feeling into something closer to a check. You do not have to believe the provider; you can look.
Where earmarkIQ sits, stated plainly
We build one of these things, so the honest thing is to state our own position against the same four questions rather than write an apparently neutral article that happens to conclude in our favour.
- Who holds the connection? earmarkIQ does, through Open Banking provided by Finexer Ltd (FRN 925695), an FCA-authorised firm. The assistant never touches your bank and never sees your credentials, because earmarkIQ never sees them either.
- What can it reach? Your categorised earmarkIQ picture: accounts and balances, spending by category, subscriptions, net worth and property equity, and your payday allocation plan. That list is the whole list.
- Can it change anything? No. earmarkIQ Context is read-only by construction — no mutating capability exists in it, and a test in our build fails if one is ever added.
- Who is accountable? earmarkIQ Ltd, as an Appointed Representative of Finexer Ltd, which you can verify on the FCA register. Every access through Context is audited, and you can revoke it yourself at any moment.
What we do not do: earmarkIQ does not move money. No assistant connected through Context can initiate a payment, and no capability exists for it to do so. Payment initiation sits within the permissions earmarkIQ operates under and is on the roadmap, but it is switched off today. If it is ever turned on, it will be something you start and confirm yourself, payment by payment, with your bank authenticating you — never something an assistant decides to do. The distinction between showing and moving is worth reading in full, because it is the line that matters most.
So: should you?
If the connection is genuinely read-only, the scope is written down, the firm is on the FCA register, and you can revoke access yourself in seconds — then yes, connecting is a reasonable thing to do, and the main thing you are risking is that your financial position exists in one more place than it did before. Judge that against how much use you will get from it.
If any of those four is missing, or if the product can act rather than only read, the calculation changes and the burden of proof should sit with the provider. “Trust us” is not a security model, and enthusiasm about what an assistant could do for your money is not a reason to give it the ability to do it.
Frequently asked questions
About earmarkIQ
earmarkIQ is a UK personal finance app for iOS and the web. It is an FCA Appointed Representative of Finexer Ltd (FRN 925695) and ICO registered (CSN2001882). It connects to UK bank accounts through read-only Open Banking, categorises spending automatically, builds a payday allocation plan, and tracks subscriptions, property equity and net worth. Website: earmarkiq.app