Queensland government agencies1 must handle personal information in compliance with the privacy principles2 in the Information Privacy Act 2009 (Qld) (IP Act). A privacy breach occurs when an agency fails to comply with one or more of the privacy principles.
Privacy breaches can result from technical issues, human error, inadequate policies and training, a misunderstanding of the law, or deliberate acts. One of the more common causes of a breach is the loss, theft, or mistaken disclosure of personal information is lost, stolen, or mistakenly disclosed (for example, a USB flash drive is lost or an email is sent to unintended recipients).
This guideline will help agencies manage a privacy breach, including whether to notify individuals whose privacy may have been affected by the breach. A self-assessment tool is also available to guide agency employees through what to do if they believe they have identified a potential privacy breach.
Privacy breach notification obligations
While the IP Act does not impose a mandatory obligation on agencies to notify the Office of the Information Commissioner (OIC) or affected individuals in the event of a privacy breach, agencies are strongly encouraged to notify OIC. Not only can OIC provide advice on responding to the breach, notification also assists OIC to respond to community enquiries about the breach.
Notifying the OIC
Agencies can report data breaches to the OIC by completing an online privacy breach report. There is more information on our privacy breach page.
OIC also strongly encourages agencies to notify affected individuals in appropriate circumstances. Doing so is good privacy practice and promotes openness and transparency.
Mandatory data breach notification
Agencies may be subject to mandatory data breach notification obligations, such as the information security incident reporting requirements under the Queensland Government Enterprise Architecture (QGEA), the Commonwealth Notifiable Data Breaches (NDB) scheme, or the My Health Records Act 2012 (Cth).
Agencies may need to seek legal advice about applicable laws or schemes, and/or their requirements.
Agencies may also be subject to additional mandatory data breach notification obligations through other legislative requirements, such as the information security incident reporting requirements under the Queensland Government Enterprise Architecture (QGEA), the Commonwealth Notifiable Data Breaches (NDB) scheme and the My Health Records Act 2012 (Cth).
Agencies may need to seek legal advice about applicable laws or schemes, and/or their requirements.
There are four key steps in responding to a privacy breach:
Each step is detailed below. Where possible, the first three steps should be undertaken concurrently. The last step includes longer-term solutions and prevention strategies.
Take whatever steps possible to contain the breach and minimise any resulting damage. For example, recover the personal information, shut down the system that has been breached, suspend the activity that lead to the privacy breach, revoke or change access codes or passwords.
If a third party is in possession of the personal information and declines to return it, it may be necessary to seek legal advice on what action can be taken to recover the information. When recovering information, ensure copies have not been made or that all copies are recovered.
Be careful when containing the breach not to destroy information that may be needed to investigate the cause of the breach.
Escalate the matter internally as appropriate. Senior management responsible for the area where the breach occurred should immediately be informed of the breach. Depending on the breach's circumstances, it may also be appropriate to inform the media relations unit, the legal services area, the information security manager, the business unit responsible for managing matters of employee misconduct (such as internal audit, ethical standards or Crime and Corruption Commission liaison officer), and/or Director-General and/or Ministerial liaison unit.
The agency’s privacy contact officer should be informed of all breaches. This officer can provide advice on the application and interpretation of the IP Act and assist in responding to public inquiries about, and managing any complaints that result from, the breach.
Reporting all privacy breaches to a designated position will also support an agency to maintain a central log of breaches that can be used to identify training opportunities or improvements to information handling practices.
In some circumstances, it may be appropriate or necessary to notify a third party of the breach, for example:
Depending on the circumstances of the breach and the information involved, other notifications may be appropriate, such as:
The Australian Tax Office also has advice about protective measures for individuals following a data breach.
To identify other appropriate actions, assess the type of personal information involved in the breach and the risks associated with the breach. Factors to consider include:
Agencies can use the Privacy Breach Self Assessment Tool to assist in assessing the risk of harm to individuals as a result of a privacy breach.
The IP Act does not specifically require an agency to notify individuals who have been affected by a privacy breach. However, a failure to notify may compound the damage for the individuals affected by the breach and reflect negatively on an agency’s reputation. Notification can also demonstrate a commitment to open and transparent governance.
In general, if a data breach creates a risk of harm to an individual, the affected individuals should be notified. Prompt notification in these cases can help mitigate the damage by enabling individuals to take steps to protect themselves.
There are occasions where notification can be counter-productive. For example, notifying individuals about a privacy breach which is unlikely to result in an adverse outcome for the individual may cause unnecessary anxiety and de-sensitise individuals to a significant privacy breach.
Factors to consider when deciding whether notification is appropriate include:
A staff member transfers agency information onto a memory stick so that they can work on some files at home. At some point between leaving work and arriving home, the staff member loses the memory stick. They report it missing the next day.
The agency checks with the lost property section of the bus company but the memory stick was not handed in. The staff member advises that the memory stick contains the names, phone numbers and email addresses of about 100 members of the public who are participating in a community consultation project lead by the agency, and includes email correspondence from these individuals.
The data on the memory stick is protected by encryption software. The agency confirms with its IT service area that even if the memory stick were to be found, the data on the memory stick is inaccessible without the proper key to decrypt the information. The agency decides that notifying the individuals whose personal information was held on the memory stick is not warranted.
A paper file containing the records of 50 employees is left in a café. The information included the names, home addresses, phone numbers, birth dates, salary information and bank account numbers. Enquiries with the café fail to locate the whereabouts of the file.
The agency decides to notify employees of the breach due to the potential risk of identity theft.
A senior manager emails the affected staff members to notify them of the breach. In the notification, the manager offers an apology, explains personal information was involved, and directs the employees to resources that set out the key signs of identity theft and what steps to take if affected. The manager also outlines what measures have been put in place to prevent any recurrences of the breach. Staff are informed of their right to make a privacy complaint to the agency, including information on the option of bringing their complaint to the OIC should they be dissatisfied with the subsequent response to their complaint.
The logistics of notifying affected individuals will depend in large part on the type and scale of the breach, as well as immediately practical issues such as having contact details for the affected individuals. Considerations include the following.
In general, individuals affected by the breach should be notified as soon as practicable. Circumstances where it may be appropriate to delay notification include where notification would compromise an investigation into the cause of the breach or reveal a software vulnerability.4
It is recommended that affected individuals be notified directly, eg by telephone, letter, email5 or in person. Indirect notification—eg by posting information on the agency’s website, placing a public notice in a newspaper, or by way of media release—should generally only be used where the contact information of affected individuals is not known, or where direct notification is prohibitively expensive or could cause further harm (for example, by alerting a person who stole a laptop as to the value of the information on it).
Tailor the content of the notification advice to the circumstances of the particular breach. Content of a notification could include:
Where a risk of harm to the individual has been identified, agencies are strongly encouraged to also notify OIC.
Once the breach has been contained, the circumstances of the breach should be investigated to determine all relevant causes and identify short or long-term measures that can be taken prevent a reoccurrence.
Preventative actions could include a:
Following any breach, the agency should assess and evaluate how well the matter was handled. In some circumstances, preparing a documented breach response plan can assist an agency to respond to a breach in a timely manner and help mitigate potential harm to affected individuals.
The plan could set out contact details for appropriate staff to be notified in the event of a breach, clarify roles and responsibilities, and document processes which will assist the agency to contain the breach, coordinate an investigation and assess the need for breach notifications.
Current as at: February 3, 2022