Two things keep automation data onshore. First, host the automation engine in an Australian region — AWS Sydney (ap-southeast-2) or a local Australian provider — so n8n, its queue, and its Postgres database all run and store data in Australia. Second, map every node that calls an external service and check whether it sends data offshore; a US-based LLM or a foreign SaaS API is a cross-border disclosure under Australian Privacy Principle 8. For sensitive steps, redact personal information before it leaves the country or run an onshore/self-hosted model. Onshore hosting plus a mapped data flow is what data sovereignty actually requires.
The onshore checklist
- Host n8n + Postgres in an Australian region (AWS Sydney or local).
- Map every external API call; identify which leave the country.
- Redact personal information before offshore calls, or use an onshore model.
- Document the data flows for your Privacy Act / APP 8 position.
Full detail: self-hosting n8n in Australia and AI agents and the Privacy Act.
Related questions
Does using a US-based LLM break data residency?
It can. Even with onshore hosting, calling a US LLM sends that payload offshore, engaging APP 8. The fixes are to redact personal information before the call, use a provider region inside Australia where available, or run a self-hosted model (such as Ollama) on your onshore server for sensitive data.
Is n8n Cloud hosted in Australia?
n8n Cloud runs in specific regions that may not be Australian, so if onshore residency is a hard requirement, self-hosting in an Australian region gives you certainty and control. You can confirm current cloud regions with n8n, but self-hosting removes the question entirely.
Still need a hand?
Book a 15-minute map (US$50, credited to a build) and we will scope it with you — or send a note and we will add the answer here.