Connecting an assistant to your finances moves a copy of whatever it reads into a conversation with a third party, so the privacy question is: what exactly will it be allowed to read, and who keeps that conversation. Choose the narrowest scope, ask narrow questions, and keep the ability to disconnect.
Notice that this is a different flow from the categorisation AI inside an expense app. Inside the app, SpendixAI sends only a normalised merchant name and an amount band, never your name, account numbers or balances. A connector you chose is you deliberately letting an assistant read your records, so it has its own rules.
What leaves your workspace, and what does not?
| Flow | What is shared | You control it by |
|---|---|---|
| In-app AI categorisation | normalised merchant name and amount band | switching AI off per feature, a monthly budget, or off entirely |
| Optional document reading | the uploaded statement itself | choosing not to use that feature |
| Assistant connected via MCP | whatever your chosen scope lets it read | scope, read-only start, disconnecting |
| Your bank login | never requested | not applicable |
Which questions are worth asking before connecting?
- What scope choices exist, and what does each allow?
- Can I begin read-only?
- Where do I see current connections, and can I disconnect each?
- Does the assistant provider keep or train on conversations? Read their terms, not the app's.
- Can I export or delete my data in the app if I change my mind?
For SpendixAI the answers are that you choose a scope, can start read-only and can disconnect any time. Records sit in your own workspace with role-based access, the product says it does not sell personal information, and owners can export data, choose document retention, delete transactions and schedule deletion of the whole workspace with a seven-day window to reverse it.
How much should I put in a chat?
Think data minimisation. If you only need a total for one category, ask for that, not a dump of every transaction. A rough illustration: a year of statements may hold 2,400 rows, while the answer you wanted is a single figure. Asking for the figure keeps 2,399 rows out of the conversation.
How do I check access later?
- Open the connections list and read what each connection can do.
- Disconnect any you no longer use.
- Ask the assistant a question about your data; confirm it cannot answer after you disconnect.
- Set a monthly reminder to repeat this.
What if I change my mind later?
Plan the exit before you enter. Disconnect the assistant first, then decide whether anything else needs removing. In the app you can delete individual transactions, which go to a recycle bin for 30 days, choose how long documents are retained, and as an owner schedule deletion of the whole workspace. The assistant provider keeps its own record of the chats, so delete those separately if you want them gone.
A useful habit is to write down, at the time you connect, the three things you would do to leave: disconnect, delete the chat, and export your data. If any of the three is unclear, pause before you proceed.
Doing this once, calmly, is far easier than working it out later while something feels wrong. It also tells you honestly whether the convenience is worth the trouble for your situation.
What we would not do
- Paste a bank login, OTP, PIN or card number into any chat.
- Grant write access just to see what happens.
- Connect on a shared or borrowed device.
- Assume the assistant provider handles your data like the app does.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

