Smiling female manager leaning at desk and discussing with colleague. Smiling entrepreneurs are discussing over desktop PC. Blond woman is wearing eyeglasses.

Data sovereignty is about whose laws govern an organisation’s data and who can lawfully demand access to it. For Australian organisations, storing data in Australia does not settle that question. Foreign laws such as the US CLOUD Act can reach data held in Australia, and organisations generally stay accountable for personal information they send to overseas providers.

This article explains data sovereignty in Australia: what it requires, how it differs from data residency, and the steps that keep data under control.

Key takeaways

  • Data sovereignty means data is subject to the laws of the country where it is stored or processed, and to other countries’ laws that reach its provider.
  • Australia has no single data sovereignty law. Data sovereignty in Australia rests on the Privacy Act (APP 8 and section 16C), sector rules for health, finance, critical infrastructure and government, and the contracts organisations sign.
  • An Australian cloud region settles where data is stored. Support access, processing in other regions and foreign laws such as the US CLOUD Act can still reach that data.
  • Data can also leave Australia through AI tools, security logs, call recordings, backups, networks and outsourced support, beyond the main cloud platform.
  • Organisations stay accountable for personal information their providers hold. Nexon helps organisations plan cloud roadmaps that factor in compliance and governance.

What is data sovereignty?

In technology and compliance, data sovereignty means data is subject to the laws of the country where it is stored or processed. Other countries’ laws can also apply when they have jurisdiction over a company that holds, processes or can access the data, such as an overseas cloud, software or support provider.

While that definition is generally accepted, the term has other meanings too. The Department of Social Services uses it to mean the right of an entity, nation or individual to control and manage their own data. Indigenous data sovereignty refers to the right of Indigenous peoples to own Indigenous data.

This article uses the legal, jurisdiction-based sense.

Data sovereignty meaning in plain terms

For IT and business leaders, the practical data sovereignty meaning comes down to one question: whose laws can reach the data? That depends on where the data is stored, processed, backed up or accessed from, and which countries the companies handling it are subject to.

A database of client records hosted in Sydney by a United States-incorporated provider is subject to Australian privacy law. The US Department of Justice confirms that US authorities can also order that provider to disclose it.

Does Australia have data sovereignty laws?

Australia has no single data sovereignty law. For organisations covered by the Privacy Act 1988, the main obligation is APP 8, which covers personal information disclosed overseas. Sector-specific rules add requirements for health records, financial services, critical infrastructure, and government information and hosting. Contracts with providers set the remaining terms.

Data residency vs data sovereignty: what is the difference?

Data residency is where data is physically stored. Data sovereignty is whose laws govern that data and who can lawfully compel access to it. When comparing data residency vs data sovereignty, residency is the easier one to establish. Data in a Sydney cloud region, for instance, resides in Australia. However, that does not make it sovereign, since sovereignty also considers the provider’s jurisdiction and support model.

The table below compares data sovereignty, data residency and data localisation by definition, the question each answers and an Australian example.

Term
Plain definition
Questions it answers
Australian example
Data sovereignty

Data is subject to the laws of the country where it is stored or processed, and to other laws that reach the provider.

Whose laws and whose authorities can reach this data?

Client records held by a US-incorporated provider can be subject to US disclosure orders as well as Australian law.

Data residency

The physical location where data is stored.

Where does the data sit?

Data held in a Sydney or Melbourne cloud region.

Data localisation

A legal requirement to keep certain data inside a country.

Proximity & Performance: Am I required to keep it here?

My Health Record system records must not be held or processed outside Australia.

Why an Australian data centre or region does not guarantee sovereignty

An Australian data centre or cloud region settles where the data sits, but data stored in Sydney can still be reached from outside Australia in three ways:

  • Through the provider’s legal obligations. A provider incorporated in the US can be ordered under the CLOUD Act to disclose data it controls, wherever that data is stored.
  • Through people. Cloud providers’ support and operations staff manage systems remotely and may work from other countries, as Microsoft’s EU Data Boundary documentation shows.
  • Through the service itself. Some cloud services hold supporting data outside the chosen region. Microsoft, for example, states on its Azure data residency page that Microsoft Entra ID may store directory data globally.

So organisations should ask each provider three questions: which countries’ laws apply to it, where its support staff work, and which services keep data outside the chosen region.

Where data localisation fits

Data localisation is a legal requirement to keep certain data inside a country, and Australia has few such laws. The clearest is section 77 of the My Health Records Act 2012. It bars the System Operator and registered repository and portal operators from holding or processing My Health Record system records outside Australia.

The same rule applies to their contracted service providers. The Data Availability and Transparency Act 2022 also prohibits storing data shared under its DATA Scheme, or accessing personal information in it, outside Australia. Most other location rules come from government policy, records rules and contracts, such as NSW’s rules on taking records out of the state.

So for most organisations, no law requires their data to stay in Australia. Holding it offshore is generally lawful, but they remain accountable for personal information they send overseas. In practice, the requirement to keep data onshore often comes from a client contract or a government tender instead.

Why is data sovereignty important for Australian organisations?

Data sovereignty is important for Australian organisations because sending data offshore does not end their obligations for it. An organisation remains accountable for personal information held by an overseas provider, including any breach that happens there. Regulators and government buyers also expect it to know where that data sits and who can reach it.

Organisations stay legally accountable for data their technology providers hold

Under APP 8, an organisation must take reasonable steps before it discloses personal information to an overseas recipient. The Office of the Australian Information Commissioner (OAIC) generally expects this to include an enforceable contract with the recipient. Section 16C of the Privacy Act then makes the organisation accountable if that recipient breaches the APPs, even if it took those steps. Limited exceptions apply, such as when the recipient is bound by a substantially similar privacy law that individuals can enforce.

Cloud storage can work differently. In limited circumstances, the OAIC says that giving personal information to an overseas cloud provider may be a use rather than a disclosure. That can apply when:

  • A binding contract limits the provider to storing the data and making it available to the organisation.
  • Any subcontractors accept the same obligations.
  • The organisation keeps effective control of how the data is handled.

In that case, the organisation is still responsible for protecting the data as its own.

Foreign laws such as the US CLOUD Act can reach data held by overseas-owned providers

The US Clarifying Lawful Overseas Use of Data (CLOUD) Act of 2018 applies to providers subject to US jurisdiction. It requires them to disclose data in their possession, custody or control when served with valid legal process. This applies whether the data is stored inside or outside the US, as the US Department of Justice explains.

According to the Attorney-General’s Department, Australia and the US brought a CLOUD Act agreement into force on 30 January 2024. Under it, each country’s agencies can seek data directly from the other country’s communications providers for serious offences. The agreement’s text also bars either country from intentionally targeting the other’s citizens or residents.

For an Australian organisation, the practical step is to know which providers fall under foreign jurisdiction and how each handles government requests for client data.

Regulators and government buyers are asking where data lives

Regulators and government buyers now ask directly about data location. APRA’s Prudential Standard CPS 230 has applied since 1 July 2025. It requires regulated entities to notify APRA before they enter a material offshoring arrangement, including where data or staff relevant to the service sit offshore. An amended version took effect on 1 July 2026 and keeps this rule.

NSW has added similar requirements for its agencies. The NSW Government Cloud Policy took effect on 1 October 2026. It requires agencies to assess data residency and jurisdictional risk, including where data is stored, processed and accessed. Agencies must also include security, privacy and information-handling clauses in their contracts, so suppliers meet these questions in tenders.

The commercial risks: breach response and procurement exclusion

Weak data sovereignty controls expose organisations to two commercial risks: breach obligations that extend to overseas providers, and exclusion from some government work.

The breach risk comes from the Notifiable Data Breaches (NDB) scheme. Under the scheme, an organisation is treated as still holding personal information it sent overseas. If it has reasonable grounds to suspect a breach at the provider, it must take all reasonable steps to assess it within 30 days. It must notify the OAIC and affected individuals if the breach is likely to cause serious harm.

These obligations come up often: the OAIC received 1,205 data breach notifications in 2025, and 716 of them were attributed to malicious or criminal activity.

A serious interference with privacy can also bring civil penalties under the Privacy Act 1988. For a body corporate, the maximum is the greater of $50 million or three times the benefit obtained. If the court cannot determine the benefit, 30% of adjusted turnover applies instead. Since the Privacy and Other Legislation Amendment Act 2024, repeated conduct is one factor in deciding whether an interference is serious.

The procurement risk comes from government hosting rules. Commonwealth agencies use providers certified under the Hosting Certification Framework for sensitive data, whole-of-government systems and systems classified PROTECTED, a government security classification. The framework also sets conditions on who owns and controls certified providers. A supplier whose hosting does not meet the framework can be ruled out of that work.

Data sovereignty requirements in Australia: laws and compliance

Data sovereignty requirements in Australia start with the Privacy Act. Under OAIC guidance, it applies to most organisations with annual turnover above $3 million, plus some smaller ones, such as private health service providers. Sector rules then add obligations for health records, financial services, government and critical infrastructure. Most of these rules allow data to sit offshore but require organisations to assess the risk, control it by contract and, in some sectors, tell a regulator.

Privacy Act 1988 and Australian Privacy Principle 8

For most Australian organisations, the Privacy Act is the main law that applies when personal information goes overseas. Its rule for this, Australian Privacy Principle 8 (APP 8), does not stop an organisation from using an overseas provider. It simply means that the organisation stays responsible for what happens to that information.

In practice, that means three things:

  • Check the provider before sharing data. Know where it will store and access the information, and how it protects it.
  • Put the protections in the contract. The OAIC generally expects a contract that requires the provider to handle the information in line with Australian privacy law.
  • Plan for the provider’s mistakes. If the provider mishandles the information, the organisation can be held responsible, even if it took those steps.

A few narrow exceptions apply, such as when the provider is covered by a similar privacy law that individuals can enforce. Organisations should get legal advice before relying on one.

Privacy law is also tightening. Since 10 June 2025, individuals can sue over serious invasions of their privacy under a new statutory tort. The government has also consulted on a draft of further privacy reforms, so more changes may follow.

Data location rules by sector

For data sovereignty in Australia, the strictest rules sit in a few sectors, including these three. For organisations in them, these rules shape where data can go and what provider contracts must cover:

  • Healthcare. Only My Health Record system data must stay in Australia. Other health information follows the Privacy Act. In NSW, Victoria and the ACT, state or territory health privacy laws also apply, as the OAIC explains.
  • Financial services. APRA-regulated entities must check the security of systems their providers manage, under CPS 234. Their contracts with material service providers, the providers their critical operations rely on, must also say who owns and controls the data, under CPS 230.
  • Critical infrastructure. Entities must tell their data storage and processing providers when those providers hold business-critical data, under the Security of Critical Infrastructure Act 2018. Since amendments in December 2024, their own data storage systems can also fall under the asset’s security obligations if they hold business-critical data.

The table below summarises what each sector’s main rule means for data location.

Strategic workload placement: Determining the optimal fit

Sector
Key rule or framework
What it means for data location
Organisations covered by the Privacy Act

Privacy Act 1988, APP 8 and section 16C.

Offshore storage or access is allowed with reasonable steps, and the organisation stays accountable.

Healthcare

My Health Records Act 2012, section 77.

My Health Record system records must not be held or processed outside Australia.

Financial services

APRA CPS 230 and CPS 234.

No blanket onshore rule, but APRA must be told before material offshoring, contracts with material service providers must address data ownership and control, and third-party-managed assets need security controls.

Commonwealth government

Hosting Certification Framework

Sensitive data, whole-of-government systems and systems classified PROTECTED use certified hosting, with conditions on provider ownership and control.

Critical infrastructure

Security of Critical Infrastructure Act 2018

No onshore rule, but data storage systems the entity owns or operates that hold business-critical data count as part of the critical asset, and third-party data providers must be told when they hold such data.

State government

State cloud and records policies, such as the NSW Government Cloud Policy.

Agencies assess residency and jurisdiction risk, and include security, privacy and information-handling clauses in contracts.

Data sovereignty and the cloud: where control is won or lost

Selecting an Australian cloud region is only one step towards cloud data sovereignty. Organisations must also consider each cloud service’s specific settings and contract terms. A sovereignty claim weakens if a provider stores backups, system logs or encryption keys overseas, especially for personal or regulated data. Where the administrators who can access the system are located, and which company employs them, also affects sovereignty. Organisations manage these choices through cloud governance, which sets the policies and controls for using cloud platforms.

Six control layers to check with any technology provider

Maintaining Australian control over data requires assessing six specific control layers. Organisations must ask cloud and technology providers clear questions about each area.

  1. Data at rest. Which region holds the primary data, and can settings or policy restrict it to approved regions? Workloads with strict location requirements can stay on private or onshore infrastructure within a hybrid cloud design.
  2. Backups and replication. Where do backup copies and disaster recovery replicas sit, and does replication stay inside Australia?
  3. Processing and third-party services. Do any features, subcontractors or connected services, such as AI, monitoring or content delivery, process data in another region?
  4. Support and admin access. Who can access systems and data for support, including subcontractors, from which countries, and with whose approval?
  5. Metadata and telemetry. Where are logs, usage data and directory information stored? These records can include user IDs, IP addresses, device details and system activity, according to ASD guidance on event logging.
  6. Keys and jurisdiction. Who holds the encryption keys, and which jurisdictions may have authority over the provider, its parent company and its subcontractors?

The answers change over time, since providers add features, regions and support locations. Ongoing cloud management should recheck these layers whenever services or regions change, and at regular reviews, rather than only at procurement.

Microsoft Azure and Microsoft 365 show how these layers play out across one provider’s platforms.

Microsoft data sovereignty in Azure and Microsoft 365

For organisations that use Microsoft 365 and Azure, data sovereignty is shared between Microsoft and the organisation. These two platforms hold much of an organisation’s email, files, chats and AI prompts. Microsoft keeps certain data in Australia by default, as set out in its data residency commitments. The organisation must enable and manage most other controls.

What Microsoft keeps in Australia. When an organisation chooses an Australian Azure region, Microsoft’s Azure data residency page states that most Azure services store and process its data there. For Microsoft 365, if an organisation’s account (its tenant) is based in Australia, Microsoft stores emails, SharePoint and OneDrive files, Teams chats and saved Copilot conversations in Australia.

What Microsoft does not promise. The commitment covers stored data, not all processing. Microsoft can handle requests using servers in other regions, and a few services, such as the Microsoft Entra ID user directory, can store data outside Australia.

What the organisation must set up. Four Microsoft controls do most of the work:

  • Location rules. Azure Policy can stop new Azure resources being created outside approved regions.
  • Support access approval. Customer Lockbox requires the organisation’s approval before Microsoft engineers access its content for support.
  • Its own encryption keys. With customer-managed keys, the organisation can revoke a key to stop Microsoft’s services reading its data.
  • Data labels. Sensitivity labels in Microsoft Purview mark which data needs the strictest location and access rules.

These controls have limits. Microsoft states that legal demands for data and emergency access do not trigger a Lockbox request in Azure, and that its services decrypt data while the organisation’s key is active.

Data sovereignty and AI tools such as Microsoft Copilot

Microsoft 365 Copilot stores and processes data in different places. Microsoft stores Copilot interaction content in Australia for Australian tenants, but Copilot’s calls to its language models can go to other regions during periods of high demand. For customers outside the EU, that can include the US, the EU or other regions.

Microsoft’s roadmap still lists in-country Copilot processing for Australia as in development, targeted for the end of 2026. Until Microsoft confirms it is available, organisations should treat Copilot prompts as data that may be processed offshore and decide which data staff can use with it.

Data sovereignty beyond the cloud: where else data can leave Australia

Data sovereignty applies wherever data is stored, processed or accessed, including tools outside the main cloud platform. AI assistants, security monitoring, phone and meeting systems, networks and outsourced support can all hold, process or give access to an organisation’s data. Each one raises the same data sovereignty and security questions as the main cloud service.

The table below lists where data can leave Australia outside the main cloud platform, and the question to ask each provider.

Technology area
Where data can leave Australia
Question to ask the provider
SaaS and collaboration tools

Backups, support access and features that process data in other regions

Which region holds our data, and which features process it elsewhere?

AI tools and built-in AI features

Prompts, files and answers processed by a model that may run in another country or come from a third party

Where does the model run, who supplies it, and are prompts, uploads and outputs kept or used for training?

Security tools and managed security operations

Logs and alerts holding user IDs, IP addresses and email details, analysed offshore

Where are logs stored and analysed, and which countries do analysts work from?

Phones, meetings and contact centres

Call recordings, transcripts and AI summaries held by the platform

Where are recordings and transcripts stored and processed?

Networks and SASE

Traffic inspected at a provider gateway in another country

Which locations inspect our traffic, and where are its logs stored?

Backup and disaster recovery

Copies replicated to a second region or a vendor site abroad

Where do backup and recovery copies sit?

Managed IT and service desks

Offshore staff with admin access, and support tickets containing personal information

Who can access our systems and tickets, from where, and with whose approval?

AI tools and AI data sovereignty

For AI tools, data sovereignty depends on where the tool processes the prompts, files and answers that staff give it. An AI feature can run on a model supplied by a third party and hosted in another country. Depending on the provider’s terms and settings, some products also keep what users enter and use it to train future models, as the OAIC’s guidance on AI products notes.

The OAIC recommends, as best practice, that organisations do not enter personal information into publicly available generative AI tools. It cites the significant and complex privacy risks involved. For approved tools, organisations should check where the model runs, who supplies it, and whether prompts are kept or used for training.

Security tools, logs and managed SOC access

Security tools collect detailed records of user activity. The ASD’s event logging guidance lists user IDs and IP addresses in security logs, and NIST guidance on log management adds email details.

The OAIC confirms that some of that, such as IP addresses, can be personal information. Data sovereignty in cyber security therefore covers where these logs are stored, where they are analysed, and which countries the analysts work from.

A managed security operations centre (SOC) with offshore analysts can give people in other countries access to this data, even when the logs themselves stay in Australia. Under the OAIC’s APP guidelines, that access can count as a disclosure. Organisations should ask their security provider where its analysts are based and how their access is approved and logged.

Phones, meetings and contact centre recordings

Phone, meeting and contact centre platforms store some of an organisation’s most sensitive conversations. Call recordings, meeting transcripts and AI-generated summaries can contain client details, health information or payment details. These records sit with the platform provider, so organisations need to know where they are stored and processed.

For organisations that outsource these services, the contract for managed unified communications and contact centre services should specify where recordings and transcripts are stored. Contact centres need particular care, since recordings can also feed the quality and analytics tools used in customer experience management.

Networks, SASE and managed support

Networks and outsourced support can move data offshore without anyone copying a file. Secure access service edge (SASE) services, as NIST describes them, can send some or all of an organisation’s internet traffic through the provider’s cloud gateways for security checks. If a gateway sits overseas, the traffic and its logs can be inspected or stored there.

Managed IT and service desk providers raise a similar issue. Offshore staff with administrator access can reach systems directly, and support tickets can contain personal information. Organisations should ask which locations inspect their traffic, and who can access their systems and tickets, from where and with whose approval.

A six-step checklist to manage data sovereignty

Managing data sovereignty takes six steps, from mapping where data goes to rechecking controls whenever something changes. Following them turns data sovereignty compliance into a repeatable process rather than a one-off review.

  1. Map the organisation’s data and where it flows. List every system that holds or processes the organisation’s data, including backups, logs, AI tools and support access. A well-organised data foundation makes this easier, since catalogued data is easier to trace.
  2. Classify data by sensitivity and legal rule. Mark which data is personal, health, financial or government information. Then record which law or sector rule applies to each type.
  3. Set location, access and key rules. Decide which data must stay in Australia, who may access it and from where, and who holds and can revoke the encryption keys. Apply these rules through cloud settings and policies, so cloud data sovereignty does not rely on manual checks.
  4. Put it in the contract. For providers that handle personal or sensitive data, or can access systems holding it, set out the terms in the contract. Cover data location, support access, subcontractor use, security obligations, audit rights and breach notification. The OAIC generally expects an enforceable contract when personal information goes to an overseas recipient, although the right steps depend on the circumstances.
  5. Monitor and keep evidence. Review provider reports, subcontractor lists, audit or certification reports and access logs at regular intervals, and keep a record of each review. Include overseas providers in the data breach response plan, so the organisation can assess a provider’s breach within the 30 days the NDB scheme allows.
  6. Recheck when the organisation adds a vendor, region or AI tool. Every new provider, region or AI feature can change where data is stored, processed or accessed. Assess the change, update contracts and controls, and approve it before it goes live.

How Nexon helps organisations keep control of data across their technology

Nexon helps mid-market, enterprise and government organisations plan, secure and manage their technology. Nexon’s services span cloud, security, communications, networks and service management, so one partner can work across the systems that hold an organisation’s data.

Cloud strategy assessment

Our cloud strategy assessment starts with your organisation, not the technology. Our consultants assess your current environment, future-state ambitions and business requirements, considering security, risk, compliance, governance and data management from the outset. We then develop a cloud roadmap that balances transformation goals with your regulatory and operational obligations.

For organisations with specific data sovereignty requirements, these considerations are embedded into the strategy and recommendations, helping ensure the proposed cloud model is secure, compliant and fit for purpose.

Unified communications, networks and contact centre

Nexon manages unified communications, contact centre and secure network solutions, including SASE services. For each managed service, Nexon can set out where call recordings, transcripts, traffic inspection and logs are held, so clients can confirm locations before they sign. [Nexon to confirm data locations for these services.]

Managed technology services and service management

Support access is one of the easiest places for data to leave Australia unnoticed. Nexon’s managed technology services are supported by a core service desk team at its Sydney head office, with teams in Brisbane, Gold Coast, Newcastle, Melbourne and Adelaide.

Its enterprise service management solutions on ServiceNow can record support requests and access approvals in one workflow, which keeps ticket data and access decisions traceable. 

Cyber security advisory and managed security

Nexon’s managed cyber security services run from an Australia-based security operations centre, 24 hours a day, every day of the year. Its cyber security advisory services include Essential Eight assessments, ISO 27001 assessments and governance, risk and compliance advice.

Nexon also works in the sectors with the strictest data rules. Its healthcare technology solutions help providers manage patient data securely, and its financial services technology solutions support organisations that must maintain APRA compliance.

For government, Nexon’s public sector technology solutions are backed by ISO 27001 certification and membership of the Defence Industry Security Program (DISP).

Talk to Nexon about a cloud strategy assessment that builds your data sovereignty requirements into your cloud roadmap, or contact Nexon to discuss your organisation’s data sovereignty requirements.

FAQs

Does using Microsoft Azure in an Australian region mean my data stays in Australia?

Mostly. Microsoft’s Azure data residency page states that most Azure services store and process data in the chosen Australian region. Some global services, such as Microsoft Entra ID, can store data elsewhere, and support access and legal demands under laws such as the CLOUD Act can come from outside Australia.

Check that the Microsoft 365 tenant’s home country is Australia, so emails, files, Teams chats and saved Copilot content are stored here. Copilot can still process prompts in other regions until in-country processing arrives, which Microsoft’s roadmap targets for the end of 2026. Until then, set rules on which data staff can use with Copilot.

Ask where data, backups and logs are stored and processed, who can access them and from which countries, who holds the encryption keys, and which countries’ laws apply to the provider and its subcontractors. Then write the answers into the contract.

A public cloud region is where a global provider stores data in Australia, which supports data residency. A sovereign cloud usually adds stronger controls over support access, encryption keys or legal jurisdiction, though the model varies by provider. For cloud data sovereignty, what matters is who can reach the data and under which laws.

It can. The CLOUD Act can require providers under US jurisdiction to disclose data in their possession, custody or control, wherever it is stored, when served with valid legal process. The Australia-US agreement adds a separate route for each country’s agencies to request data directly from the other’s providers for serious crimes. Microsoft and Amazon Web Services (AWS) are US companies, so data in their Australian regions may fall within that reach.

A provider’s support engineers, administrators and subcontractors can access data when a support case or task needs it. Some providers offer approval-based access, such as Microsoft’s Customer Lockbox, although Microsoft notes that legal demands in Azure fall outside it. Confirm which countries these staff work from, and write approval rules into the contract.

Encryption keys affect who can read data and when. As Microsoft’s documentation on customer-managed keys shows, an organisation that holds its own keys can revoke them to stop the provider decrypting its data. The provider still decrypts the data while the key is active, so customer-held keys reduce risk but do not remove the provider’s access.

Generally yes, except for My Health Record system data, which section 77 of the My Health Records Act 2012 bars from being held or processed outside Australia. Other health information can go offshore under the Privacy Act, but the healthcare provider stays accountable. State health records laws may also apply, as the OAIC notes.

No. APRA has no blanket onshore rule, but under CPS 230, regulated entities must notify APRA before entering a material offshoring arrangement, including where relevant data will sit offshore. CPS 234 also requires them to assess the security of information assets that third parties manage.

Most come from state cloud, records and procurement policies and contracts, rather than a single law. The NSW Government Cloud Policy, in effect from 1 October 2026, requires agencies to assess data residency and jurisdictional risk. It also requires security, privacy and information-handling clauses in contracts. Councils and agencies outside NSW should check their own state’s policies.

It should map which data is moving, classify it by sensitivity and legal rule, and choose regions and services that meet those rules. Treat data sovereignty and the cloud design as one decision, with region policies, key management, support access rules and contract terms in place before any data moves.

Nexon builds cloud strategies for Australian mid-market, enterprise and government organisations, with roadmaps that factor in risk, security, compliance and governance. Its managed security runs from an Australia-based security operations centre.

References