Chapter 14 — Privacy foundations

Lesson map

Lesson 14 published. Map, example, EX040.

flowchart TD
  N0["Learning outcomes"]
  N1["14.1 Privacy principles"]
  N2["14.2 Member data"]
  N3["14.3 Privacy and staff trust"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX040"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["14.1 Privacy principles"]
  N2["14.2 Member data"]
  N3["14.3 Privacy and staff trust"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX040"]

[Learning outcomes]
    |
    v
[14.1 Privacy principles]
    |
    v
[14.2 Member data]
    |
    v
[14.3 Privacy and staff trust]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX040]

Learning outcomes

You will (1) explain core privacy principles; (2) apply them to member data at a library; (3) connect privacy to staff trust in security programmes.

14.1 Privacy principles

Privacy principles include purpose limitation, collecting data only for stated purposes; data minimisation; accuracy; storage limitation; and security of processing. Libraries hold sensitive information about what people read, so they have a strong tradition of protecting member privacy. Nadia learns that privacy and security overlap but differ: security protects data from unauthorised access, while privacy also limits what authorised people do with it. A system can be secure yet still misuse data if it collects or shares more than needed. Nadia reads the library's privacy policy.

14.2 Member data

Nadia reviews how Ashcombe handles member data requests. Phone callers sometimes ask whether a person is a member or what they borrowed. Staff are trained to refuse, but callers claiming to be police or relatives can be persuasive, using authority and urgency described by Cialdini. Nadia proposes a written procedure: never disclose member information by phone; refer formal requests to the privacy officer in writing. This removes the need for counter staff to judge credibility under pressure, which protects both members and staff.

14.3 Privacy and staff trust

Security programmes also collect data about staff, such as who reported or clicked. If staff believe this data will be used against them, they may stop reporting. Nadia argues that the same privacy principles should apply to staff data: collect only what is needed, report aggregates and do not use simulation results for discipline. Respecting staff privacy builds the trust that makes people willing to admit mistakes quickly, which is often the most valuable security behaviour after an incident. Managers discuss it.

Worked example

Nadia explains privacy principles, writes a no-phone-disclosure procedure and applies privacy to staff security data.

Synthetic case. The procedure is synthetic; Cialdini (2021) is real.

Errors and limits

Procedures may delay genuine urgent requests. Aggregates can still reveal individuals in small groups.

Exercises

• EX040 — Privacy versus security. How does privacy differ from security?
  Show marking criteria

  Rubric: 3 = privacy also limits what authorised people do with data;; 2 = use limits;; 1 = vague;; 0 = none.
• EX041 — Phone procedure. What does the new procedure require?
  Show marking criteria

  Rubric: 3 = no disclosure by phone and written requests to the privacy officer;; 2 = written;; 1 = vague;; 0 = none.
• EX042 — Staff data. Why apply privacy principles to staff data?
  Show marking criteria

  Rubric: 3 = to keep the trust that supports reporting;; 2 = trust;; 1 = vague;; 0 = none.

Synthesis

Privacy protects members and staff, and procedures remove pressure from counter staff.

Continue studying — chapter 14 of 40

← Chapter 13 (draft) · Course chapter index · Chapter 15 (draft) →