Pupil data protection starts with clear management decisions about collection, purpose and access. Organise the review before relying on a supplier’s compliance badge.
Pupil records are a daily management responsibility
Registration forms, attendance lists, health notes, activity photographs and learning accounts move between many people and tools. A platform may be secured while a complete export is forwarded to a chat group or a former employee retains access. Protecting pupil information therefore begins with management decisions about collection, purpose and use.
This guide helps school leaders organise a review with staff and suppliers. It offers a data map, supplier questions, an incident exercise and a first-month plan. It does not certify a school’s compliance or replace legal assessment of its particular processing. Distinguish the organisational suggestions here from requirements that need formal verification.
Start with Morocco’s framework, then assess international connections
The starting reference is Morocco’s Law 09-08 and CNDP guidance. It addresses purpose, proportionality, accuracy and retention, among other safeguards. Have each activity and its appropriate procedures assessed; a general signature cannot settle every use.
GDPR territorial scope requires an Article 3 assessment, including EU establishment connections or targeting people in the EU with services or monitoring their behaviour there. Website accessibility in Europe alone is insufficient. Nationality alone is not the test.
Do not conclude “exempt because we are in Morocco” or “compliant because our supplier is European”. Prepare the facts about the activity, people’s locations and each organisation’s role, then obtain appropriate assessment. Outcomes can differ between activities within one institution. Examining GDPR does not replace attention to Moroccan obligations.
Map where information starts and where it goes
Activity | Information to review | Where copies may exist | Management question |
|---|---|---|---|
Registration | Identity, contacts and required documents | Forms, email and paper | Are old form fields collected without a current need? |
Learning and assessment | Accounts, assignments and results | Platform and teacher exports | Who actually needs individual results? |
Attendance and transport | Presence records and contact arrangements | Apps, spreadsheets and groups | Does someone receive a full list when only a subset is needed? |
Support and health | Specific support information | Restricted files and separate notes | Is access separated according to the task? |
Communications and photographs | Images, newsletters and recipient lists | Website, social accounts and albums | Who reviews what will become public? |
Suppliers | Information sent to external services | Contracts, integrations and backups | What happens when the relationship ends? |
Start with system names and descriptions rather than copying pupil records into the map. An inventory should not become another exposed database containing all the details. Select one activity and ask its owner to describe the actual route, rather than the route a procedure manual assumes.
A 30-minute meeting to reveal forgotten copies
During the first 10 minutes, trace a fictional registration through to creation of a learning account. Ask where each item was transferred and who received it. During the next 10 minutes, each owner identifies a copy retained outside the main system. In the final 10 minutes, select 3 actions, each with an owner and due date.
Possible actions include replacing a complete list with task-specific information, reviewing a public sharing link or establishing a single document intake route. Do not delete records indiscriminately to reduce totals. Review operational needs, retention requirements and archiving arrangements before removal.
Build permissions around work
Replace “all staff need everything” with named tasks: registering pupils, correcting records, viewing one class’s results, responding to families and administering accounts. Ask owners to justify the fields their work requires. Viewing information does not necessarily require export or publication privileges.
Include the start and end of relationships: new employee, trainee, temporary cover, support supplier and departing staff member. One practical control is an access request naming the task, approver and review date. At departure, coordinate access removal and work handover without sharing passwords or destroying records that must be retained.
Ask suppliers about practice, beyond a badge
Role: what do they do for the school, and do they use information for other purposes?
Location: where are hosting, copies and support, and who can access information from elsewhere?
Other parties: which organisations receive information or support processing?
Control: can the school set permissions, disable an account and retrieve its information?
Retention: what happens to data, exports and backups at service termination?
Incidents: how will they alert the school, who communicates and what details are supplied?
Evidence: which written commitments and appropriate supporting evidence can be reviewed?
Have the required processing and international-transfer formalities assessed according to the facts. Server location or a “GDPR compliant” phrase cannot resolve that assessment. A free tool also warrants review if it receives real pupil information.
Notices and consent: clarity for each use
From a communication perspective, a family should be able to understand what the school does with information, whom to contact and what choices concern a particular use. Have wording, legal grounds and representation of minors checked appropriately. Do not assume consent is the only basis for every activity.
Discuss school administration, public activity photographs and uploading content to an AI tool separately. One vague form should not serve as the answer to all 3. Use fictional records for staff training rather than uploading named worksheets or individual notes merely to get a faster draft.
When a family submits a request
Provide an identified route that does not circulate through every messaging group. Record the date, request type, requester and follow-up owner. Verify authority proportionately. Do not send a complete file to the first address claiming to belong to a parent. Complex questions about representation should follow the school’s approved process.
Route the request to the appropriate person with the minimum necessary detail. Make the response understandable and record what was done and what requires legal review. Do not promise immediate blanket deletion without checking retention duties, and do not ignore a request merely because a supplier holds the information.
An incident exercise: a list sent to the wrong group
Use an entirely fictional list in a paper exercise. Ask who receives the alert, who limits sharing, where facts are recorded and who decides the appropriate communication to affected people and competent authorities. How would the school assess copies or downloads? Never send a real pupil list to test response speed.
The first organisational task is to contain further circulation and preserve an accurate account through an identified owner. Do not ask everyone to resend the file to prove receipt. Legal response and notification deadlines, where applicable, depend on the relevant framework and facts. A GDPR deadline should not be imported as an automatic rule for every Moroccan incident.
The first month: small, verifiable decisions
Week 1: map registration, name owners and identify 2 legal questions requiring answers.
Week 2: review one team’s access and sharing links, documenting approved changes.
Week 3: examine one supplier and one information notice with the appropriate reviewer.
Week 4: run an incident exercise and review completed actions and unresolved decisions.
Measure concrete progress: do we know who can export? Was an inappropriate link closed? Is a family request assigned to someone? Counts of forms or staff signatures should not become the sole evidence of protection. A documented operational decision is more useful than a slogan disconnected from practice.
Frequently asked questions
Does a European platform put the whole school under GDPR?
A supplier’s nationality does not settle that question. Assess activities, roles and territorial scope alongside relevant contracts and obligations.
Is a spreadsheet less sensitive than a platform?
The file type does not remove the sensitivity of its contents. Review access, circulation and copies regardless of the tool.
Is a general consent form sufficient?
Do not treat it as a universal answer. Examine purpose, legal grounds, information and the conditions of each use separately.
Does this guide prove our school complies?
No. It organises questions and work. Compliance assessment requires reviewing the school’s processing, documents and applicable rules.
Sources and editorial notes
Checked on 28 October 2026: Law 09-08 published by CNDP and EDPB Article 3 guidance. The table, exercises and monthly plan are original organisational proposals. Cyber Sqool supports a digital culture in which pupil protection informs everyday decisions; this article is not a legal audit or official accreditation.
