Regions and data residency
Data residency is the single most common procurement blocker in education, and the answer differs by country. A German school needs EU hosting. A UK academy trust needs the UK or the EU. A US district asks about FERPA. A Canadian board often has a province-level requirement. An Australian school asks about the Privacy Act.
So there is no company-wide default region. It is settled during the sale, recorded on the deployment, and shown back to you during onboarding to confirm.
Available regions
Section titled “Available regions”| Region | Location | Residency statement |
|---|---|---|
ap-southeast | Sydney, Australia | Data stays in Australia |
ap-singapore | Singapore | Data stays in Singapore |
ap-south | Bangalore, India | Data stays in India |
eu-central | Frankfurt, Germany | Data stays in the EU, under GDPR |
eu-west | Amsterdam, Netherlands | Data stays in the EU, under GDPR |
uk-south | London, United Kingdom | Data stays in the UK, under UK GDPR |
ca-central | Toronto, Canada | Data stays in Canada, under PIPEDA |
us-east | New York, United States | Data stays in the United States |
us-west | San Francisco, United States | Data stays in the United States |
Adding a region is a host plus an entry in the control plane, not an architecture change. If you need one that is not listed, ask.
What stays in the region
Section titled “What stays in the region”Everything that is your data. The database, its backups, and any files you upload. Backups replicate within the region only.
Not the control plane. It is global, and it holds counts, versions and billing records. No names, no records, no ticket content. See the control plane.
The distinction matters for an assessment form. “Is any data processed outside the region” has a precise answer: the number of technician accounts and managed devices, the list of enabled modules, and the version, all attached to a deployment id. Nothing that identifies a person.
The instance can answer for itself
Section titled “The instance can answer for itself”Admin, Compliance in your own deployment states its region, its residency and what each configured connector sends where. It reads this from local configuration rather than by calling home, deliberately, so it can still answer while cut off from everything, including during the incident where somebody is most likely to ask.
This is the page to screenshot for a departmental vendor assessment. See compliance answers.
What each connector sends where
Section titled “What each connector sends where”Residency covers the data we hold. A connector you enable sends data to that vendor, which is a separate question and one an assessment will ask separately.
The compliance page states it per category, because the question is about the kind of data leaving, and a school swapping Jamf for Intune has not changed the answer.
| Category | What leaves |
|---|---|
| MDM | Device serial numbers, models, assignment and compliance state |
| SIS | Student and staff names, year levels, identifiers and email addresses |
| Directory | Names, usernames, email addresses and group membership |
| Message content and recipient addresses | |
| SMS | Phone numbers and message content |
| Ticketing | Ticket subject, body and requester details |
| Warranty | Serial numbers |
| Repair vendor | Serial numbers, fault descriptions and contact details |
| Security | Device identifiers and application approval requests |
| CRM | Account and contact details |
| Printing | Usernames, card numbers and print balances |
| AI | Whatever you ask the assistant, to a model you host |
The AI row is worth reading twice. The in-product assistant runs against a model you host, and nothing is sent to an external AI provider. That guarantee is about the assistant. It does not extend to a third-party MCP client you have chosen to connect, because that client’s model sees whatever it is handed.
Self-hosted
Section titled “Self-hosted”Your data is wherever your server is, and that is the whole answer. The compliance page still works and still states what each connector sends, which is usually the part an assessment actually cares about.
Changing region
Section titled “Changing region”Supported, and treated as a planned migration: an export, a provision in the new region, an import and a DNS change. The same machinery that moves a customer between self-hosted and managed.
Tell us early. The DNS and identity provider changes have lead times that dwarf the actual data movement.