[ PRACTICAL SCHOOL GUIDE ]
School data location and control
Turn data-location requirements into verifiable system choices.
The idea
Turn data-location requirements into verifiable system choices.
Classroom example
Map a student prompt, connected document, provider request, log, and backup to its storage location, operator, and retention rule.
Try this next
Use this checklist for school data location and control.
- Draw the data flow
- Confirm subprocessors and providers
- Test deletion and recovery
Draw the actual data path
Identify where the school workspace, document index, model provider, logs, and backups operate. A locally hosted interface can still send prompts to an external model provider.
Try it with your school
- List each service that receives school data.
- Review the selected provider's processing terms.
- Confirm who can administer and export data.
- Define retention and deletion responsibilities.
Review the result
Make a deployment decision from the whole path. A label such as hosted or self-hosted is not enough to establish the location of every data processor.