Skip to content

Data residency

51 help pages

Data residency sets the country where a site's Patching builds run. Each update job clones your repository and runs Composer and the agent in a throwaway build environment; this setting chooses the country that environment runs in. It is set per site. On the previous prices it is included in every Patching plan. On the new prices, Australia is always available, and choosing another country is part of Agency, Enterprise and Black (see The new pricing: Pay as you go and Agency).

Where to set it.

  • In the enrolment wizard, on the Mode step. Australia is the default.
  • In an enrolment profile (Settings → Patching → Profiles). Sites enrolled from the profile take its country.
  • On the site's Patching tab: an administrator or site manager selects Edit, chooses another country under Data residency and selects Save. The form shows Applies from the next job: a job already queued or running keeps the country it started with. The change is recorded in the site's activity with the old and new country, and who made it.

Only organisation administrators and site managers can change the setting. Any member can see the site's country.

Choosing another country on the new prices. This applies only where your account is on the new prices. On Pay as you go, where more than one country is offered, the Data residency list shows the other countries as "(country) (Agency)". They are greyed out, with the note "Choosing another country is part of the Agency plan." and a See plans link to Plans. Saving one anyway, in the wizard, a profile or the site's Edit form, is refused with "Choosing where Patching builds run is part of the Agency plan. This organisation's plan builds in Australia. Move to Agency on the billing page to choose another country." Australia is always allowed. The field stays hidden while only one country is offered. Moving an existing Pay as you go account to Agency in the dashboard is not available yet, so contact support.

Keeping what you have. A site or profile that already holds a country keeps it, and you can save other changes. Losing the option never moves data and never changes the saved setting.

Applying a profile. If a profile's country is not Australia and your organisation is on Pay as you go, applying it keeps each site's own country. The preview shows the site as blocked: "Choosing the data residency country is part of the Agency plan; this website keeps its current country".

If your plan ends. If you chose a country while on Agency, Enterprise or Black and that plan ends, new jobs build in Australia instead. The site's Patching tab shows where the next job builds, and the job's activity says "Builds in Australia, not (country): choosing the country is part of the Agency plan, and this organisation's plan no longer includes it". The site's setting stays, so the country comes back with the plan, and the activity then says "Builds in (country) again: this organisation's plan includes choosing the country again". A country chosen before your account moved to the new prices keeps building there.

Countries. Builds run on Vultr, a cloud provider, so a country can be offered only where Vultr has a location. Today Sentinel offers Australia only. While only one country is offered, the Data residency field is hidden in the wizard, the profile form and the site's Edit form when the site already has that country. The Patching tab still shows the country, read-only. Sentinel offers more countries as it switches them on, and the field appears when there is a choice. If Vultr stops offering a country that is on offer, it disappears from the list for new choices; a site that already uses it keeps it, and Sentinel staff are told. Vultr's list is checked every day.

How a job runs. Jobs run on build machines that Sentinel creates on demand, in the site's country, including Australia. A machine may run more than one job and is deleted when it is idle. The build environment (the container and its workspace) is thrown away after every job. Starting a machine adds a few minutes to a job. An Australian job does not fail for lack of a machine; it waits for one. For any other country, if no build machine is ready in the chosen country within 20 minutes, the job stops without building anywhere else: it is shown as Failed with "Blocked: no build server became available in (country)", organisation administrators are told in the bell and by email, and you can run the update again later. A job is never moved to another country, with one exception: if the plan that included your choice of country ends, new jobs build in Australia. The site's Patching tab then shows Australia next to the chosen country, and each such job's activity says why.

Where the job ran. Each job on the site's Patching tab shows Built in and the country, and the job's first step in the activity log says the same. A queued job shows Builds in and the country it will use.

Where your data goes. Data residency covers the build environment only.

DataWhere it is
Your repository's code, composer.json and composer.lockCloned into the build environment in the chosen country and deleted when the job ends; the build machine is deleted when it is idle.
Composer packagesDownloaded into the build environment in the chosen country from Packagist, Drupal.org and the other repositories your composer.json names.
Git and hosting credentials, and your AI keyStored encrypted in Sentinel's dashboard in Australia. For a job they are passed to the build environment in memory only and never written to its disk.
Code and prompts sent to your AI providerSent from the build environment to the AI provider you connected, at that provider's standard endpoint. Data residency does not change where the AI provider processes them.
The update branch and pull requestPushed to your Git host, wherever that host keeps your repository.
Deployments (Copilot and Autopilot)Requested by Sentinel's dashboard in Australia from your hosting platform.
Job steps, logs, activity and stored artefacts (diffs, test output)Kept in Sentinel's dashboard database in Melbourne, Australia, whatever country the build ran in.

Legal and policy context. Sentinel does not decide whether a setting meets your obligations; you, your customer or your adviser do. The summaries below are general information, not legal advice, and were checked against the primary sources on 24 October 2026.

  • Australia. The Digital Transformation Agency's Hosting Certification Framework certifies hosting providers at two levels, Certified Assured and Certified Strategic, to reduce data sovereignty, ownership and supply chain risk. Government agencies must use certified services for sensitive government data, whole-of-government systems and systems classified PROTECTED, alongside the Protective Security Policy Framework. Sentinel and Vultr are not certified under the Framework, so choosing Australia keeps builds in Australia but does not make Patching a certified service.
  • Canada. The Treasury Board's requirement on electronic data residency (first issued as the Direction for Electronic Data Residency and now part of the Directive on Service and Digital) asks federal departments to keep Protected B, Protected C and Classified electronic data in Canada, mainly when it is at rest. It binds federal departments, not private companies, though contracts often carry it over.
  • European Union and United Kingdom. The GDPR and the UK GDPR do not require personal data to stay in the EU or the UK. They set rules for transferring it outside: to a country with an adequacy decision, or with safeguards such as standard contractual clauses (Chapter V, Articles 44 to 49). Choosing an EU country or the United Kingdom keeps the build there while your plan includes the choice; your code may not contain personal data at all, and the AI provider and Sentinel's dashboard in Australia are separate transfers to assess.
  • India. The Digital Personal Data Protection Rules, 2025 (notified November 2025) allow personal data to be transferred outside India, subject to any conditions or restrictions the Central Government sets by notification (Rule 15). The cross-border provisions take effect in May 2027.

Sources: Hosting Certification Framework, Protective Security Policy Framework, Government of Canada: Data sovereignty and public cloud, Directive on Service and Digital, European Commission: international data transfers, GDPR Article 44, Digital Personal Data Protection Rules, 2025.