01. Recognize personal data
Professional objective : Data dictionary with classification rationale.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Classify ten fictional form fields by their ability to identify someone directly or indirectly.
- Check the result against this criterion: Pseudonymized data may still count as personal data.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Classify ten fictional form fields by their ability to identify someone directly or indirectly.
Reference answer and verification
Data dictionary with classification rationale. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Pseudonymized data may still count as personal data.
Expected output : Data dictionary with classification rationale.
Next chapter: reuse this output as the starting point for the next activity.
02. Purpose limitation and form minimization
Professional objective : Minimal form and field-by-field rationale.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Reduce a twelve-field fictional form to the fields needed for booking a workshop.
- Check the result against this criterion: Do not collect extra data merely in case it becomes useful.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Reduce a twelve-field fictional form to the fields needed for booking a workshop.
Reference answer and verification
Minimal form and field-by-field rationale. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Do not collect extra data merely in case it becomes useful.
Expected output : Minimal form and field-by-field rationale.
Next chapter: reuse this output as the starting point for the next activity.
03. Lawful bases and transparency
Professional objective : Privacy notice and legal-questions table.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Compare fictional processing activities and draft a short notice without treating consent as universally suitable.
- Check the result against this criterion: Choosing a lawful basis requires contextual legal review.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Compare fictional processing activities and draft a short notice without treating consent as universally suitable.
Reference answer and verification
Privacy notice and legal-questions table. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Choosing a lawful basis requires contextual legal review.
Expected output : Privacy notice and legal-questions table.
Next chapter: reuse this output as the starting point for the next activity.
04. Map the data lifecycle
Professional objective : Data-flow map and step owners.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Map collection, access, sharing, storage, archiving and deletion of a fictional registration.
- Check the result against this criterion: Account for overlooked copies and exports.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Map collection, access, sharing, storage, archiving and deletion of a fictional registration.
Reference answer and verification
Data-flow map and step owners. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Account for overlooked copies and exports.
Expected output : Data-flow map and step owners.
Next chapter: reuse this output as the starting point for the next activity.
05. Set retention periods
Professional objective : Retention schedule with deletion triggers.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Write a fictional retention schedule distinguishing operational need, possible obligations and deletion.
- Check the result against this criterion: Legal retention periods must be checked by jurisdiction and purpose.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Write a fictional retention schedule distinguishing operational need, possible obligations and deletion.
Reference answer and verification
Retention schedule with deletion triggers. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Legal retention periods must be checked by jurisdiction and purpose.
Expected output : Retention schedule with deletion triggers.
Next chapter: reuse this output as the starting point for the next activity.
06. Control access and confidentiality
Professional objective : Permission matrix and revocation procedure.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Assign role-based access to fictional participant records and plan revocation.
- Check the result against this criterion: Avoid unjustified public-link sharing.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Assign role-based access to fictional participant records and plan revocation.
Reference answer and verification
Permission matrix and revocation procedure. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Avoid unjustified public-link sharing.
Expected output : Permission matrix and revocation procedure.
Next chapter: reuse this output as the starting point for the next activity.
07. Handle individual rights
Professional objective : Request register and response templates.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Simulate access and correction requests using invented identities.
- Check the result against this criterion: Verify identity and applicable rules before disclosing records.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Simulate access and correction requests using invented identities.
Reference answer and verification
Request register and response templates. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Verify identity and applicable rules before disclosing records.
Expected output : Request register and response templates.
Next chapter: reuse this output as the starting point for the next activity.
08. Cookies, tracking and third parties
Professional objective : Tracker register and consent questions.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Inventory trackers for a fictional site and assess necessity without claiming automatic compliance.
- Check the result against this criterion: Consent obligations depend on context and implementation.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Inventory trackers for a fictional site and assess necessity without claiming automatic compliance.
Reference answer and verification
Tracker register and consent questions. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Consent obligations depend on context and implementation.
Expected output : Tracker register and consent questions.
Next chapter: reuse this output as the starting point for the next activity.
09. Processors and transfers
Professional objective : Provider review checklist.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Assess a fictional provider for access, location, subcontractors and deletion.
- Check the result against this criterion: Do not declare a transfer lawful without regulatory review.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Assess a fictional provider for access, location, subcontractors and deletion.
Reference answer and verification
Provider review checklist. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Do not declare a transfer lawful without regulatory review.
Expected output : Provider review checklist.
Next chapter: reuse this output as the starting point for the next activity.
10. Handle a privacy incident
Professional objective : Incident record and decision log.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Simulate loss of a USB drive with fictitious records; order containment, logging and escalation.
- Check the result against this criterion: Legal notification duties require a contextual assessment.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Simulate loss of a USB drive with fictitious records; order containment, logging and escalation.
Reference answer and verification
Incident record and decision log. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Legal notification duties require a contextual assessment.
Expected output : Incident record and decision log.
Next chapter: reuse this output as the starting point for the next activity.
11. Privacy risk and privacy by design
Professional objective : Annotated before/after and risk matrix.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Redesign a fictional form with data minimization, retention, access control and notices.
- Check the result against this criterion: A checklist is not a substitute for a required impact assessment.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Redesign a fictional form with data minimization, retention, access control and notices.
Reference answer and verification
Annotated before/after and risk matrix. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
A checklist is not a substitute for a required impact assessment.
Expected output : Annotated before/after and risk matrix.
Next chapter: reuse this output as the starting point for the next activity.
12. Final project: registration data governance
Professional objective : Governance dossier and improvement plan.
Fictional case study
A fictional cultural workshop collects event registrations. All participants and data are invented.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Deliver a data map, minimal form, notice, rights workflow, incident plan and supplier review.
- Check the result against this criterion: Obtain legal review before real-world deployment.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Deliver a data map, minimal form, notice, rights workflow, incident plan and supplier review.
Reference answer and verification
Governance dossier and improvement plan. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Obtain legal review before real-world deployment.
Expected output : Governance dossier and improvement plan.
Next chapter: reuse this output as the starting point for the next activity.
