GDPR for Schools: A Practical Data Protection Checklist
GDPR for schools and training centers made practical: legal bases, privacy notices, photo consent, minors, retention, access control, processors and data breaches.
In this article
GDPR for schools means that any school, language school, tutoring center or training provider processing personal data of students, parents or staff in the EU must have a legal basis for each use, inform people transparently, protect the data, keep it no longer than necessary and use service providers only under a proper contract. In practice, compliance comes down to a manageable checklist: know what data you hold and why, limit who can see it, decide how long you keep it and know what to do if something goes wrong. This guide walks through that checklist for course-based institutions.
In short
- Map your data first: which personal data you collect, for what purpose, where it is stored and who can access it.
- Most student data is processed to fulfill the enrollment contract or legal obligations. Consent is needed mainly for extras such as photos, videos and marketing.
- Give staff access only to what their role requires, set retention periods and sign data processing agreements with your software and service providers.
- Prepare for data breaches before they happen, because GDPR deadlines for notifying the authority are short.
Which data protection laws apply
The General Data Protection Regulation (GDPR) applies to organizations established in the EU and to organizations outside the EU that offer services to people in the EU. The United Kingdom applies its own UK GDPR, which follows the same principles. Size does not exempt you: a tutoring center with two teachers processes personal data just as a large school does, even if the scale of the measures differs.
Outside Europe, other laws apply. In the United States, for example, FERPA protects student education records at schools that receive funding from the US Department of Education, and other federal and state rules cover children's data online. Many other countries have comprehensive data protection laws of their own. The principles in this checklist, such as purpose limitation, transparency, security and retention, appear in most of them, so the checklist is a useful starting point wherever you operate.
Each EU country has a data protection supervisory authority that publishes guidance and handles complaints. Its website is the best source for national details, such as specific rules for minors or employee data.
Know your data and your legal bases
1. Map the personal data you process
List every type of personal data you hold, why you hold it, where it is stored and who has access. For a typical course provider, the list includes student contact details, parent or guardian contacts for minors, enrollment and course data, attendance, assignments and results, invoices and payments, messages and support requests, photos or videos and staff data. Many organizations are also required to keep a formal record of processing activities; even where you are not, this map is the basis for everything else.
2. Identify a legal basis for each purpose
The GDPR lists six legal bases for processing. For course providers, four matter most:
- Contract: data you need to deliver the course the student enrolled in, such as contact details, course assignment, attendance, results and billing.
- Legal obligation: data you must keep by law, such as invoices for tax purposes.
- Legitimate interests: purposes that are reasonable and expected, such as basic security measures, after weighing them against the person's interests.
- Consent: needed for purposes that are optional, such as publishing photos on social media or sending marketing newsletters to people who are not existing customers.
A common mistake is to ask for consent for everything. If you need the data to deliver the course, consent is the wrong basis, because a person could withdraw it at any time.
Inform people and handle consent properly
3. Provide a clear privacy notice
Students, parents and staff must be told what data you collect, why, on which legal basis, how long you keep it, who receives it and what rights they have. Give the privacy notice at enrollment, in plain language, and make it available in the student portal and on your website. If you teach children, write a version they can understand.
4. Photos, videos and minors
Photos and recordings of lessons, events and certificate ceremonies are where consent matters most. Ask separately for each use, such as the internal course channel, the website and social media, so people can agree to one and refuse another. Make withdrawing consent as easy as giving it, and keep a record of who consented to what.
For minors, involve parents or guardians. The age from which a young person can consent on their own differs between countries and contexts, so check your national rules. When in doubt, ask both the student and a parent.
If you record online lessons, inform participants beforehand, explain the purpose and who can watch the recording, and consider whether the purpose could be achieved without recording faces and voices.
5. Respect data subject rights
People can ask for access to their data, correction, deletion in certain cases, restriction of processing and a copy of the data they provided. Under the GDPR you generally have one month to respond. Prepare a short internal procedure, so a request does not cause panic when it arrives.
Protect, limit and delete
6. Control access by role
Teachers need their students' attendance and results, not their payment history. Office staff need invoices, not exam answers. Give each person access only to what their role requires, remove access promptly when staff leave and avoid shared logins. Use strong, unique passwords, and enable additional login protection wherever your tools offer it.
7. Limit what you collect and keep
Collect only what you need. A date of birth may be necessary for minors or certain certificates, but a full home address is not always needed for an online course. Set a retention period for each data type and delete or anonymize data when it expires. Invoices usually have to be kept for the period your tax law requires, while photos from a course two years ago probably do not.
8. Reduce copies and side channels
Student lists exported to personal laptops, class photos in private messaging apps and spreadsheets attached to emails are typical weak points. Keep personal data in your central system and avoid copies. Never paste students' personal data into public AI tools; our article on AI in education management explains why.
Processors, transfers and breaches
9. Sign data processing agreements
Software providers, email services, cloud storage and payment providers that process personal data on your behalf are processors. The GDPR requires a contract with each of them, usually called a data processing agreement, that sets out what they may do with the data and how they protect it. Ask for it before you import any personal data.
10. Check international transfers
If a provider stores or accesses data outside the EU and EEA, the transfer needs a legal mechanism, such as an adequacy decision for the destination country or standard contractual clauses. Ask your providers where data is hosted and which safeguards apply.
11. Prepare for data breaches
A data breach can be a lost laptop with student lists, an email sent to the wrong group or unauthorized access to an account. Under the GDPR, breaches that pose a risk to people must be reported to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of them. Serious breaches may also have to be communicated to the people affected. Decide in advance who assesses incidents, who reports them and how you document them, including incidents you decide not to report.
This article is general information, not legal advice. Data protection rules differ in detail between countries; check your specific situation with a qualified data protection expert or your supervisory authority.
Data types, legal bases and risks at a glance
| Data type | Typical legal basis | Retention hint | Risk |
|---|---|---|---|
| Student contact details | Contract | During enrollment, then as long as needed for follow-up obligations | Medium: misuse for marketing, accidental disclosure in group emails |
| Parent or guardian contact details | Contract or legitimate interests, depending on who is the contracting party | As long as the minor is enrolled | Medium: outdated contacts, sharing with the wrong person in custody situations |
| Attendance records | Contract, sometimes legal obligation for funded programs | As long as needed for certificates, billing or reporting duties | Low to medium, higher if reasons for absence include health details |
| Grades, exam results and assignments | Contract | Results needed for certificates may be kept longer; submitted work can usually be deleted sooner | Medium: sensitive for the student, must not be visible to classmates |
| Invoices and payments | Contract and legal obligation | As required by tax and accounting law | Medium to high: financial data, fraud risk |
| Photos and videos | Consent for publication; contract only where recording is essential to the course | Delete when the purpose ends or consent is withdrawn | High: especially for minors and once published online |
| Health or special needs information | Requires a specific condition for special category data, often explicit consent | Only as long as needed for the support provided | High: special category data with stricter rules |
Parent communication raises its own privacy questions, such as who may receive information about a student. Our guide to parent communication covers those situations.
How Zolinex supports data protection
Zolinex is built around role-based access with separate portals for administrators, teachers and students. Each user sees the information that belongs to their role: students, for example, see their own courses, attendance, invoices, payments and certificates. Keeping student records, documents, attendance, invoices and messages in one system reduces the spreadsheets, email attachments and messaging groups through which personal data most often leaks, and it gives you one place to look when someone asks what data you hold about them. Zolinex is operated by a company based in Wiesbaden, Germany; for questions about data processing, write to [email protected]. See all features.
Data protection is not a one-time project. Work through the checklist once, assign a person responsible and review it every year or whenever you add a new tool or process.
Frequently asked questions
Does GDPR apply to small tutoring centers and language schools?
Yes. The GDPR applies to any organization that processes personal data in the context of an establishment in the EU, or that offers services to people in the EU, regardless of size. A small tutoring center processes student contact details, attendance, results and payments, so it must have legal bases, inform people, protect the data and use processors under a contract. Measures can be proportionate to its size.
Do schools need consent to process student data under GDPR?
Not for everything. Data needed to deliver the course, such as contact details, attendance, results and billing, is usually processed on the basis of the contract or a legal obligation. Consent is mainly needed for optional purposes, such as publishing photos or videos and certain marketing. Asking for consent where another basis applies is a common mistake.
Can a school post photos of students on social media?
Generally only with consent that is specific to that use, informed and freely given, and can be withdrawn at any time. Ask separately for internal use, the website and social media. For minors, involve parents or guardians, as national rules on the age of consent differ. Delete photos when consent is withdrawn and keep a record of who agreed to what.
How long can a school keep student data?
Only as long as necessary for the purpose. Set a retention period per data type: invoices are usually kept as long as tax law requires, records needed to confirm certificates may be kept longer, while photos, submitted work and contact details of former students can often be deleted much sooner. Document the periods and delete or anonymize data on a regular schedule.
What should a school do after a data breach?
Contain the incident, assess the risk to the people affected and document what happened. Under the GDPR, breaches that pose a risk must be reported to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of them. If the risk is high, inform the affected people as well. Prepare these steps before an incident happens.