Why the governance terms matter before client data touches an AI tool
Before using an AI tool for client work, check the terms for the exact product and account: how it handles prompts and files, who can access them, when they are deleted and what happens if a supplier changes the service.
For professional-services teams, the contract and control pack should be reviewed before any live use. That means procurement, information security, practice leadership and the responsible client team need a shared view of the permitted use case, the data classes involved and the human review step before outputs reach a client file.
The safest answer is a terms checklist backed by operational controls
Before using a specific AI tool on client work, verify the data processing role, training rights, retention period, data location, sub-processors, access controls, audit logs, deletion rights, incident duties and exit process. Then match those terms to an internal policy that says what the tool may and may not touch.
Do not rely on a general privacy page alone. Ask for the product-tier terms that apply to the exact workspace, plan, region and feature your team will use. Consumer settings, API terms and enterprise controls can differ materially, even when the product name is the same.
Check where AI risk sits in your current workflows
The core data terms to verify
Start with the processing role. The supplier should state whether it acts as processor, controller or independent controller for each part of the service. If the answer changes between prompts, uploaded files, telemetry, support access and model-improvement data, record the difference rather than treating the tool as one simple bucket.
Ask separately about training, tuning, evaluation and service improvement for each data type. Reconcile the supplier's answer with the binding terms and available settings, recording unverifiable points instead of claiming that an account owner can test all provider-side reuse.
Check retention and deletion by data type. Meeting transcripts, uploaded documents, chat history, logs and generated outputs may each have different retention periods. The firm should know what is deleted, when it is deleted, whether backups are included and what happens when a user leaves or a matter closes.
Security, access and audit evidence
Check the access controls needed for the proposed client work, including available single sign-on, multi-factor authentication, permissions, workspace separation and controls for sharing, exports and public links. If the firm uses matter-level information barriers, check whether the tool supports them or whether the use case must be narrowed.
Decide which usage and review records the workflow needs: user, time, data class, matter or workflow, and reviewer. Check what the tool records and whether a manual register can fill any gaps without copying unnecessary client data. If the evidence remains insufficient for the proposed work, do not approve that use.
Inspect each assurance document for its type, issuer, scope, period, service boundary and exceptions. Compare that scope with the proposed product, region and hosting model, then assess subprocessors, support access and incident terms separately.
How to turn the review into a usable policy
Record the permitted-use decision and who approved it. Classify the tool by approved use cases, blocked data types, required review steps, record-keeping requirements and named owner. Make it clear when staff can use the tool, when they need approval and when a client-specific instruction overrides the default policy.
Check which obligations apply to the firm's jurisdiction, profession and use case. These may include confidentiality, privilege, UK GDPR, professional conduct and insurer terms; for relevant financial-services work, also check Consumer Duty and SM&CR responsibilities. Record the applicable requirements in the tool decision.
Keep AI governance current as tools and terms change
Implementation discipline after approval
Once the terms are acceptable, roll the tool out in stages. Start with low-risk workflows, approved templates and a review checklist. Capture exceptions, failed outputs, user questions and any client objections. This evidence tells you whether the policy works in practice and whether the tool should be expanded, restricted or retired.
Recheck terms when the supplier changes model providers, launches new default-on features, changes retention settings or introduces new integrations. Keep the decision's version history, owner and route for staff to raise questions alongside the supplier review.
Build a controlled AI implementation plan
Conclusion
The right test is whether the firm can explain and evidence what happened to client data throughout the tool lifecycle. If the contract, settings, logs and internal policy do not line up, keep the use case out of client work until the control gap is closed.
Need a controlled AI route for a regulated team?
For a proposed financial, insurance or advisory workflow, identify the exact tool terms, permitted data, access controls and reviewer before approving client use.