AI & DIGITAL SKILLS MAGAZINE Learn from beginner to expert
Contact EDITION 2026
ISHRAQA7 — The practical digital learning magazine
ISHRAQA 7 ACADEMY · Security & Future

Data protection: privacy, lifecycle and compliance

A fictional cultural workshop collects event registrations. All participants and data are invented.

  • LevelBeginner → Intermediate
  • Course programme12 modules
  • Course filesPDF · CSV · TXT · ZIP

Also available in العربية Français

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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Classify ten fictional form fields by their ability to identify someone directly or indirectly.
  3. Check the result against this criterion: Pseudonymized data may still count as personal data.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Reduce a twelve-field fictional form to the fields needed for booking a workshop.
  3. Check the result against this criterion: Do not collect extra data merely in case it becomes useful.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Compare fictional processing activities and draft a short notice without treating consent as universally suitable.
  3. Check the result against this criterion: Choosing a lawful basis requires contextual legal review.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Map collection, access, sharing, storage, archiving and deletion of a fictional registration.
  3. Check the result against this criterion: Account for overlooked copies and exports.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Write a fictional retention schedule distinguishing operational need, possible obligations and deletion.
  3. Check the result against this criterion: Legal retention periods must be checked by jurisdiction and purpose.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Assign role-based access to fictional participant records and plan revocation.
  3. Check the result against this criterion: Avoid unjustified public-link sharing.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Simulate access and correction requests using invented identities.
  3. Check the result against this criterion: Verify identity and applicable rules before disclosing records.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Inventory trackers for a fictional site and assess necessity without claiming automatic compliance.
  3. Check the result against this criterion: Consent obligations depend on context and implementation.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Assess a fictional provider for access, location, subcontractors and deletion.
  3. Check the result against this criterion: Do not declare a transfer lawful without regulatory review.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Simulate loss of a USB drive with fictitious records; order containment, logging and escalation.
  3. Check the result against this criterion: Legal notification duties require a contextual assessment.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Redesign a fictional form with data minimization, retention, access control and notices.
  3. Check the result against this criterion: A checklist is not a substitute for a required impact assessment.
  4. 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

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Deliver a data map, minimal form, notice, rights workflow, incident plan and supplier review.
  3. Check the result against this criterion: Obtain legal review before real-world deployment.
  4. 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.

Check your knowledge

1. Recognize personal data
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
2. Purpose limitation and form minimization
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
3. Lawful bases and transparency
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
4. Map the data lifecycle
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
5. Set retention periods
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
6. Control access and confidentiality
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
7. Handle individual rights
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
8. Cookies, tracking and third parties
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
9. Processors and transfers
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
10. Handle a privacy incident
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
11. Privacy risk and privacy by design
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
12. Final project: registration data governance
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?

Glossary for this page

The key terms used in this content, each with a short definition.

personal data
Any information that can identify a person: name, phone, email, photo, file number…
workflow
The sequence of steps a task follows from start to finish, across people or apps.

Course files

Choose a language, then the format you need.

العربية

FileFormatSizeDownload
الدليل التعليمي PDF 45 KB Download — الدليل التعليمي (PDF)
دفتر التمارين PDF 39 KB Download — دفتر التمارين (PDF)
دليل التصحيح PDF 39 KB Download — دليل التصحيح (PDF)
المشروع النهائي PDF 22 KB Download — المشروع النهائي (PDF)
قائمة التحقق CSV 2 KB Download — قائمة التحقق (CSV)
بيانات افتراضية CSV 1 KB Download — بيانات افتراضية (CSV)
مراجع رسمية TXT 1 KB Download — مراجع رسمية (TXT)
حقيبة تدريب دون اتصال ZIP 2 KB Download — حقيبة تدريب دون اتصال (ZIP)

Français

FileFormatSizeDownload
Manuel pédagogique PDF 31 KB Download — Manuel pédagogique (PDF)
Cahier d’exercices PDF 26 KB Download — Cahier d’exercices (PDF)
Corrigés des exercices PDF 26 KB Download — Corrigés des exercices (PDF)
Projet final PDF 12 KB Download — Projet final (PDF)
Grille de contrôle CSV 2 KB Download — Grille de contrôle (CSV)
Données fictives CSV 1 KB Download — Données fictives (CSV)
Références officielles TXT 1 KB Download — Références officielles (TXT)
Kit pratique hors ligne ZIP 2 KB Download — Kit pratique hors ligne (ZIP)

English

FileFormatSizeDownload
Course manual PDF 28 KB Download — Course manual (PDF)
Practical workbook PDF 24 KB Download — Practical workbook (PDF)
Answer guide PDF 25 KB Download — Answer guide (PDF)
Final project PDF 12 KB Download — Final project (PDF)
Quality checklist CSV 1 KB Download — Quality checklist (CSV)
Fictional data CSV 1 KB Download — Fictional data (CSV)
Official references TXT 1 KB Download — Official references (TXT)
Offline practice kit ZIP 2 KB Download — Offline practice kit (ZIP)