Why Every Australian Industry Needs Data on Australian Soil

From patient records to student data, tenant applications to tax files — Australian regulations increasingly demand that personal information stays under Australian jurisdiction. Here's what the law says for your industry.

The Privacy Act 1988 (Cth) governs how personal information is collected, stored, used, and disclosed across Australia. The Privacy and Other Legislation Amendment Act 2024 introduced penalties of up to $50 million per contravention for serious interference with privacy. The $3 million annual turnover small business exemption — which has shielded most small operators since 2000 — is expected to be removed by December 2026, bringing an estimated 2.5 million additional businesses under the Act. And from 1 July 2026, AML/CTF reforms will independently drag over 100,000 businesses under Privacy Act obligations regardless of the exemption's formal status.

Meanwhile, if your backend provider is a US-incorporated company (AWS, Google Cloud, Azure, Supabase, Firebase), your data is legally reachable under the US CLOUD Act — regardless of which region you select. WattleDB is 100% Australian-owned, removing that jurisdictional risk entirely.

Industries Covered

🏥

Healthcare — GPs, Dental, Allied HealthPatient records, Medicare data, clinical systems

Healthcare providers handle some of the most sensitive personal information in Australia. Under the My Health Records Act 2012, all data within the My Health Records system — including backups — must never be processed, held, taken, or handled outside of Australia (Section 77). This is one of the strictest data residency mandates in Australian law, with zero exceptions for identifiable data.

Beyond My Health Records, general practice, dental, and allied health data falls under the Privacy Act 1988 and specifically the handling of "health information," which is classified as sensitive information under APP 3. Health service providers have always been covered by the Privacy Act regardless of turnover — the small business exemption has never applied to health services.

The Australian Dental Association (ADA) mandates that dental records be securely stored and protected from unauthorised access. Computer systems must be password-protected, screen visibility limited to staff, and security software kept current. Under APP 8, cross-border disclosure of health information requires the disclosing entity to take reasonable steps to ensure the overseas recipient complies with the APPs — a much harder bar to clear than simply hosting in-country.

My Health Records Act 2012 (s.77)

All My Health Record data, including backups, must never be processed, held, or handled outside Australia. No exceptions for identifiable data.

Source: Digital Health Agency — My Health Record legislation

Privacy Act 1988 — Health Services

Health service providers are exempt from the small business exemption. All practices handling health information must comply with the APPs, regardless of turnover.

Source: OAIC — Small business exemption guidance

ADA Data Privacy Guidelines

Dental practices must implement technical and physical security measures, restrict access, maintain security software, and have data breach response plans.

Source: Australian Dental Association — Policy Statement 5.18

My Health Records Rules 2026

Non-compliant registered organisations may have their My Health Record registration revoked. OAIC is the privacy regulator for the system.

Source: Digital Health Agency — Participation obligations

How WattleDB Helps

WattleDB stores all data — including backups and replicas — on Australian-owned infrastructure in Sydney and Canberra. No US parent entity means no CLOUD Act exposure for patient records. Row-level security enforces access control at the database layer, and Australian-only SMTP ensures appointment confirmations and password resets never traverse offshore relays.

👶

Childcare & Early LearningEnrolment data, child images, worker records

Childcare centres handle children's personal information, family details, medical histories, photos, and CCTV footage — data that demands the highest protection standards. The National Quality Framework (NQF) was updated from 1 January 2026 with enhanced child safety requirements in Quality Areas 2 and 7.

Changes to Regulation 168 now require services to have explicit policies for the taking, use, storage, and destruction of images and videos of children, obtaining parental authorisation, and governing use of optical surveillance devices like CCTV. Personal device use by staff while working directly with children is banned or restricted across all states from September 2025.

The OAIC has published an exposure draft of the Privacy (Children's Online Privacy) Code 2026, which imposes strict requirements on how children's personal information is collected and handled. The final Code must be completed by 10 December 2026. A National Early Childhood Worker Register launched nationally from 27 February 2026, centralising worker screening data.

NQF 2026 Amendments — Reg 168

Mandatory policies for taking, storing, and destroying images/videos of children. Parental authorisation required. CCTV use must be governed by policy.

Source: ACECQA — NQF child safety changes, 1 January 2026

Children's Online Privacy Code 2026

OAIC exposure draft imposing strict standards on collection and handling of children's personal information. Final Code due 10 December 2026.

Source: DLA Piper — Privacy Matters, April 2026

How WattleDB Helps

Children's data demands the strongest possible protections. WattleDB ensures enrolment records, medical information, emergency contacts, and image metadata never leave Australian jurisdiction. No US-owned entity can be compelled to disclose a child's personal information under the CLOUD Act. Storage policies enforce granular access control for sensitive files like photos and medical certificates.

🏗️

Construction & TradesElectrical, plumbing, building — worker safety, licences, compliance records

Construction businesses — including electricians, plumbers, and builders — handle worker safety records, licence information, induction certificates, and client personal data. Australian builders must retain construction documents for 6 to 10 years covering statutory warranty periods (6 years for major defects), ATO records (5 years), Fair Work obligations (7 years), and NCC compliance evidence.

State-based long service portability schemes (e.g., NSW Long Service Corporation) require employers to keep books and records for at least six years after the last service entry, including worker names, addresses, dates of birth, and service periods. Queensland's QBCC Amendment Act 2025 introduces electronic processes for managing builders' licences, approvals, and WHS obligations from 2026.

Cloud-based document management with Australian data residency is now a tender requirement for many commercial construction projects. For firms handling worker personal information (TFNs via payroll, White Card records, medical fitness certificates), the Privacy Act applies — and once the small business exemption is removed, every sole-trader sparky and plumber will need to comply.

State Long Service Acts

Records of worker names, addresses, dates of birth, and service periods must be kept for at least 6 years after last entry.

Source: NSW Long Service Corporation — Employer obligations

WHS Act & Safe Work Australia

Induction records, competency certificates, and incident reports must be retained. Cloud-based WHS platforms need secure, accessible storage.

Source: Safe Work Australia — Construction safety

How WattleDB Helps

Construction SaaS platforms built on WattleDB can store worker safety records, licence data, and compliance documentation on Australian-owned infrastructure. S3-compatible storage handles large files like site photos, plans, and video inductions with data residency guarantees. For tenders requiring Australian-hosted data, WattleDB is an easy compliance tick.

📡

TelecommunicationsCarriers, ISPs, MVNOs — metadata retention, subscriber data

Australian telecommunications providers operate under some of the most prescriptive data obligations in the country. The Telecommunications (Interception and Access) Amendment (Data Retention) Act 2015 requires carriers and ISPs to retain specific telecommunications metadata for a minimum of two years. This includes subscriber information, call date/time/duration, device location data, IP addresses, and email sender/recipient details.

Retained data must be encrypted and protected from unauthorised interference or access. The Australian Privacy Principles apply to all data retained under the Act, imposing obligations on service providers to ensure quality, security, and proper handling of personal information.

The OAIC has direct oversight of telecommunications carriers' handling of data collected under the data retention scheme. Carriers and carriage service providers that use communications infrastructure in Australia are subject to these obligations, as well as the broader Telecommunications Act 1997 provisions on protecting communications.

Data Retention Act 2015

Mandatory 2-year retention of telecommunications metadata. Data must be encrypted and secured. OAIC oversees compliance.

Source: Department of Home Affairs — Data retention obligations

Telecommunications Act 1997

Carriers must protect the confidentiality of communications. OAIC has oversight of privacy handling by carriers and carriage service providers.

Source: OAIC — Telecommunications privacy legislation

How WattleDB Helps

Telco platforms and MVNOs building subscriber management, billing, or customer portals on WattleDB get mandatory encryption, Australian-owned storage, and zero CLOUD Act exposure for subscriber metadata. The 2-year retention requirement aligns with database-level backup policies that keep all data onshore.

🎓

Education & TrainingSchools, universities, RTOs — student records, learning platforms

Australian educational institutions collect extensive personal information about students, families, and staff. Private schools and RTOs are covered by the Privacy Act 1988 (government schools fall under state/territory privacy legislation). Higher education providers must comply with privacy requirements set out by the Department of Education and TEQSA (Tertiary Education Quality and Standards Agency).

In 2026, new guidelines focus on managing the full lifecycle of children's data in schools: intentional use of social media, minimising sharing of personal information, and obtaining proper consent. The Safer Technologies 4 Schools (ST4S) framework, developed by Education Services Australia, aims to unify digital privacy standards across states and territories.

Research has highlighted that most Australian universities and schools lack adequate cybersecurity protection, and student data is widely collected through learning management systems, assessment platforms, and third-party EdTech tools — often without sufficient scrutiny of where that data is processed and stored.

Privacy Act — Private Schools & RTOs

Private educational institutions must comply with the APPs. Health information (e.g., student medical records, allergy details) is classified as sensitive information.

Source: OAIC — Privacy Act guidance for organisations

ST4S Framework 2026

Safer Technologies 4 Schools aims to streamline digital privacy assessment of EdTech products across Australian states and territories.

Source: Education Services Australia — ST4S initiative

How WattleDB Helps

EdTech platforms built on WattleDB can assure schools and universities that student data stays under Australian jurisdiction. No US parent entity can be compelled to hand over student records, assessment results, or behavioural data. This is a competitive advantage when selling to education departments with privacy-conscious procurement policies.

📈

Accounting & TaxTax agents, BAS agents, bookkeepers — TFNs, financial records

Tax practitioners handle Tax File Numbers (TFNs), financial statements, and deeply sensitive client information. The Privacy (Tax File Number) Rule 2015 governs how TFN information is collected, used, stored, and disclosed. The Tax Practitioners Board (TPB) requires agents to keep proper client records and maintain confidentiality of client information.

From 1 July 2026, accounting firms become classified as "Tranche 2 entities" under AML/CTF reforms. This independently brings them under Privacy Act obligations, with records required to be kept for at least 7 years to evidence compliance. This affects over 100,000 businesses.

The TPB's 2026 exposure draft on AI use makes clear that tax practitioners must obtain explicit client permission before disclosing information to any third-party AI platform. Inputting client data into an external AI tool counts as disclosure — and if that AI tool runs on US-owned infrastructure, you're making a cross-border disclosure under APP 8.

TFN Rule 2015

Strict requirements on collection, use, storage, and disclosure of Tax File Number information. TFN data must be secured and access restricted.

Source: Privacy (Tax File Number) Rule 2015

AML/CTF Tranche 2 (Jul 2026)

Accounting firms become reporting entities. 7-year record retention. Privacy Act obligations apply regardless of turnover.

Source: AUSTRAC — AML/CTF reform

How WattleDB Helps

Accounting SaaS platforms on WattleDB keep TFN data, financial records, and client files on Australian-owned infrastructure. No US entity can compel access to your clients' tax records. With 7-year retention requirements under AML/CTF, having a sovereign database you control — not one owned by a Silicon Valley company — is a compliance fundamental.

🏠

Real Estate & PropertyAgents, property managers — tenant data, applications, identity documents

Real estate agents collect identity documents, financial statements, employment details, and rental histories from tenants. From 1 July 2026, real estate agents come under the Privacy Act through AML/CTF reforms, regardless of their turnover.

The OAIC launched a compliance sweep in January 2026, conducting targeted reviews of real estate agents' privacy policies. Agencies using AI tools for tenant screening or automated application processing must disclose this by 10 December 2026 under the new ADM transparency obligations. AI-powered decisions on tenancy applications must clearly disclose what personal data is used and which decisions are made entirely by AI.

Privacy breaches now carry penalties of up to $660,000 for non-compliance and up to $66,000 for non-compliant privacy policies under the new infringement notice regime.

OAIC Compliance Sweep (Jan 2026)

Targeted review of real estate agents' privacy policies. Non-compliant policies face up to $66,000 in infringement notices.

Source: OAIC — Privacy compliance sweep announcement

AML/CTF Obligations (Jul 2026)

Real estate agents become reporting entities under AML/CTF reforms, bringing full Privacy Act obligations regardless of turnover.

Source: AUSTRAC — AML/CTF Tranche 2 reforms

How WattleDB Helps

PropTech platforms on WattleDB store tenant applications, identity documents, and financial records on Australian-owned infrastructure. With OAIC actively auditing real estate privacy practices, having a sovereign backend removes the jurisdictional risk entirely. No need to prove a US provider will comply with Australian privacy law — WattleDB is already under it.

👴

Aged CareResidential care, home care — client health data, care plans

The Aged Care Act 2024 and the Aged Care Rules 2025 now govern data handling in the sector. The Act imposes three critical obligations: use personal information solely for providing aged care, do not disclose without written consent (except when necessary for care), and safeguard information with reasonable security measures.

Aged care providers handle health information, care plans, medication records, and financial details of vulnerable Australians. The sector achieved only 87% compliance with information management and privacy standards in 2026, indicating systemic challenges with data protection.

The Aged Care Quality and Safety Commission oversees compliance and can impose sanctions on providers who fail to meet standards. Privacy Act obligations apply fully to aged care providers — these are health service providers and have never been exempt.

Aged Care Act 2024

Personal information must be used solely for aged care purposes. Disclosure requires written consent. Reasonable security measures are mandatory.

Source: Federal Register of Legislation — Aged Care Act 2024

Quality & Safety Commission

Only 87% compliance with privacy standards in 2026. Commission can impose sanctions including revoking provider registration.

Source: Aged Care Quality and Safety Commission

How WattleDB Helps

Aged care management platforms on WattleDB keep care plans, medication records, and client health data on Australian-owned infrastructure. For a sector already struggling with 87% privacy compliance, removing the jurisdictional complexity of US-owned cloud providers is a straightforward step toward better compliance outcomes.

🛒

Retail & HospitalityCustomer loyalty, POS data, booking systems, food safety records

Australian retail and hospitality businesses increasingly collect customer data through loyalty programs, online ordering, booking platforms, and POS systems. Currently, businesses under $3M turnover are exempt from the Privacy Act — but this exemption is expected to be removed by December 2026. An estimated 2.5 million businesses will need to comply.

Over 80% of Australian retail leaders consider loyalty strategies important over the next 12-18 months. These programs collect purchase histories, dietary preferences, contact details, and payment information. Under the APPs, businesses must publish an up-to-date privacy policy explaining what data is collected, why, how long it's kept, who it's shared with, and how customers can access or correct their data.

As third-party cookies phase out, first-party data from loyalty programs and in-store interactions becomes the primary source for personalisation. This makes Australian-hosted data storage not just a compliance issue but a competitive asset — customers increasingly value knowing their data stays local.

Small Business Exemption Removal

Expected December 2026. All businesses, regardless of turnover, will need to comply with the Privacy Act and APPs. Affects ~2.5M businesses.

Source: Attorney General's Department — Privacy reform

APP Obligations for Loyalty Programs

Clear consent, transparent privacy policies, purpose limitation, data minimisation, and secure storage required for customer data collection.

Source: OAIC — Australian Privacy Principles guidance

How WattleDB Helps

Retail and hospitality SaaS platforms on WattleDB — POS systems, loyalty programs, booking engines — can tell merchants their customer data stays in Australia on Australian-owned infrastructure. When the small business exemption drops, having sovereign data storage is one less compliance headache for every café, restaurant, and retailer in the country.

💳

FinTech & InsurTechBanking, payments, lending, insurance — APRA-regulated data

Financial services operate under the strictest regulatory scrutiny in Australia. APRA CPS 234 requires APRA-regulated entities to maintain information security capabilities commensurate with the threats they face. This extends to third-party service providers — including cloud and backend infrastructure. APRA expects entities to assess and manage risks associated with outsourcing to foreign jurisdictions.

FinTech companies building lending platforms, payment systems, or insurance products handle financial data, identity documents, credit histories, and transaction records. Under the Privacy Act, credit reporting information has specific protections under Part IIIA, with strict rules on access, use, and disclosure.

Enterprise clients and government agencies increasingly require 100% Australian jurisdictional control in RFPs. A US-owned backend is a disqualifying factor for many government and enterprise procurement processes in the financial sector.

APRA CPS 234

Information security standard for APRA-regulated entities. Extends to third-party providers including cloud infrastructure. Jurisdictional risk must be assessed.

Source: APRA — Prudential Standard CPS 234

Privacy Act Part IIIA — Credit Reporting

Specific protections for credit reporting information including strict access, use, and disclosure rules.

Source: Privacy Act 1988 (Cth) — Part IIIA

How WattleDB Helps

WattleDB is built for the compliance demands of financial services. 100% Australian-owned entity, ISM-aligned controls, architected for IRAP assessment. No CLOUD Act exposure means no jurisdictional risk to flag in your APRA CPS 234 assessment. Win RFPs that require sovereign infrastructure.

🏛️

GovTech & DefenceGovernment agencies, contractors — PROTECTED-level data

The Whole-of-Government Cloud Computing Policy (issued December 2025, effective 1 July 2026) mandates cloud-first for all new federal digital and ICT initiatives. Agencies must use infrastructure hosted in certified, sovereignty-compliant facilities. The DTA Hosting Certification Framework sets the standards for government data hosting.

GovTech contractors building applications for government agencies must align with the Protective Security Policy Framework (PSPF) and the Information Security Manual (ISM). For sensitive government data, infrastructure must be assessed under the Infosec Registered Assessors Program (IRAP).

IRAP is not a certification — it's a risk-based assessment framework run by the ACSC. WattleDB's infrastructure is designed from the ground up to align with ISM controls, making the path to a successful IRAP assessment at PROTECTED level substantially shorter.

Cloud Computing Policy (Jul 2026)

Cloud-first mandate for all new federal digital initiatives. Sovereignty-compliant infrastructure required.

Source: DTA — Cloud Computing Policy, December 2025

IRAP & ISM Controls

Risk-based assessment framework by ACSC. Not a pass/fail certification. WattleDB architected for IRAP assessment at PROTECTED level.

Source: ACSC — IRAP program

How WattleDB Helps

WattleDB is architected for IRAP assessment with ISM-aligned controls. 100% Australian-owned entity, onshore-only support staff, no foreign parent company. Build government applications on infrastructure designed for the compliance requirements your agency clients demand.

Your Industry. Your Data. Australian Soil.

Whatever you build, whoever you serve — WattleDB keeps your users' data under Australian law, on Australian-owned infrastructure, with zero foreign jurisdiction exposure.

You're on the list! We'll be in touch.
Disclaimer: This page provides general information about Australian regulatory requirements as of June 2026 and does not constitute legal advice. Regulatory frameworks evolve and individual circumstances vary. Consult a qualified legal professional for advice specific to your situation. References to legislation, penalties, and regulatory bodies are based on publicly available government sources and may be subject to change.