Essay 131
AI vendor terms: four clauses to check before you adopt a tool
2026-10-01
The demo shows what the tool can do; the terms show what the vendor may do, and customer data lives in the gap between them.
Adopting an AI tool takes an afternoon: card details, a workspace, the whole team invited by evening. The part that gets skipped is the subscription agreement, and it is the only part written by the other side. Inside it sit clauses that decide what happens to your material: the proposals you draft, the client documents you summarize, the history your team accumulates inside the tool.
The honest framing is a gap. The demo shows what the tool can do; the terms show what the vendor may do. Nothing in the product tour contradicts a clause that lets your inputs improve a shared model, because the tour is not the contract. Between the two sits the quiet transaction most businesses never notice they agreed to.
The failure versions are unremarkable, which is what makes them common. Business documents fed into a tool whose terms allowed those inputs to train a model shared with strangers. A customer conversation stored on servers in a jurisdiction nobody checked, under rules nobody read. A cancellation executed cleanly, which is when the team discovers there is no export, and the accumulated work history evaporates with the login.
Before adopting, check four things in the terms. Whether your inputs train anything shared, and whether a setting exists to switch that off. Where the data lives, which country's servers hold it, and who inside the vendor can reach it. What happens on cancellation, specifically whether your history leaves with you in a form a human can open. And what the vendor may claim: rights over your content that outlive the subscription are not a detail.
Then prefer the configurations where your data stays your own. Most serious tools now ship a workspace setting that excludes customer content from shared training, and most businesses never switch it on, because the setting lives in an admin menu nobody owns. Treat the terms check the way you would treat credit terms from a supplier: routine, documented, and done before the relationship starts, not during a dispute.
We run AI through our own funnel, so these questions get asked of every tool we adopt, and we built our own assistant precisely so the answers stay ours. This essay is not legal advice: a hard reading of cross-border data terms belongs with licensed practitioners, and jurisdictions differ. Guidance, not guarantees: four checks before the card details, and the material stays yours.
FAQ
Direct, unambiguous answers
What should I check in an AI tool's terms before adopting it?
Four things, before the card details. Whether your inputs train anything shared, and whether a setting exists to switch that off. Where the data lives, which country's servers hold it, and who inside the vendor can reach it. What happens on cancellation, specifically whether your history leaves with you in a form a human can open. And what rights over your content outlive the subscription.
Can an AI vendor train its model on my business documents?
Only if the subscription terms allow it, which is why the terms matter more than the demo. Nothing in the product tour contradicts a clause that lets your inputs improve a shared model, because the tour is not the contract. Many serious tools ship a workspace setting that excludes customer content from shared training, and most businesses never switch it on because it lives in an admin menu nobody owns.
What happens to my data if I cancel an AI subscription?
Whatever the terms say, so read the cancellation clause before subscribing. The failure version is a cancellation executed cleanly, at which point the team discovers there is no export, and the accumulated work history evaporates with the login. Check specifically whether your history leaves with you in a form a human can open, and test the export while the account is still alive.
Is checking AI vendor terms a legal question?
The four checks are a routine business reading, the way you would treat credit terms from a supplier: documented and done before the relationship starts, not during a dispute. A hard reading of cross-border data terms, though, belongs with licensed practitioners, because jurisdictions differ and the stakes rise with customer data. This kind of guidance is not legal advice, and the deep reading is not a do-it-yourself task.
Next step
AI Systems
AI that holds a conversation and closes work (WhatsApp consultants, extraction pipelines, grounded answers): Maryam's architecture tuned to your business.
Start an order, request a private consultation, or simply ask a question: one WhatsApp message in Arabic or English opens the conversation.
Talk on WhatsApp