To disconnect Claude from an expense app, remove the connection in both places: in Claude's own connector or integration settings, and in the expense app's connection area. Then test it by asking Claude a question that needs your data. If access has really stopped, Claude should say it cannot see the information. With SpendixAI, you choose a scope when you connect, can begin read-only, and can disconnect at any time.
Menu names change from version to version, so look for the words connector, integration or MCP in each settings area rather than following a fixed path.
What does it mean to be connected?
SpendixAI lets Claude or ChatGPT connect through MCP, a standard way for an assistant to reach an app. When you connect, you pick a scope, which decides what the assistant may see or do, and you can start read-only. Disconnecting removes that permission going forward.
Disconnect in two places
- In Claude: open its settings, find the connectors or integrations list, find the expense app entry and remove or disable it.
- In your expense app: open the MCP or connected-assistants area and revoke the connection there too.
- Close and reopen the Claude chat, or start a new one.
- Test: ask for something only your data could answer, such as last month's grocery total. A correct answer means access is still live.
- If it is still live, repeat step 1 and 2 and check that you were in the right account.
Doing both sides matters. A connection removed only on one side may leave a stale entry on the other, which is harmless but confusing.
What happens to conversations I already had?
Disconnecting stops new access. It does not rewrite what was already said in earlier chats. Those conversations sit in your Claude history, which you manage in Claude's own settings, including deleting old chats. If a chat held something you would rather not keep, delete the chat there.
Special cases: accountant, privacy and small business
| Situation | Sensible setup | When to disconnect |
|---|---|---|
| Accountant helping you for a few weeks | Read-only scope, nothing that edits | On the last day of the engagement |
| Privacy-minded personal user | Connect only for a specific review, read-only | Right after the review |
| Small business owner | Connect on your own workspace, never share logins | When the person or tool no longer needs it |
Say your accountant needs three weeks, from 1 to 21 April, to review your spending. Put a reminder on 21 April to disconnect, and a second on 22 April to run the test question. That is two small calendar entries that remove a long-running permission.
What if I only want to limit it, not remove it?
- Change the scope to read-only if you started with more
- Connect only when you want a review, then disconnect
- Switch off AI categorisation in the app if your worry is about processing, which is a separate control from the assistant connection
- Export a CSV report and share that instead, if the person only needs figures
The AI and privacy page in the app explains how categorisation works and the controls you have, and it is separate from the assistant connection.
How often should I review who has access?
Treat connections like house keys. Once a quarter, open the connection lists in both places and ask whether each entry is still needed. Remove anything you do not recognise. A personal user who connects only for an occasional review will find the list is short and the habit takes two minutes. For a small business, add the same item to the monthly close checklist so it does not depend on anyone's memory.
A final check
- Connection removed in Claude
- Connection revoked in the expense app
- Test question fails as expected
- Reminder set to review again next month
- Old chats deleted if needed
Useful ideas start with a clearer picture of your own spending.
Explore your reports


