Lesson 5: Handle data through its lifecycle
You will be able to: apply minimization, purpose limitation, and retention to a feature, and trace a deletion request through every place the data lives.
About 4 min
Personal data has a life cycle: collect → use → share → store → retain → delete. Privacy laws attach obligations to each stage. The GDPR states them as principles, and the same ideas appear in many other privacy laws:
- Purpose limitation: collect data for specified, explicit purposes, and do not reuse it for something incompatible.
- Data minimisation: collect only what is adequate, relevant, and necessary for that purpose.
- Storage limitation: keep identifiable data no longer than the purpose requires.
- Data protection by design and by default: build these limits into the system, rather than relying on people to apply them.
People can ask for a copy of their data or for it to be erased. Under the GDPR, controllers must respond without undue delay and within one month; that can be extended by two further months for complex or numerous requests. Erasure is not absolute: data that must be kept to meet a legal obligation, for example, can be retained. Other laws set different timelines and exceptions.
Exercise 1 of 2: Configure the referral feature
Brightwell is launching referrals. A patient enters a friend’s email address; Brightwell sends one invitation; if the friend signs up, the referrer gets a booking credit. Brightwell’s legal team has determined that credit transactions must be kept for seven years to meet tax record-keeping obligations.
Choose a setting for each item, based on the stated purpose and requirements.
Collection and use
A referrer asks Brightwell to delete their account
Choose how the deletion is handled in each place the referrer’s data lives.
Apply it 2 of 2: A request for a copy
A patient asks Brightwell for a copy of their personal data. The support console has an export button, but it only covers the primary database.
Is the console export a complete response?
Key points
- Collect only what a stated purpose needs, and do not reuse it for unrelated purposes.
- Every store needs a retention rule, including logs, analytics, backups, and warehouses.
- Deletion has to reach every copy, or be documented where it cannot (for example, backups that expire on schedule).
- Legal retention obligations can override erasure; keep only what the obligation requires.