SaaS contract of an AI tool: clauses to review before buying
SaaS contract of an AI tool: prepare the review of data, subprocessors, security, changes and reversibility before signing.
By Pablo Nastar

The « subscribe » button does not explain what happens to your data, which subprocessors are involved or how to recover your work on exit. The SaaS contract of an AI tool must be read from the intended use: uploaded documents, created accounts, connected systems and decisions supported by the output.
This article prepares the questions to pass to the competent functions. It does not give legal advice and does not replace reading the contract, the DPA, the security annexes and the service-specific terms.
Contents
- Describe the use before rereading the clauses
- Reconstruct the contractual chain
- Examine data, security and service evolution
- Prepare reversibility before signing
- Train users on what the contract authorises
- Frequently asked questions
Describe the use before rereading the clauses
A clause does not have the same scope depending on whether the tool rephrases a public text or accesses a client file. The review therefore begins with a factual usage sheet, not with an abstract list of legal keywords.
Map the flows
Note the data categories, their origin, the affected persons, the connected systems, the countries involved and the recipient of the output. Specify whether the vendor can use the inputs or interactions to improve the service. Also distinguish the free account tested by one person from the professional contract planned for the team.
The CNIL explains how to qualify the roles of data controller and processor. This qualification depends on the real purposes and means; the commercial name of the relationship is not enough.
Assign the questions
Procurement controls the commercial scope and the commitments. The DPO examines the processing of personal data. Security evaluates access to the information system and the technical measures. The business checks the functions, limits and consequences of an error. Legal counsel settles the contractual questions that go beyond the grid.
The guide on AI confidentiality helps prepare the data inventory. The article on choosing a pilot use case lets you reduce the scope before the negotiation.
Reconstruct the contractual chain
The main contract is only one piece. The terms of use, the DPA, the privacy policy, the security annex, the technical documentation and the list of subprocessors can carry different commitments.
Build a hierarchy of evidence
| Topic | Document to find | Question to have reviewed |
|---|---|---|
| Purchased service | order form and contract | functions, accounts, duration, support |
| Personal data | DPA and annexes | roles, instructions, assistance, final fate |
| Subprocessors | list and change procedure | location, notification, possible objection |
| Security | annex, certifications, documentation | measures, incidents, access, logs |
| Content | terms of use | rights over inputs and outputs, reuse |
| End of contract | reversibility clauses | export, deletion, deadline, cost |
The CNIL publishes examples of processing clauses. They are a working resource, not an automatic validation of a particular contract.
Capture the version examined
Keep the date, the URL or the file, the language and the version of the terms reviewed. An isolated screenshot of a marketing page does not replace the contractual document. If a policy can change unilaterally, ask how the organisation will be informed and what consequence that change will have on the service.
Examine data, security and service evolution
The review must cover what enters, what is kept, what can be reused and what leaves. A general promise of confidentiality does not answer these four questions.
Data and instructions
Check the purpose, the data categories, the duration, the processing locations and the requests of the affected persons. Ask whether the inputs, outputs or user feedback are used for training or improvement, and whether that behaviour depends on the plan or a setting.
Access and incidents
Examine the authentication, the roles, the logs, the administrator accounts and the incident procedure. The ANSSI recommends a risk-based approach for generative AI systems. Its guide addresses the security architecture, not the whole set of contractual and business obligations.
Change of service
A model, a connector or a policy can evolve during the subscription. The review must ask how changes are announced, whether the administrator can refuse them and when a new test is needed. A contract acceptable today does not authorise all future functions.
Explicit absence of client experience. Educasium does not claim to have negotiated these clauses for a client. The grid prepares a cross-disciplinary review; only the vendor's documents and the opinion of the competent people make it possible to conclude.
Prepare reversibility before signing
The exit must be designed while the organisation still holds negotiating power. Waiting for termination exposes you to discovering too late a closed format, a short deadline or an export cost.
Test export and deletion
Ask which objects are exportable: content, histories, configurations, logs and metadata. Test the format on a pilot account. Check the fate of backups and the proof of deletion, without promising an instant disappearance that the contract does not guarantee.
Step 1: list the assets. Identify what the team creates or configures in the service.
Step 2: define the export format. Check that it can be read without the subscription.
Step 3: assign the request. Name the person who triggers the export and checks its receipt.
Step 4: prepare continuity. Describe the temporary method without the tool.
Step 5: verify deletion. Pass the questions to the DPO and legal depending on the context.
Step 6: estimate the effort. Include the cleanup, the migration and the training on the new environment.
Examine operational lock-in
Contractual reversibility can remain unusable if the team does not document its procedures. Keep the important instructions, the decisions and the work templates in a controlled space. Avoid making a private conversation the only memory of the process.
Train users on what the contract authorises
A clause known only to procurement does not frame the daily action. Training translates the decisions into examples: which account to use, which data to exclude, where to check a setting and how to report a doubt.
Build a short usage sheet
The sheet mentions the authorised tasks, the forbidden inputs, the mandatory control, the help channel and the review date. It avoids summarising the contract as « secure tool », a phrase too vague to guide the user.
The prompt engineering training addresses the quality of instructions. It must be completed by the data and account rules: a good prompt sent into an unsuitable environment remains a bad use.
Limits and counter-cases
A certification does not necessarily cover your configuration or your use. A signed DPA does not guarantee business quality. A favourable clause does not prevent a human error. Finally, some risks cannot be reduced to an acceptable level: the right choice is then not to use the service for that task.
Frequently asked questions
Is a DPA always necessary?
The answer depends on the processing of personal data and the roles of the parties. Do not infer the absence of data from the mere fact that the content looks professional. A document can identify a person directly or indirectly. The DPO or the competent counsel must examine the real case.
Can you rely on a security certification?
A certification provides information about a scope and a period. Check that scope, the certified entity and the services covered. It replaces neither the analysis of the flow nor the configuration test. Ask for the elements needed for your own decision.
What should be checked about deletion?
Look for the deadline, the backups, the subprocessors and the proof provided. Distinguish deletion of the account, of the active content and of technical copies. Also check what the organisation must export before the operation. Have the clause reviewed if it stays ambiguous.
What to do if a clause is unclear?
Turn the ambiguity into a written question and assign it to the right contact. Do not interpret a marketing page as a commitment. If the answer does not allow a decision, limit the scope or suspend the purchase. Keep the answer with the version of the contract.
Have it reviewed before committing the organisation
The contract of an AI tool must tell the same use as the business sheet. If the data, the responsibilities or the output remain unknown, the purchase is not ready.
The introduction to AI and prompting training helps teams translate the framework into usage actions, without replacing legal advice. Training eligible for OPCO/FIF PL funding subject to conditions. Qualiopi-certified organisation. To define the programme, contact Educasium.