A budget question is one of the lowest-risk things to ask an assistant, because it can be answered from totals rather than individual transactions. The privacy-minded way to do it is to ask for category totals first, use read-only access, avoid asking for merchant detail unless you need it, and disconnect afterwards. You will usually get what you want without exposing a line of your spending history.
Why budget questions are gentler than other questions
'How much have I spent on groceries?' needs one number. 'Which shops did I visit?' needs a list. SpendixAI lets Claude or ChatGPT connect through MCP, you choose the scope, you can begin read-only, and you can disconnect whenever you want. A budget conversation fits in the narrowest scope, so choose that.
Three tiers of question
| Tier | Example | Detail the assistant needs |
|---|---|---|
| 1: Totals | How much of my November budget is left? | Budget and spent figures |
| 2: By category | Which categories are over pace? | Category totals |
| 3: Rows | What made up my eating-out total? | Individual transactions |
Stay on the first two tiers as long as they answer you. Go to the third only when a total puzzles you.
A worked example
Say your monthly budget is ₹30,000 and you have spent ₹12,600. A tier-one question gives you ₹12,600 of ₹30,000, which is 42 percent (12,600 divided by 30,000). If it is the 12th, about 40 percent of a 30-day month has passed, so you are slightly ahead of pace and a little careful is enough. You did not need any merchant names to know that.
What the in-app AI sees is a different matter
Categorisation runs in stages: your own rules, then your history and similar merchants, and only if AI is on, an AI model for what is left. That model receives the normalised merchant name and an amount band, not your name, account numbers, full statement text or balances. You can switch AI off for a feature, set a monthly AI budget, or turn it off entirely, in which case unmatched items are held for review. Optional features such as reading an unfamiliar statement layout do process the uploaded document.
A tidy way to do it
- Decide your question before connecting.
- Connect with the narrowest scope, read-only.
- Ask for totals first.
- Close the chat and disconnect.
- Note the date you connected and disconnected.
What to keep off the table
- Bank logins and card details. The app does not ask for them and no budget question needs them.
- Pasting statements into a chat. Use the scoped connection instead.
- Leaving the assistant connected on a shared device.
What a run of budget questions reveals
Even summary questions can paint a picture over time. Asking every week about 'eating out' and 'medical' says something about your life to anyone who can read that conversation. If that matters, ask less often, or ask only about the overall remaining budget. You can run the routine check yourself in the app's dashboard and insights, which need no assistant at all, and keep the assistant for the conversational questions, such as which category looks most worrying.
Exits if you change your mind
Owners can export data, choose document retention, delete transactions (which sit in a recycle bin for 30 days) and schedule deletion of a whole workspace with a seven-day window to reconsider. We do not sell personal information. Check the assistant's own settings for what it keeps on its side.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

