Provider terms: residency, retention, training use
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
check AI provider terms against company policy and reflect them in the architecture and contract.
Planned topics
- Questions for every provider: where is data processed and stored, how long is it kept, is it used to train models, who are the sub-processors, and what are the breach terms.
- Defaults are not policy: consumer-grade and enterprise terms differ, and options such as zero or limited retention may need to be requested or configured.
- Residency and cross-border rules may restrict regions; confirm region options and any fallback routing.
- Capture terms in the contract and a data processing agreement; ask legal and privacy to review.
- Terms change: record the version reviewed and review again on provider updates. Verify before recording any specific provider term.
Draft outline details
Demonstration
a provider-terms checklist for Larkspur: processing region, retention, training use, sub-processors, deletion on request, audit rights, incident notice, exit and data return; each with status and evidence.
Check your understanding
Why not rely on provider defaults?
Show answer
They may not meet company policy; terms must be checked, configured, and contracted.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.