If you run an online shop, you’re holding a lot of personal information, probably more than you think about day to day. Names, emails, delivery addresses and order histories are sitting in your store, your inbox and your mailing list. If any of that ends up in the wrong hands, you need to move quickly and keep a cool head, and having a plan already worked out makes those first few hours a lot less stressful.
Plenty of small business owners are surprised that the reporting rules can apply to them. Others go the other way and assume they have to report every incident, when they might not need to.
A data breach is when personal information is accessed or disclosed without permission, or lost. That could be your website getting hacked, someone on your team emailing the customer list to the wrong person, or a lost laptop. It could also be a supplier who stores your customer records getting breached themselves. It doesn’t have to be a cyber attack. Plain old human error is behind plenty of them.
Personal information covers more than people expect, too. Names and contact details, but also order records, payment details and anything else that identifies someone. If you’ve got a mailing list or customer accounts, you hold personal information. Your privacy policy should already say what you collect and why, and our guide to ecommerce law compliance covers that side of it.
Who has to report
The Notifiable Data Breaches scheme is in Part IIIC of the Privacy Act 1988 (Cth). It’s applied to breaches since 22 February 2018 and it’s overseen by the Office of the Australian Information Commissioner, the OAIC. It covers organisations that have to follow the Australian Privacy Principles, which includes businesses and not for profit organisations with annual turnover over $3 million.
If your turnover has been $3 million or less in every financial year since 2001, you’re generally exempt. But there are exceptions. According to the OAIC guidance on the Notifiable Data Breaches scheme, a small business is still covered if it provides a health service and holds health information, if it trades in personal information, or if it’s a credit reporting body. And if you hold tax file numbers, you have to follow the scheme for that information. If you’re not sure which side you’re on, get advice now, before anything goes wrong.
Even if you’re exempt, your customers will still expect you to do something. A breach can hurt trust no matter what the law says you have to do, and a lot of small businesses follow the same steps anyway because it’s good practice. State and territory privacy laws can also apply in some cases, and the rules can change over time.
What to do when it happens
The OAIC sets out the four steps for responding to a data breach: contain, assess, notify and review. The first three can happen at the same time or one straight after the other. Sometimes it’s right to tell the people affected straight away, before you’ve even finished assessing.
First, stop it getting worse. That might mean stopping whatever unauthorised activity is going on, shutting down a system, or getting back records that went to the wrong place. If shutting a system down isn’t practical, change who has access or fix the weak spot. Try not to destroy evidence while you’re doing it, because records of what happened will help you find the cause later.
Then find out as much as you can. What kind of information was involved, how did it happen and how far did it spread? Who might have it now, and what could they do with it? If there are reasonable grounds to suspect a notifiable breach, the law says you have to do a reasonable and prompt assessment, and take reasonable steps to finish it within 30 days of becoming aware of those grounds. The OAIC sees 30 days as the outer limit. It isn’t a target, so go faster if you can, and keep notes on any delays and why they happened.
Under the scheme, a breach is notifiable when three things are all true. Personal information has been accessed, disclosed or lost without authorisation. The breach is likely to cause serious harm to someone, and likely here means more probable than not. And you haven’t been able to prevent that harm with remedial action. If the law says you have to notify and you don’t, that’s treated as an interference with privacy under the Act.
Serious harm can mean identity theft, significant financial loss or threats to someone’s physical safety. It can also mean damage to their reputation or lost job and business opportunities. How sensitive the information is matters, and so does whether it was protected by something like strong encryption. In one OAIC example, strong encryption made it unlikely anyone could access the information, so notification wasn’t needed. Whether the security could be got around is part of the assessment though, so check what else was taken. In another OAIC example, a leaked mailing list of names, emails and suburbs did need notification because of the phishing risk.
If it’s notifiable, you have to send a statement to the Commissioner as soon as practicable. It includes your identity and contact details, a description of the breach, the kinds of information involved and the steps people should take in response. Then you tell the people affected. That can be everyone involved or only the ones at risk of serious harm. If neither of those is practical, you publish the statement on your website and take reasonable steps to get the word out.
Telling people means they can protect themselves. They can change passwords, keep an eye on their accounts and watch out for scam messages. But the OAIC also says that alerting people about a breach with little or no risk of harm can make them worry for nothing. Keep your message plain and factual. Say what happened, what information was involved and what you’re doing about it.
Once the urgent stuff is done, look at why it happened. The OAIC suggests working out the root cause, putting a prevention plan together and updating your policies and procedures. You might need to change staff training or look again at the suppliers involved. Explain any changes to your team, and write down what you changed and when, so you’ve got a record if anyone asks later. Keep a record of every incident and how you handled it too, even the ones you didn’t have to report.
Getting ready before anything happens
It’s much easier to plan for a breach before you’ve had one. Start by listing everywhere customer information lives, from your website and payment tools to spreadsheets and email. Only keep what you need and delete old records you don’t use anymore. Only give admin access to people who really need it. If you’re bootstrapping a business with minimal capital, this all costs you time and not much else.
Your website is often the way in for an attack. Keep plugins, themes and software up to date, and get rid of anything you don’t use. Go with a host and platform that make updates and backups easy. If you’re building a new site, our web design tips for beginners can help you plan the basics. It’s a lot easier to build security in at the start than to add it later.
Moving premises or changing systems is another risky time. Records get packed into boxes, devices change hands and people share passwords to keep things moving. Plan how customer data will be moved, stored and wiped. Our article on office relocation mistakes goes through other things that can go wrong during a move.
Then write a short response plan and keep it somewhere everyone can find it. It doesn’t need to be long. It might cover:
- who leads the response and who they report to
- how to contain the usual problems, like a hacked account or an email sent to the wrong person
- who to call for technical help
- how you’ll contact customers if you need to
- where you keep notes about each incident.
This is general information about Australian privacy law and isn’t legal advice. Laws and processes can be different between states and territories and they change over time. For advice about your own situation, talk to a qualified lawyer.
