One fact sits behind everything on this page: on the free and personal versions of ChatGPT, Copilot, Gemini and Claude, what your staff type in is used to train the AI - unless someone has switched that off. The switch starts in the "on" position on all four tools, and paying for a personal subscription does not move it.
We've published a three-part guidance series for businesses running Sage 200 that fixes this - menu by menu, question by question. Copies are free on request.
Written for finance teams, accounts staff and business owners - plain English throughout, no jargon, and every setting located menu by menu so you can hand a guide to your team and let them work through it.
ChatGPT, Copilot, Gemini and Claude, each taken in turn: what the plans cost, what each plan does with your data, where that data goes, and the exact settings to change. Ends with a five-minute action plan - four settings changes for anyone on a personal account, six steps for business owners.
Includes the point most businesses miss: if you already pay for Microsoft 365, your staff already have a protected version of Copilot at no extra cost.
Request this guideThe five questions we're asked most: Can I put company names and addresses into AI tools? Do I have to tell my customers? Do my terms need to change? What about analysing Sage data in Excel? Do I need a privacy policy? - answered plainly, with ready-made privacy-notice wording you can copy straight in.
Covers the complaints-handling duty in force since 19 June 2026, which applies to every UK business however small.
Request this guideAI has gone from answering questions to acting on your behalf - sending emails, updating files, even making purchases. Useful, and a genuinely different risk picture for anyone whose systems hold accounting data. What agents are, what can go wrong, and an action plan before you switch anything on.
Not written to discourage AI use - written so you go in with your eyes open.
Request this guideThe moment AI meets your Sage 200 estate - staff pasting ledger extracts into a chatbot, an agent connected to email and files, an analysis tool reading the database - the questions stop being theoretical.
We work on both sides of that line. We build AI products around Sage 200 for a living, so we know exactly what these tools can reach and what they should never touch - and our own product is built to the standards the guides describe: read-only access, data staying on your machine, nothing used to train AI models.
If you want help applying the guidance to your own setup - which plans your team should be on, which settings to lock down, whether an AI tool someone wants to adopt is safe around your accounts data - that conversation is free too.
One email, no obligation - tell us your company name and we'll send the series over. Guidance rather than legal advice, but it should leave you knowing exactly what to ask and what to put in place.