Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
In today’s digital economy, personal information flows through almost every Australian business. Whether you run an online store, a professional services firm, or a growing tech startup, customers expect you to handle their data carefully and lawfully.
That expectation is backed by law. Australia’s privacy framework sets clear rules for when you can collect personal information, how you must protect it, and what to do if something goes wrong. The good news is you don’t need to be a tech giant to get this right. With a clear plan, the right policies and some sensible practices, you can build customer trust and minimise risk.
This guide explains what “data protection and privacy” really mean for your business in Australia, when you need a Privacy Policy, the key laws to be aware of, and practical steps you can take today.
What Do “Data Protection” And “Privacy” Mean In Australia?
“Data protection” is about preventing personal information from misuse, loss, unauthorised access, modification or disclosure. In practice, it covers your processes, staff training and security controls (both technical and physical).
“Privacy” is about collecting, using and disclosing personal information fairly and transparently. It also covers how individuals can access and correct their information, and how you handle complaints.
In Australia, privacy is primarily governed by the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). These rules apply to “personal information” - anything that identifies, or could reasonably identify, an individual (for example, names, emails, phone numbers, addresses, payment details, IP addresses in some contexts, and health information).
Many everyday business activities fall within this scope: website contact forms, online orders, mailing lists, CRM notes, customer support records and employee files. If you’re collecting personal information, you need a lawful reason to collect it, you should only collect what you need, and you must keep it secure.
Do You Need A Privacy Policy In Australia?
This is a common question - and the answer depends on whether you’re an “APP entity” under the Privacy Act.
- Businesses and not-for-profits with annual turnover of more than $3 million are generally APP entities and must comply with the Privacy Act, including having a clearly expressed, up-to-date Privacy Policy (APP 1).
- Some small businesses under $3 million are also APP entities. This includes, for example, health service providers, businesses that trade in personal information, contractors providing services to the Commonwealth, credit reporting bodies and certain tax file number (TFN) handlers.
If you are an APP entity, you must publish an accessible Privacy Policy that explains your handling of personal information in plain English. Even if you fall outside the Privacy Act, many small businesses still choose to have a Privacy Policy to meet platform expectations (such as app stores or payment gateways), demonstrate transparency and align with customer expectations.
Put simply: if you collect personal information in the course of doing business, it’s wise to have a tailored, easy-to-read Privacy Policy and to actually follow it in practice.
What Laws And Rules Could Apply To Your Data Practices?
You’ll likely engage with more than one legal regime when handling customer and employee information. Here are the key frameworks to know about in Australia.
Privacy Act 1988 (Cth) and Australian Privacy Principles (APPs)
For APP entities, the APPs set the baseline for how you collect, use, disclose, store and destroy personal information. They also require a publicly available Privacy Policy and outline rights for individuals to access and correct their information.
Notifiable Data Breaches (NDB) Scheme
If you’re an APP entity and you experience an eligible data breach that is likely to result in serious harm (for example, a cyber incident exposing customer records), you must assess and notify affected individuals and the regulator. Having a practical, tested Data Breach Response Plan helps you move quickly and meet your obligations under the NDB scheme.
Australian Consumer Law (ACL)
The ACL prohibits misleading or deceptive conduct. If your public statements (including your Privacy Policy or marketing) say you protect data in a certain way, you need to actually do it. Overstating your security or privacy practices can be treated as misleading conduct.
Spam and Telemarketing Rules
Direct marketing by email, SMS and phone is regulated. You need consent, accurate sender identification and a working unsubscribe for commercial electronic messages under the Spam Act. For telemarketing, the Do Not Call Register rules also apply. Our overview of email marketing laws covers the essentials for compliant campaigns.
Sector-Specific Rules
Some industries have additional obligations - for example, health records legislation, credit reporting, financial services regulation, or child-related services. If you operate in one of these sectors, expect extra requirements beyond the general privacy framework.
International Considerations
If you target or serve customers in the European Union or the United Kingdom, the GDPR/UK GDPR may apply based on where the customer is located. These regimes have additional requirements (for example, expanded rights and stricter consent). Even where they don’t strictly apply, adopting best practice can future-proof your business as Australian law continues to evolve.
What Should A Privacy Policy Cover (And What’s Often Missed)?
A good Privacy Policy is clear, specific to your business model and easy for customers to find. If you’re an APP entity, your policy must set out certain details. Regardless of size, cover these practical points in plain English:
- What types of personal information you collect (customer, prospect, supplier and employee data, as relevant).
- How you collect information (web forms, checkout, phone, email, cookies/analytics, social sign-ins, in-person forms).
- Why you collect it and the primary uses (fulfilling orders, providing services, customer support, analytics, marketing where consented).
- When you disclose information to third parties (such as payment processors, logistics providers, IT vendors) and whether information is sent overseas.
- How you keep information secure and how long you retain it (including de‑identification or destruction practices where applicable).
- How individuals can access and correct their information, and how to make a privacy complaint.
Two additional documents help close common transparency gaps:
- Privacy Collection Notice provided at the point of collection (for example, near a form) to explain the specific purpose, any required disclosures and how to find your full policy.
- A concise Cookie Policy (or a section within your Privacy Policy) explaining use of cookies, analytics and advertising technologies. While not always legally mandated in Australia, a clear Cookie Policy improves transparency and aligns with platform expectations.
Finally, keep your policy accurate. Avoid copying a generic template that doesn’t reflect your systems. If you say you encrypt all data, or delete records after 30 days, make sure that’s true operationally.
Practical Steps To Protect Personal Data Day-To-Day
Strong privacy compliance isn’t just about documents - it’s about everyday behaviours and sensible controls. These actions will reduce risk and support compliance, no matter your size.
1) Collect Less, Keep It Only As Long As Needed
Only collect personal information you genuinely need to deliver your product or service. If you don’t need a date of birth or a full address, don’t ask for it. Set retention rules so old records are securely destroyed or de-identified when no longer required.
2) Map Your Data Flows
List what you collect, where it’s stored, who can access it and which systems or vendors receive it. This is critical for breach response and for keeping your Privacy Policy accurate. It also helps you spot unnecessary collection or risky practices.
3) Lock Down Access And Use Smart Security Basics
Use strong, unique passwords with multi‑factor authentication, and restrict access on a “need to know” basis. Keep software patched, encrypt portable devices where possible, and back up critical systems. An internal Information Security Policy sets clear rules for your team on passwords, devices, remote work and incident reporting.
4) Train Your Team
Privacy is a team sport. Run short onboarding and refresher training so staff know what personal information is, how to recognise phishing, and how to escalate incidents quickly. If you handle employee data, consider an Employee Privacy Handbook to set expectations.
5) Prepare For Incidents
Practice makes perfect. A quick tabletop exercise can test your escalation path, assess decision-making against the NDB scheme and clarify who communicates with customers and regulators. Keep contact details for your cyber insurer, IT support, and legal advisors handy in your Data Breach Response Plan.
6) Manage Your Vendors
Most businesses use cloud tools for payments, communications, CRM or storage. Review your suppliers’ security, know where data is hosted and ensure your contract covers privacy, confidentiality and breach notification. A tailored Data Processing Agreement can formalise those obligations, especially if data is processed overseas.
Marketing, Cookies And Overseas Services: How Do You Stay Compliant?
Marketing and growth tools are powerful - but they do affect your privacy obligations. Here are common scenarios and how to approach them.
Email And SMS Marketing
For commercial electronic messages, you need consent, identification and an easy unsubscribe. If you use lead magnets or referral programs, check how consent is captured and recorded. Make sure your database is cleansed regularly so opt-outs are honoured. Our overview of email marketing laws explains the key rules to follow.
Analytics, Tracking And Targeted Ads
Using analytics and ad pixels can involve collecting device data and creating profiles across services. Be transparent in your Privacy Policy and Cookie Policy about what you collect and why. If you enable cross‑site tracking or demographic features, explain that clearly and provide opt‑out pathways where available.
Storing Or Processing Data Overseas
If personal information is disclosed to overseas recipients (for example, your cloud provider hosts data outside Australia), the Privacy Act requires APP entities to take reasonable steps to ensure similar protections apply. Disclose the countries involved in your Privacy Policy where you can, and build appropriate vendor obligations into your contracts (this is where a Data Processing Agreement helps).
Data Retention And Deletion
Holding onto personal information longer than necessary can increase risk. Implement a schedule for routine deletion or de‑identification aligned with legal and operational needs. Treat backups and old exports with the same discipline you apply to live systems.
What Legal Documents And Policies Should You Consider?
Your documentation should match how your business actually works. At a minimum, consider these core documents and policies (and make sure they’re aligned):
- Privacy Policy: Explains what you collect, why you collect it, who you share it with, how you secure it and the rights individuals have. A tailored Privacy Policy is essential if you are an APP entity and recommended for most online businesses.
- Privacy Collection Notice: Short notice at the point of collection covering purpose, key disclosures and a link to your full policy. See Privacy Collection Notice.
- Data Breach Response Plan: Roles, steps and notification criteria so you can respond fast and meet NDB obligations if required. Keep your Data Breach Response Plan tested and current.
- Information Security Policy: Internal rules for passwords, devices, access control, incident reporting and acceptable use. A documented Information Security Policy supports training and accountability.
- Data Processing Agreement (DPA): Contract terms with processors or tech vendors that handle personal information, covering security, sub‑processors and breach notice. Use a Data Processing Agreement when appropriate.
- Cookie Policy: A concise explanation of cookies, analytics and advertising technologies you use, and how users can manage preferences. A clear Cookie Policy increases transparency and user trust.
- Website or App Terms: Set out acceptable use, your intellectual property, disclaimers and limits of liability. While not legally required in every case, robust Website Terms and Conditions are best practice for online businesses.
- Email Disclaimer (Optional): Useful for professional services to reinforce confidentiality and misdirection notices; see Email Disclaimer.
Not every business will need every document on day one, but most will benefit from several of these. The key is consistency: your policies, contracts and actual processes should all align.
Step-By-Step: How To Lift Your Privacy Compliance This Month
- Run a quick data audit: List the personal information you collect, where it lives, who can access it and which vendors touch it.
- Update your paperwork: Draft or refresh your Privacy Policy and collection notices so they reflect reality (not what you wish were true).
- Tighten access and backups: Implement multi‑factor authentication, review user permissions and ensure backups are secure and tested.
- Train your team: Run a short session on phishing, safe handling of personal information and incident escalation.
- Prepare for incidents: Put a practical Data Breach Response Plan in place and run a 30‑minute drill.
- Check your marketing settings: Confirm consent capture flows, unsubscribe behaviour and configure analytics/ad tools to align with your policies and the Spam Act rules.
- Review vendor contracts: Add privacy and security clauses or a Data Processing Agreement where third parties process personal information.
Key Takeaways
- Privacy in Australia is governed by the Privacy Act and APPs; many businesses over $3 million turnover - and certain small businesses - must have a clear, accurate Privacy Policy.
- Even if you’re not strictly covered, transparent privacy practices, a tailored policy and sensible security controls build customer trust and reduce risk.
- Compliance isn’t just a document on your website - day‑to‑day behaviours, staff training and vendor management matter just as much.
- The Notifiable Data Breaches scheme requires quick action and communication when a serious breach occurs, so a tested incident plan is essential.
- Direct marketing, cookies and overseas cloud services bring extra obligations - be clear about tracking, consent and cross‑border disclosures.
- Align your Privacy Policy, collection notices, contracts and actual processes so what you say publicly matches what you do in practice.
If you’d like a consultation on getting your business’ data protection and Privacy Policy right in Australia, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.








