This article sets out what I've found across a year of research and analysis while implementing Claude for my clients. Disclaimer: None of this is legal advice, so make sure you seek your own.
The short answer
- One Australian law requires data to stay onshore, section 77 of the My Health Records Act, and it binds the operators of that system rather than ordinary organisations.
- Australian Privacy Principle 8 (APP 8) permits overseas processing and holds you liable for what the overseas provider does with the data, so the accountability stays here.
- A Sydney region buys you residency while jurisdiction stays with the provider's home courts, and that holds for every US platform.
- The prudential, health, legal and financial-crime rules ask you to manage the transfer, and government agencies are the exception, since certification pushes them onshore in practice.
- The contract decides the vendor review: no training on your data, defined retention, a named subprocessor list, and retrieval and deletion rights.
Residency and sovereignty answer different questions
In software procurement, residency and sovereignty get used as if they were the same thing, and the difference between them decides how much of your compliance question a Sydney region can answer.
- Residency
- Where the processing and the storage happen.
- Sovereignty
- Whose legal system can compel access to the data.
Sovereignty follows the company rather than the server, because the US Clarifying Lawful Overseas Use of Data Act (CLOUD Act) lets American law enforcement compel a US provider to produce data in its control wherever in the world that data sits. Australia and the US also hold a bilateral agreement (opens in a new tab), in force since January 2024, that lets authorities in either country request data directly from a provider in the other country for serious crime investigations, instead of going through the slower government-to-government process.
A US platform processing your data in Sydney gives you residency while jurisdiction stays in the United States, and that holds for Anthropic, OpenAI, Google and Microsoft alike. What matters is whether that arrangement meets your compliance requirements, and for most Australian organisations it does, because the Privacy Act allows the transfer as long as you manage it.
The Privacy Act permits overseas processing and keeps you accountable
The Privacy Act's cross-border rule is APP 8, which permits the transfer while keeping the liability at home. Before an organisation discloses personal information to an overseas recipient, APP 8.1 requires reasonable steps to ensure the recipient handles it to the standard of the Australian Privacy Principles (APPs), which in practice means a binding contract. Section 16C then holds the Australian organisation liable for what the overseas recipient does with the data, as if the organisation had done it itself, so the accountability never leaves the country even when the processing does. The Office of the Australian Information Commissioner (OAIC) carries the detail in its APP 8 guidelines (opens in a new tab).
The duty falls away in a few narrow cases, including a list of trusted countries the 2024 reforms let the government prescribe and that is still empty as at August 2026, so in practice you are doing the reasonable steps.
Cloud arrangements can sit outside APP 8 altogether, because the same guidelines treat sending data to an overseas provider as a use of the data rather than a disclosure of it, as long as the provider may only use it for the purpose you set, you keep effective control, and every subcontractor carries the same restriction. Those conditions describe a well-drafted enterprise AI agreement: no training on your data, defined retention, a named subprocessor list, and retrieval and deletion rights that keep control with you.
On AI specifically, the OAIC's October 2024 guidance (opens in a new tab) recommends against entering personal information into publicly available AI tools, and it treats overseas hosting as a live APP 8 question, and the line it draws sits between consumer tools, where you control nothing, and enterprise agreements, which give you the controls above.
Enforcement has arrived alongside the guidance, because the Federal Court ordered Australian Clinical Labs to pay $5.8 million (opens in a new tab) in October 2025, the first civil penalty under the Act, the OAIC opened 2026 with a compliance sweep that examines whether privacy policies name the countries data goes to, and from 10 December 2026 a new rule requires privacy policies to disclose automated decision-making that significantly affects people.
One law requires onshore data, the rest require management
The rules that come up in these conversations are privacy, prudential, health, legal, government, critical infrastructure and financial crime, and a single data-localisation rule exists among them: section 77 of the My Health Records Act (opens in a new tab), which forbids holding or processing My Health Record system data outside Australia, and even that binds only the system's own operators, repositories and contracted providers. A private clinic's ordinary patient records sit under APP 8 and the state health privacy principles, which conditionally permit transfer like everything else.
Banking, insurance and superannuation
The Australian Prudential Regulation Authority (APRA) permits offshoring as long as it is told first, because CPS 230 (opens in a new tab), in force since 1 July 2025, asks the entity to notify APRA before entering a material offshoring arrangement and to keep managing the risk, where the outsourcing standard it replaced asked for consultation. Directors often assume APRA blocks offshoring outright, and its first AI letter to industry, 30 April 2026, is about governance and supply-chain visibility and says nothing about location.
Health providers
Health data outside the My Health Record system can go overseas on the same conditions as everything else, because the state rules, meaning Victoria's health privacy principle (HPP) 9, NSW's HPP 14 and Queensland's Information Privacy Act, permit transfer out of the jurisdiction with comparable protection, a contract, or consent, which is the APP 8 shape restated.
The legal profession
Confidentiality binds wherever the data sits, so the conduct rules travel with the file, the regulators' joint statement of December 2024 warns against public chatbots for client material, and the court practice notes (NSW from November 2024, the Federal Court from April 2026 (opens in a new tab), Victoria from May 2026) condition AI use on controlled environments and on the data staying out of training. The privilege-waiver risk the 2025 family-law authority flagged turned on exposure through public tools rather than on server location.
Government agencies
Certification pushes agencies onshore in practice, because the Hosting Certification Framework (opens in a new tab) gates sensitive and PROTECTED workloads behind certified providers, and new certifications have been paused since November 2025 pending reform. Assessors under the Information Security Registered Assessors Program check controls against the Information Security Manual, and the AI-in-government policy mandates accountable officials and impact assessments, so what limits an agency is what it can certify.
Critical infrastructure and reporting entities
The Security of Critical Infrastructure Act and the financial-crime rules both permit offshore processing while keeping the liability here, because the Act's 2024 amendments pull data storage systems into risk-management and notification duties, and the Australian Transaction Reports and Analysis Centre permits outsourced processing with the reporting entity still answerable for it.
The residency you can buy, as at August 2026
Residency itself has become buyable through 2026, which removes most of the practical objection. The picture below is as at August 2026 and it has moved every quarter, so verify the current state before relying on it.
- Claude through AWS Bedrock. The Sydney region serves older Claude models directly, and newer models arrive through cross-region inference profiles (opens in a new tab), which come in geographic and global variants, and AWS has been adding Australia-bounded profiles through 2026, so check the current model list before you assume a model runs in region.
- OpenAI models through Azure. Regional and data-zone deployments exist in Australia East, and in-region model availability is thinner than the global tier and shifts often, so check model by model.
- Gemini through Vertex AI. The Sydney region serves current Gemini models, and Google's residency terms (opens in a new tab) cover data at rest in the selected region while support staff can sit offshore.
- The direct APIs. Anthropic's API processes in the United States or Europe today, and the company signed a memorandum of understanding with the Australian government in July 2026 (opens in a new tab) and says it is exploring local capacity through partners. OpenAI's direct API makes no Australian commitment, and the NEXTDC AI campus it attached its name to in Sydney is compute capacity due in 2027, which says nothing about where your data is processed today.
What this means for a vendor review
The questions that decide a review are the ones the law asks: whether the provider trains on your data, how long it retains it, who the subprocessors are, whether you keep effective control through retrieval and deletion rights, whether your privacy policy names the countries involved, and whether you could show your reasonable steps if the OAIC asked. Location decides the answer only where a certification requirement or the My Health Records Act puts it there, so when a stakeholder says the law requires your data onshore, asking which section settles it, because one such law exists and it probably does not bind you.
If what you need is sovereignty itself, meaning data no foreign court can reach, no platform above supplies it at any region setting, and the only path that does is running open-weight models on hardware you control, which I weigh up in Open models are closing the gap, and there are still too many reasons to wait.