Letting Claude read your spending directly can be more private than sending CSV files, provided you keep the scope read-only, ask narrow questions and disconnect afterwards. The data it reads still becomes part of a conversation with a third party, so decide what you are comfortable sharing first.
Privacy here is about three things: what is readable, what is retained, and how fast you can cut access.
How does a connector differ from a CSV for privacy?
| Point | CSV file | Connector |
|---|---|---|
| What is shared | Everything in the file | What the scope and your question allow |
| Copies left behind | Files in downloads and chats | No file; conversation only |
| Staleness | As of export | Live |
| Cutting access | Delete files and chats | Disconnect in the tracker |
The connector wins on copies and on narrowness, but only if you stay disciplined in what you ask.
What is the in-app AI doing?
Separate from any connector, SpendixAI categorises in stages: your rules, then your history and similar merchants, then only if AI is on an AI model using the normalised merchant name and an amount band, not your name, account numbers, full statement text or balances. You can switch AI off per feature or entirely. Optional features that read an unfamiliar statement layout process the uploaded document.
A narrow question versus a broad one
Say you want to know your 2026 spend on subscriptions. Broad: show me all my transactions this year. Narrow: what is my total for the Subscriptions category this year? If the year has 2,400 rows and the category has 30, the broad version exposes 2,400 rows to answer a question about 30.
Checklist before you connect
- Choose read-only. SpendixAI lets you choose a scope and disconnect any time.
- Decide which categories stay off-limits in your questions.
- Read the assistant provider's data terms.
- Confirm you know where the connections list is.
- Note how to export or delete data in the app if needed; owners can also schedule workspace deletion with a seven-day window to change their mind.
What should I keep out of scope?
Decide before you connect which rows you do not want discussed. For many people that includes medical bills, loan payments and transfers to family. You can ask for totals by category and skip the lists in those categories, or leave them out of the question entirely. The connector reads what your scope allows, so a narrower scope is the stronger protection than a promise to be careful.
- Medical and insurance rows.
- Loan and EMI payments.
- Family transfers.
- Anything involving other people's names.
How do I check that access is really gone?
Disconnect in the tracker, then open a fresh chat and ask for a figure only your data could provide, such as last month's total for a category. A properly disconnected assistant should say it cannot see your data. If it still answers, close the session, check the connections list again, and if it still looks wrong, contact the tracker's support before using the connection again.
It also helps to put a monthly reminder in your calendar. Privacy is not one decision; it is a small habit of looking at what is still open. Take two minutes on the same day each month to open the connections list, close what you do not need, and glance at the questions you asked recently to see whether any went further than necessary.
After the session
- Disconnect.
- Ask the same question again to confirm access is gone.
- Delete the chat if you do not need it.
- Repeat monthly if you keep a connection open.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

