Does putting tenant or vendor details into an AI tool send their information overseas?
Often the processing happens overseas, so APP 8 may be engaged. Whether s 16C accountability then attaches is genuinely arguable and we do not resolve it here, because several major AI providers plausibly carry on business in Australia, which can give them an Australian link under s 5B(3)(b) (carrying on business in Australia), with the Act extended to their overseas acts by s 5B(1A). Where that is so, s 16C switches off entirely. The practical rule does not depend on that question: keep client personal information out of general AI tools, because APP 6 and APP 11.1 apply either way.
By Jon Oates, Founder of Privaproof · Last updated · Start the free 2-min audit →
General information, not legal advice. Your obligations depend on your circumstances.
Not sure it's you?
Does this apply to you?
Tap what's true for your agency. Nothing is saved.
Orientation only, not a compliance assessment. General information and tools, not legal advice.
Why is this the disclosure nobody notices?
Because it never goes through a procurement decision. A property manager pastes a difficult email thread into a chatbot to soften the tone. A sales agent drops an applicant's details in to draft a rejection. Someone uploads a rental ledger to get a summary. None of that appears in a systems review, and none of it was anyone's decision.
That makes it the most common unplanned offshore disclosure in a real-estate business, and the one least likely to be caught before it matters.
What is the actual rule for staff?
Write one they can follow, because a ban nobody obeys is worse than a rule people use.
- No names, addresses, contact details, identity documents, bank or income details go into a general AI tool.
- Draft with the specifics stripped out, then add them back locally.
- No uploading of application files, ledgers, ID scans or inspection photos.
- If a tool is genuinely useful, ask for it properly rather than working around the rule.
This rule is correct whether or not APP 8 is engaged, which is the point. APP 6 governs whether the use is within the purpose the information was collected for, and APP 11.1 governs the security of what you hold. Both apply regardless of where the server is.
If you want AI tooling properly, choose a service where you can establish the data location and the processing terms, including whether your inputs are used for training, and then treat it as any other supplier under APP 8. Check your own vendor's terms rather than assuming either way.
Sources: Privacy Act 1988 (Cth), APP 6, APP 8 and APP 11.1 (Schedule 1) · OAIC APP Guidelines chapters 6, 8 and 11 · OAIC APP guidelines
Are we accountable for what the AI provider does with it?
This is the part that is genuinely unsettled, and we are not going to pretend otherwise.
Section 16C makes a disclosing entity accountable for an overseas recipient's acts only where three conditions are all met: APP 8.1 applies, so no APP 8.2 exception is in play; the APPs do not already apply to the overseas recipient; and the act would breach an APP other than APP 1.
The second condition is where AI tools sit awkwardly. Where a provider has an Australian link under s 5B(3)(b) (carrying on business in Australia), with the Act extended to its overseas acts by s 5B(1A), the Privacy Act binds it directly, and s 16C does not operate at all. Several large AI providers plausibly carry on business in Australia. Whether a particular one does is a question about that provider, not a question we can answer generically, and asserting it either way would be guessing.
What does not change: your own obligations for the information you hold and the use you make of it.
Sources: Privacy Act 1988 (Cth), ss 5B(1A), 5B(3)(b) and 16C, and APP 8.1 and 8.2 (Schedule 1) · OAIC APP Guidelines chapter 8, paragraphs 8.60 to 8.63 · OAIC APP guidelines
What about using AI to screen or rank tenants?
That is a different question, and a dated one. The automated decision-making transparency rule inserting APP 1.7 to 1.9 commences on 10 December 2026 and applies to decisions made from that date. It is not yet in force.
When it commences, it will reach computer programs that make a decision, or do something substantially and directly related to making one, where the decision could reasonably be expected to significantly affect a person's rights or interests. That threshold matters: a tool that merely sorts or displays applications is unlikely to reach it, while a scoring engine that determines the shortlist may. The obligation is disclosure in your privacy policy, so the work is knowing what your software actually does before then.
Sources: Privacy and Other Legislation Amendment Act 2024 (Cth), Act No. 128 of 2024, inserting APP 1.7 to 1.9, commencing 10 December 2026 · OAIC APP guidelines · See also automated decision-making and privacy for real estate
→ The Kit includes staff-use rules covering what may and may not be pasted into an AI tool.