Short answer
For government buyers, the practical questions are where stakeholder data is stored, processed and backed up (residency), whose laws and control it is subject to (sovereignty), and what security assurance covers the vendor's own application. Australian hosting gives residency, but data held by a US-headquartered provider can still be reachable under the US CLOUD Act, so no vendor on such a provider can honestly promise immunity from foreign law. Use the PSPF, the ISM and the Hosting Certification Framework to set requirements, and ask vendors to evidence their answers.
What is data sovereignty, and how is it different from residency?
Data sovereignty is the idea that data is subject to the laws and governance of the place, and the parties, that control it. Data residency is narrower: where the data physically sits and is processed. The two are often blurred in marketing, and the difference matters when you buy software.
- Residency asks: are the primary data, backups, logs, search indexes and AI processing all in Australia?
- Sovereignty asks: which governments' laws could compel the provider, or its own providers, to hand data over?
- Control asks: who manages the encryption keys, who can access the data, and under what approvals?
Why does it matter for government stakeholder data?
Stakeholder engagement records hold names, addresses, phone numbers, views on contentious projects and sometimes culturally sensitive information. They are personal information under privacy law, may be requested under FOI or RTI, and are increasingly used as evidence in audits and disputes. Three things follow:
- Legal exposure: knowing which laws apply to the data is part of protecting it, including foreign laws that reach the provider.
- Security assurance: agencies need evidence about controls, and need to know whether an assessment covers the vendor's application or only its cloud provider.
- Community trust: people expect what they tell a project or agency to be handled carefully and kept onshore.
How do classification and hosting requirements fit together?
The Protective Security Policy Framework (PSPF) sets how Australian Government entities protect information, including how it is marked: OFFICIAL, OFFICIAL: Sensitive, PROTECTED, SECRET or TOP SECRET. The originator of the information decides how it is marked, based on the harm that would follow if it were compromised.
The Hosting Certification Framework, run by the Digital Transformation Agency, helps agencies source hosting that meets enhanced privacy, sovereignty and security requirements. It applies to hosting of systems at PROTECTED, whole-of-government systems and sensitive government data. Hosting providers are certified at Strategic or Assured level.
Requirements for a particular system flow from these frameworks, the ISM and your agency's own policies, so ask your agency security adviser what applies rather than relying on a vendor's summary.
What does an IRAP assessment tell you?
The Infosec Registered Assessors Program (IRAP) is run by the Australian Signals Directorate (ASD). ASD-endorsed assessors carry out independent security assessments of ICT systems and cloud services against the Information Security Manual (ISM), for systems up to SECRET. An assessment produces a report; the agency then decides whether to authorise the system.
Three points are easy to miss. IRAP assessors do not certify or accredit systems. An assessment generally does not cover every ISM control, so read the report to see what was tested. And a cloud provider's assessment covers its infrastructure, not the application a vendor runs on top of it. For the full set of buyer questions, see IRAP and stakeholder management software: what buyers should ask.
What about AI features?
AI features are often where data leaves the country unnoticed: a vendor stores data in Australia but sends text to an offshore model for summarising or sentiment analysis. Ask specifically where AI inference runs and whether prompts and outputs are retained.
NSW Government agencies also apply the AI Assessment Framework under the NSW AI Operational Policy when it is required, which covers matters including transparency, human oversight, fairness, accountability and privacy. Uses assessed as high or critical risk go to the NSW AI Review Committee. See the NSW AI Assessment Framework explained.
What is the CLOUD Act risk?
The US Clarifying Lawful Overseas Use of Data (CLOUD) Act, passed in 2018, allows US authorities to require providers subject to US jurisdiction to preserve or disclose data within their possession, custody or control, regardless of whether it is stored inside or outside the United States. Australia and the United States also have an agreement under the CLOUD Act framework, in force since 2024, that lets each country's authorities seek data directly from providers in the other for serious crime investigations, subject to safeguards.
If stakeholder data is held by a US-headquartered cloud provider, or by a vendor running on one, it may be reachable under US law regardless of where the servers are. Australian residency is still valuable, but treat any claim that foreign law cannot touch the data with caution, and ask vendors to explain their position plainly.
What should be on your procurement checklist?
- Where all data is stored, processed and backed up, including logs, search indexes and disaster recovery.
- Where AI inference runs, and whether any prompts or outputs leave Australia or are retained by a model provider.
- A complete subprocessor list, with the location of each.
- What security controls the vendor can evidence for its own application, and what any IRAP assessment actually covers.
- Who manages encryption keys and who can access production data.
- Personnel security arrangements, if your classification requires them.
- Which foreign laws could apply to the vendor and its providers, explained plainly.
- Contract terms for residency, breach notification, audit rights and return or deletion of data at exit.
For more on privacy obligations, see community engagement data, the Privacy Act and data residency.
Where VivoAI fits
VivoAI keeps the engagement record in AWS Sydney (ap-southeast-2), with the region enforced in code, AI inference onshore, and offshore processing paths disabled by default. Encryption key management is Australian-controlled, and VivoAI has no corporate presence outside Australia. AWS is US-headquartered, so we offer data residency, not immunity from foreign law.
VivoAI is built against the Australian Government Information Security Manual (ISM), ISO/IEC 27001 controls and the ASD Essential Eight. Not IRAP-assessed. The AWS Sydney infrastructure we run on is IRAP-assessed; that covers our infrastructure. See where the record lives, and what we can and can't claim.
Frequently asked questions
What is the difference between data residency and data sovereignty?
Residency is about where data is physically stored and processed. Sovereignty is about whose laws and whose control the data is subject to. Data can be resident in Australia and still be reachable under foreign law if the provider holding it is subject to that law.
Does hosting in an Australian cloud region protect data from the US CLOUD Act?
Not by itself. The CLOUD Act allows US authorities to require US-based providers to disclose data in their possession, custody or control regardless of where it is stored. Australian residency still matters for privacy, security and performance, but it is not immunity from foreign legal process.
What hosting is required for PROTECTED information?
Australian Government requirements for PROTECTED systems are set through the PSPF, the ISM and the Hosting Certification Framework, which applies to hosting of PROTECTED systems, whole-of-government systems and sensitive government data. Check the current documents and your agency security adviser for what applies to your system.
Is stakeholder engagement data classified?
It depends on the content and on your agency's assessment. Much of it is personal information covered by privacy law, and some records may warrant an OFFICIAL: Sensitive marking or higher. The originator of the information decides its classification, using the PSPF.
Sources
- Protective Security Policy Framework (Department of Home Affairs)
- Hosting Certification Framework (Digital Transformation Agency)
- Infosec Registered Assessors Program (Australian Signals Directorate)
- IRAP consumer guide (Australian Signals Directorate)
- Information Security Manual (Australian Signals Directorate)
- United States and Australia enter CLOUD Act agreement (US Department of Justice)
- Australia–United States CLOUD Act Agreement (Department of Home Affairs)
- NSW AI Assessment Framework (Digital NSW)
This article is general information, not legal advice. Check the requirements that apply to your agency and obtain advice for your circumstances.
Next step
Ask us the hard residency questions
We'll walk your security team through where the record lives, where the AI runs and what we can and can't claim, before you commit to a pilot.