Protecting IP, company data and the financials
There are four layers. The contract with the provider, the settings you choose, the access you grant, and the habits of your people. Most businesses have the first and none of the other three, and the IP leaks through the fourth.

What you're actually protecting
It helps to name it. For most B2B businesses the intellectual property is the pricing logic, the customer list, the designs or formulations, the method that makes you faster than competitors, and the proposals that carry it. The financials are the management accounts, margins by customer and job, payroll, and anything the board sees before the market does. Those are different things with different leak paths, and calling it all "security" hides that.
The four layers
The contract: a business or enterprise agreement with the provider, not a consumer account. There are five questions to put to any provider, and a lawyer should read the answers:
- Is our data used to train or improve your models? The answer has to be no.
- Who at your company can see our prompts and outputs, and when?
- Where is it stored, for how long, and can we set that?
- What happens when we leave: deletion, export, timescale?
- Which sub-processors handle it, and will you tell us if that changes?
The settings: training off, even if the contract says it already is. History retention set to the shortest period that works. Workspaces and licences owned by the company, so when someone leaves their account goes with them and the data stays with you. This takes an afternoon, and most businesses we see haven't done it.
The access: tools and agents read only the ring their job needs – the rings are in what data AI should see. The financials are restricted: no agent reads them, and a person uses an assistant on them only inside the company workspace, for a named task.
The habits: the one-page rule, shown to everyone on the staff and to every new starter. These things never go into a tool (customer personal data, payroll, anything under a non-disclosure agreement, source designs and formulations, passwords), and if you're not sure, ask this person. Plus a way to ask that's quicker than guessing.
The financials specifically
Your finance person wants to use an assistant on the management accounts, and should be able to. The conditions: the company workspace with training off, the file uploaded for the task and removed afterwards, the output read by the person before it goes anywhere, and no agent in the loop. What shouldn't happen is the board pack pasted into a personal account to "tidy the wording". That's the most common financial leak we've seen, and it's entirely a habit problem.
This isn't legal advice
The contract layer is one for your lawyer and, if you handle personal data in any volume, for whoever advises you on privacy law in your country. What we can say from experience is that the contract is usually fine and the other three layers are usually missing.