Appropriate handling of information about people, including its collection, use and sharing.
2
New cards
Security
Protecting systems and data against unauthorised access, damage, loss or alteration.
3
New cards
Ethics
Principles used to decide whether an action is fair, responsible and respectful.
4
New cards
Can a system have strong security but poor privacy?
Yes. It might securely store far more personal data than it actually needs.
5
New cards
Does legal automatically mean ethical?
No. An action may be legal but still unfair, misleading or harmful.
6
New cards
Can an action breach school rules without breaking a law?
Yes. For example, using AI in a way forbidden by an assessment policy.
7
New cards
Personal information
Information about an identified person or someone who can reasonably be identified.
8
New cards
Examples of personal information
Name, address, phone number, email, identifiable images, student results, linked location history or online activity.
9
New cards
Sensitive information
A particular category of personal information receiving additional protection, such as health information, religious beliefs or racial or ethnic origin.
10
New cards
Is a password legally classified as sensitive information automatically?
No. It still requires strong protection, but is not automatically sensitive information in this legal sense.
11
New cards
How can separate data identify someone?
Combining details such as year group, birth date, suburb and sporting team may identify a person.
12
New cards
De-identification
Reducing the ability to connect data to an individual.
13
New cards
Is removing names enough to de-identify data?
Not always. Other details can be combined to identify someone.
14
New cards
Scenario: A report names a student's suburb, year group and team but not their name. What is the risk?
The combined details could identify the student; removing names alone may not de-identify the data.
15
New cards
How do users provide data to digital systems?
Forms, uploads, permissions for location/camera/contacts, searches, browsing, shopping and interactions.
16
New cards
What data can systems collect automatically?
Device details, activity logs and location data.
17
New cards
Cookies
Small pieces of data stored by a website in a browser; they can remember logins or carts and may support tracking.
18
New cards
Metadata
Data describing other data, such as when and where a photograph was taken.
19
New cards
Profiling
Using data to infer a person's interests, habits or likely behaviour.
20
New cards
Benefit and risk of location access
Benefit: navigation and nearby services. Risk: revealing movements or routines.
21
New cards
Benefit and risk of learning analytics
Benefit: identifying students needing support. Risk: incorrect labels or unnecessary monitoring.
22
New cards
Benefit and risk of personalised recommendations
Benefit: relevant content. Risk: manipulation or a narrow range of viewpoints.
23
New cards
Benefit and risk of targeted advertising
Benefit: relevant ads. Risk: intrusive profiling or exploiting vulnerabilities.
24
New cards
How can you judge whether data collection is reasonable?
Ask whether the amount of data collected is necessary for the service provided.
25
New cards
Scenario: A calculator app requests location access. What should you question?
Whether location data is necessary for the calculator's purpose.
26
New cards
Consent
Agreement to a particular handling of information.
27
New cards
What are the four features of valid consent?
Informed, voluntary, current and specific, and given by someone with capacity.
28
New cards
Informed consent
The person understands what is proposed.
29
New cards
Voluntary consent
The person has a meaningful choice.
30
New cards
Current and specific consent
The agreement relates to a particular use and is relevant to that use.
31
New cards
Consent given by someone with capacity
The person can understand and communicate the decision.
32
New cards
Does clicking "I agree" automatically prove meaningful consent?
No. The person may not understand the request or have a meaningful choice.
33
New cards
Is consent required for every collection of ordinary personal information?
No. Requirements depend on the circumstances and applicable law.
34
New cards
When is consent generally required for sensitive information?
Generally, subject to legal exceptions.
35
New cards
Transparency
Clearly explaining what a system does with information.
36
New cards
What should a privacy notice explain?
What is collected, why, how it is used/shared, how to access/correct it and how to raise concerns.
37
New cards
Scenario: A school app needs a name for attendance but also requests advertiser sharing. What is the ethical response?
Separate the choices and clearly explain advertising use; do not imply it is necessary for attendance.
38
New cards
What is the Privacy Act 1988?
An Australian law that includes 13 Australian Privacy Principles (APPs).
39
New cards
Do the APPs automatically apply to every organisation and individual?
No. They apply to organisations and agencies covered by the Privacy Act, subject to its rules.
40
New cards
Why can unnecessary collection increase risk?
More personal information is exposed if the system is compromised.
41
New cards
What four parts should an APP scenario answer include?
Identify the issue, link a relevant APP, explain the impact and recommend a specific improvement.
42
New cards
When applying APPs, what should you check about transparency?
Whether users can understand the privacy information.
43
New cards
When applying APPs, what should you check about collection?
Whether the system requests unnecessary information.
44
New cards
When applying APPs, what should you check about notification?
Whether users are told what is collected and why.
45
New cards
When applying APPs, what should you check about use and sharing?
Whether information is used and shared for an appropriate purpose.
46
New cards
When applying APPs, what should you check about accuracy?
Whether incorrect records could cause harm.
47
New cards
When applying APPs, what should you check about protection?
Who can access the information and how it is protected.
48
New cards
When applying APPs, what should you check about retention?
Whether information is kept longer than needed.
49
New cards
When applying APPs, what should you check about user control?
Whether people can access and correct their records.
50
New cards
Digital footprint
The trail of information created through digital activity.
51
New cards
Active digital footprint
Information you deliberately provide or publish, such as posts, comments, photos and registration details.
52
New cards
Passive digital footprint
Information recorded during activity, sometimes without you noticing, such as browsing logs or automatic location data.
53
New cards
How can other people affect your digital footprint?
They can post photographs, tag you or share information about you.
54
New cards
Why do digital footprints matter?
They can affect safety, privacy, reputation, relationships, future study or work, and the content or ads shown to you.
55
New cards
Does deleting a post guarantee it is gone?
No. Copies, screenshots or records may remain.
56
New cards
How can you manage your digital footprint?
Review privacy settings, limit permissions, avoid identifying details, ask before posting others, review old accounts and correct inaccurate information.
57
New cards
Scenario: A uniform photo, regular training location and weekly timetable are posted. What is the risk?
Combined information could reveal where someone is likely to be at particular times.
58
New cards
Vulnerability
A weakness that could be exploited or lead to harm.
59
New cards
Threat
Something capable of causing harm.
60
New cards
Risk
The likelihood of harm and its potential impact.
61
New cards
Scenario: A student reuses a password and someone steals it. Identify vulnerability, threat and risk.