Before you pull a client's expense data into your own workflow, settle consent, the minimum data you need, how it travels, where it will sit and when it will be deleted. Technology comes last. With SpendixAI the practical route is an export made by the workspace owner, and the product lets owners export data, choose document retention and delete transactions. That puts the client in control, which is what a privacy-minded approach should do.
Do you need all of it?
Ask for the smallest set that does the job. If you only need categorised totals for a quarter, do not take every transaction with merchant names. If you need the ledger, take the ledger, but not receipts or documents unless you must verify something. The app keeps receipts with their transactions, so a transaction export does not have to include them.
The checklist, in order
- Consent. The client agrees in writing to what you will take, why and for how long.
- Minimum. List the columns and the period.
- Channel. Decide how the file travels, using a shared folder with named access rather than forwarding to many people.
- Storage. Decide where it sits and who on your team can open it.
- Retention. Write the deletion date in the register.
- Review. Check the list again at the end of the engagement.
What sits where
| Item | Where it lives | Who controls it |
|---|---|---|
| Original records | Client's workspace, with role-based access | The workspace owner |
| Export file | Wherever it was sent or saved | You, once received |
| Assistant chat | The assistant provider's service | Its own terms and settings |
| Your imported copy | Your accounting system | You |
The point of the table is the third row. If a client connects Claude or ChatGPT through MCP, what the assistant reads is handled by that provider. The app lets the client choose the scope, start read-only and disconnect at any time, but it cannot control the provider's side. Read those terms before suggesting it.
A worked example of data minimisation
Say a client has 1,680 transactions in the year and you only need to check a quarter's travel and software spend, which is 410 rows. Taking 410 rows rather than 1,680 means you hold about 24 percent of the data (410 divided by 1,680 is 0.244). The rest stays with the client. Fewer rows also means a smaller thing to protect and to delete.
What to ask the vendor
- Is there a documented interface for programmatic access, and what can it read?
- How are permissions scoped and revoked?
- What is the retention and deletion process?
- What does the vendor say about selling data? The vendor states that it does not sell personal information; read the current policy for yourself.
Deleting at the end
When the engagement ends, delete working copies according to the note you agreed, and record that you did. Deleted transactions in the app go to a recycle bin for 30 days, and owners can schedule deletion of a whole workspace with a seven-day window to change their mind.
Talking to clients about it
One clear sentence helps: 'I will ask you to export a file each month, keep it for this long, and open it only for these tasks. we will not ask for logins.' A client who understands the limits can agree to them knowingly, and you have a record of what you promised. Put the retention period in the same message so there is no argument later. If a client asks you to delete data earlier, do it and note the date.
Ready to proceed?
- Consent in writing.
- Columns and period listed.
- Channel and storage decided.
- Deletion date recorded.
- Vendor questions answered.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

