Privacy and residency of model calls
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
decide what data may go to which model, where, and for how long.
Planned topics
- Every call to a model sends data to a processor; check its terms, retention, location, and use of data for training.
- Classify data and allow only permitted classes for each model option.
- Minimize and redact: send only what the task needs, remove identifiers where possible.
- Residency rules may require regional endpoints or self-hosting; verify with legal.
Draft outline details
Demonstration
a data-flow diagram for the support assistant with country boundaries, the fields sent to the model, the provider's retention terms (verify), and a redaction step.
Check your understanding
What should you check before sending personal data to a hosted model?
Show answer
The provider's terms: retention, location, training use, and whether the data class is allowed.
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.