This guideline is a companion to Undertaking a Privacy Impact Assessment. It is not a comprehensive guide to identifying or managing privacy risks arising out of a project. It outlines
The following tables outline areas of risk that should be considered and managed during a project or when an agency changes how it operates, and the related legislative sections.
QPP 2 | No consideration given to whether it's lawful and practical for people to interact anonymously or pseudonymously with the project. No system in place to facilitate anonymous or pseudonymous interaction. |
---|---|
QPP 3.1 | Collecting more personal information than needed, e.g. extra information not needed for the project or information which has nothing to do with the agency's functions/activities. |
QPP 3.3 | Collecting sensitive information without consent where QPP 3.4 doesn't apply. |
QPP 3.6 | Collecting personal information from someone other than the individual it is about where QPP 3.6(a) and (b) don't apply. |
QPP 4 | No system in place to identify and assess unsolicited personal information, e.g. included in free text fields or sent by email. |
QPP 5 | Not informing people of all the relevant matters listed in QPP 5.2. |
For more information refer to the collection of personal information guidelines.
QPP 6 | Using or disclosing personal information for a secondary purpose (i.e. for something other than why it was collected) without making sure it is permitted by QPP 6.1(a) or QPP 6.2. |
---|---|
Section 33 | Disclosing personal information out of Australia when not permitted by section 33. |
Chapter 2, part 3 | Not taking reasonable steps to bind contractors involved in the project to comply with the IP Act. |
Refer to Key privacy concepts – use and disclosure, Disclosing personal information out of Australia, Binding contractors to the IP Act and the QPP 6 guidelines.
QPP 10.1 | Not having systems in place to ensure that personal information collected by the project is accurate, up to date and complete. Note: This is primarily a risk when personal information is collected from someone else, instead of from the individual it is about. |
---|---|
QPP 10.2 | Not having systems in place to ensure that personal information used and disclosed by the project is accurate, up to date, complete and relevant to whatever is being done with it. |
QPP 11.1 | Security, systems, practices and access controls are not appropriate to protect personal information from misuse, interference or loss and from unauthorised access, modification or disclosure. Protections must consider both internal and external actors. |
QPP 11.2 | No systems in place to identify when personal information is no longer needed for any purpose and trigger an assessment about its retention or de-identification. |
Refer to QPP 10 – quality and accuracy of personal information and QPP 11 – security, deidentification and destruction of personal information.
QPP 1 | Not assessing whether the project must be included in the agency's QPP privacy policy. |
---|---|
Chapter 3A | No systems to identify data breaches arising from the project. No systems to inform internal stakeholders of data breaches and undertake mandatory data breach notification. |
Chapter 5 | No processes in place to manage privacy complaints arising out of the project. |
QPP 12&13 | Systems do not support or allow the extraction of personal information into a generic format, for example, a text file or PDF. Systems do not allow personal information to be easily updated by amendment or notation. Note: this is also an important requirement for meeting the agency's obligations under the Right to Information Act 2009 (Qld). |
Refer to the QPP 1 - Transparency and privacy policies, Mandatory notification of data breach, and QPP 12 and 13 – access and correction.
Physical security measures focus on physical access and control mechanisms, including:
Technical solutions focus on minimising privacy risk through technological measures, including through the:
Develop and put into practice policies or procedures that support privacy awareness and compliance with the privacy principles. This could include policies and procedures:
Current as at: July 1, 2025