Residency and cross-border transfers
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
reflect residency and transfer rules in the architecture.
Planned topics
- Ask first: which laws apply to which data, and where may it be stored and processed.
- Residency is about where data lives; transfers are about where it travels, including support access and logs.
- Architectural levers: region selection, regional stores, tokenization before transfer, contractual safeguards.
- Check the SaaS and AI providers' regions and sub-processors (verify before recording).
Draft outline details
Demonstration
a map of Larkspur's systems with region labels and arrows for flows that cross a border, such as CRM SaaS support access.
Check your understanding
Is storing data in-region enough?
Show answer
No. Remote support access, backups, and analytics flows may still cross borders.
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.