Skip to content
plugboard.appRequest a demo

Let us host it

Regions and data residency

Data residency requirements differ 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.

RegionLocationResidency statement
ap-southeastSydney, AustraliaServer and host backups in Sydney; offsite copy in Oceania, best effort
ap-singaporeSingaporeServer and host backups in Singapore; offsite copy in Asia-Pacific, best effort
ap-southBangalore, IndiaServer and host backups in Bangalore; offsite copy in Asia-Pacific, best effort
eu-centralFrankfurt, GermanyServer and host backups in Frankfurt; offsite copy in Western Europe, best effort
eu-westAmsterdam, NetherlandsServer and host backups in Amsterdam; offsite copy in Western Europe, best effort
uk-southLondon, United KingdomServer and host backups in London; offsite copy in Western Europe, best effort
ca-centralToronto, CanadaServer and host backups in Toronto; offsite copy in Eastern North America, best effort
us-eastNew York, United StatesServer and host backups in New York; offsite copy in Eastern North America, best effort
us-westSan Francisco, United StatesServer and host backups in San Francisco; offsite copy in Western North America, best effort

Adding a region is not an architecture change. If you need one that is not listed, ask.

The managed application database and uploaded files are hosted in the agreed region, on a server that holds no other school’s deployment. Server backups are held by the hosting provider (DigitalOcean) in the same region. Offsite backup copies are encrypted with your deployment’s own key before upload and stored in a bucket of their own on Cloudflare R2, created with the location hint nearest your region: oc for Sydney, which we describe as Oceania, best effort. Cloudflare treats a hint as a preference and offers no Australian jurisdiction for R2, so we do not say the offsite copy stays in Australia. When a deployment is decommissioned, its bucket is deleted 30 days later, or after the window you agreed, and we email you to confirm.

External connectors, email, external AI inference and edge services have separate processing locations. Billing and support records are separate business records. Count-only usage reporting excludes school records and ticket content, but this does not make all other processing regional. See what we process.

Settings, Compliance in your own deployment states its configured region, its residency and what each configured connector sends where. It reads this from local configuration, so it still answers while the deployment is cut off from everything else.

This is the page to screenshot for a departmental vendor assessment. See compliance answers.

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.

CategoryWhat leaves
MDMDevice serial numbers, models, assignment and compliance state
SISStudent and staff names, year levels, identifiers and email addresses
DirectoryNames, usernames, email addresses and group membership
IdentityUsernames and email addresses, for authentication only
EmailMessage content and recipient addresses for notifications sent by the desk
SMSMobile numbers and message content
PrintingUsernames, card numbers and print activity
TicketingTicket subjects, descriptions and the requester’s name
WarrantyDevice serial numbers only
Repair vendorDevice serial numbers, fault descriptions and the owner’s name
SpreadsheetWhatever the linked sheet contains, which is usually induction rosters
CRMOrganisation and contact records
BillingBilling contact and payment records. No student data
SecurityDevice identifiers and policy decisions
AIThe text of a question and the desk records needed to answer it. Where it goes depends on which of the three AI connectors you configured

Where ticket text goes depends on which of the three AI connectors you configured: nowhere at all for the bundled model, to your chosen provider on your own key, or to our inference provider on a managed plan that includes AI. None of that extends to a third-party MCP client you connect, because that client’s model sees whatever it is handed.

Your data is wherever your server is. The compliance page still works and still states what each connector sends, which is usually the part an assessment asks about.

Supported, and treated as a planned migration: a backup, a provision in the new region, a restore and a DNS change, as for a move between self-hosted and managed.

Tell us early. The DNS and identity provider changes have lead times that dwarf the actual data movement.