This is a concept website · Enquire about this domain

dedicated-servers.com.auThe stack

Guide 5 of 7Where it sits

Does my server need to be in Australia?

A dedicated server is one machine in one country, so the location question has a precise answer where other services blur it. The Privacy Act does not stop a business using an overseas provider; the OAIC sets out what it asks instead, and ASD adds a test of its own.

General information, not legal or security advice.

Start with what the law does not do, because the OAIC is explicit about it. The Privacy Act does not prevent an organisation or agency from engaging a provider to store or process personal information overseas. What it does is keep the duties attached: the organisation must comply with the Australian Privacy Principles in sending personal information to the overseas provider, just as it needs to for any other overseas outsourcing arrangement. A rule that hosting must stay onshore is not what the Act says; a duty that follows the data across the border is.

That duty is not a formality, and the OAIC says what reasonable steps can look like: where an organisation continues to 'hold' personal information when storing or using it with a provider, reasonable steps may include robust management of the third party handling it, including effective contractual clauses, verifying the provider's security claims through inspections, and regular reporting and monitoring. Those steps are about how the provider is managed and checked, and the Privacy Act does not stop the provider being overseas.

Whether the Privacy Act covers a business is its own question.

A use, or a disclosure

The Privacy Act's overseas machinery switches on with the word "disclosure", and the OAIC draws a careful line between disclosing personal information and merely using it. The clearest example is traffic: routing personal information, in transit, through a server located outside Australia would usually be considered a 'use'. A machine that passes packets through a country is not the same thing as a copy of the records handed to someone there.

The dividing test is control. In limited circumstances, providing personal information to an overseas contractor to perform services on your behalf may be a use rather than a disclosure, and that happens where the entity does not release the subsequent handling of the information from its effective control. Where it is a use, the information may still be 'held' by the organisation even though it is physically located overseas, so the APPs that apply to a holder still apply, and the organisation is accountable for breaching them. Where the line is genuinely unclear, the OAIC's recommended path is the safe one: take reasonable steps to ensure the APPs are complied with. And in most circumstances, providing personal information to an overseas recipient, including a contractor performing services on the entity's behalf, is a 'disclosure', to which APP 8 and section 16C apply.

Where it is a disclosure, the duties are two halves of one rule. APP 8.1 requires the organisation or agency, before the disclosure, to take the steps that are reasonable in the circumstances so that the overseas recipient does not breach the APPs other than APP 1 in relation to the information. Section 16C then keeps the responsibility home: the organisation is accountable, in certain circumstances, for an act or practice of the overseas recipient that would breach the APPs, and accountable means the act is taken to have been done by the organisation itself and to be a breach of the APPs by it. The OAIC summarises the pair as a framework that generally requires the organisation to ensure the overseas recipient will handle the information in accordance with the APPs, and answer for it if they do not.

Two doors out are worth knowing, since they are the exceptions an overseas arrangement often leans on. The accountability does not apply where the information is disclosed under one of the exceptions in APP 8.2, or where the recipient has what the OAIC calls an 'Australian link', because a recipient with an Australian link is covered by the Privacy Act in its own right. Where it is a disclosure, the organisation must also take reasonable steps to ensure the overseas recipient complies with the APPs, and remains accountable if the recipient breaches them, subject to those exceptions.

Choosing a country

ASD approaches the same question from the direction of risk rather than law, and its model puts the choice of country on the customer's list: your data, meaning control of who can access it, and using services and support staff located in countries that are suitable based on the sensitivity of the data. The Executive guidance turns that into a question for the provider: does it guarantee that its services, including its support staff, are located in countries that are suitable for the sensitivity of the data?

The two duties can look like each other, so keep the tests apart. The Privacy Act's test is legal and threshold-based: it binds certain organisations, and it asks what reasonable steps were taken and who answers for the overseas recipient. ASD's test is advice and always-on: it asks whether the country is suitable for the sensitivity of the data, whoever you are and whatever the law requires. A business can pass one and fail the other: an organisation that picked a suitable country still owes the OAIC version of accountability for the data it discloses.

The Hosting Certification Framework

Search for Australian hosting requirements and you will meet the Hosting Certification Framework, so it is worth knowing exactly whose question it answers. It is a Department of Home Affairs framework that provides guidance to Australian Government customers, enabling them to identify and source hosting services that meet enhanced privacy, sovereignty and security requirements. Its audience is stated precisely: Australian Government customers procuring hosting arrangements for sensitive government data, whole-of-government systems, and systems rated at the classification level of PROTECTED.

It is also a moving target at the moment, which matters if a provider's page leans on it. The framework is currently undergoing reform, and the Department paused the HCF Certification registration of prospective service providers, and of HCF Certified providers seeking supplementary assessment, from 3 November 2025 until the reforms are complete. Providers already certified are not affected by the pause. For a private business renting a dedicated server, the framework answers a different question: it is the bar a government buyer holds hosting providers to, not the rule that decides where your own data may sit.