GDPR compliance for university platforms is often reduced to a single issue: hosting servers in Germany. That is necessary—but not sufficient. A university running Canvas on EU servers is not automatically GDPR-compliant. And a university that uses learning activity data for an early warning system without documenting the legal basis for processing is in breach of the GDPR—regardless of where the servers are located.
This article provides a comprehensive overview of which data processing activities on learning platforms are relevant under data protection law, when a data protection impact assessment is mandatory, what the US CLOUD Act means for specific platform choices, what a data processing agreement must contain at a minimum—and how a university can involve its data protection officer in a structured way.
Which data processing activities on learning platforms are subject to the GDPR
In the context of university learning platforms, personal data encompasses far more than names and email addresses. It includes all data that can be linked to an individual—including usage patterns, learning progress data, communication content, examination data, and biometric data (e.g., in proctoring). Each of these processing activities requires its own legal basis.
| Data type | Examples | Risk level | Often overlooked? |
|---|---|---|---|
| Identification data | Name, student ID number, email | Standard | No |
| Learning activity data | Login times, page views, time spent in modules, click behavior | Elevated | Frequently |
| Examination data | Grades, exam attempts, timestamps, exam content | High | No |
| Communication data | Messages between instructors and students, forum posts | Increased | Frequently |
| Behavioral patterns / Profiles | Early warning system scores, aggregated activity profiles | High – special duty to verify | Very common |
| Biometric data | Facial recognition in proctoring, typing behavior analysis | Very high – Art. 9 GDPR | Partially |
| Device data | IP addresses, browser fingerprints, device type | Standard to elevated | Frequently |
Legal bases: What higher education institutions rely on to process data
Every processing activity requires a legal basis under Article 6 of the GDPR. In practice, three legal bases are particularly relevant for higher education institutions:
Art. 6(1)(b): Performance of a contract
Processing is necessary for the performance of the study contract (enrollment and examination regulations). This covers: identification data, examination data, and grade recording. It does not cover: behavioral profiles, early warning systems, or marketing analytics.
Art. 6(1)(e): Task carried out in the public interest
The most important legal basis for public higher education institutions to carry out their educational and research responsibilities. Permits a broad range of data processing, but requires a specific statutory basis in the higher education act or higher education data protection law of the relevant German federal state.
Art. 6(1)(a): Consent
For processing that goes beyond the scope of the study agreement—for example, voluntary use of additional apps, exam proctoring, or marketing communications. Important: Consent must be freely given—which can be problematic in an academic context if consent is effectively a prerequisite for taking exams.
Data protection law for public higher education institutions is not uniform across Germany—each federal state has its own provisions in its higher education act or data protection act. Private higher education institutions are subject to the general GDPR framework, without any special provisions specific to higher education. Data protection officers should be familiar with the current version of the applicable state law.
Data Protection Impact Assessment: When It Is Mandatory
A data protection impact assessment (DPIA) under Article 35 GDPR is mandatory where processing is likely to result in a high risk to the rights and freedoms of natural persons. For higher education institutions, this is mandatory in the following scenarios:
- Any form of proctoring (camera, microphone, behavioral analysis) – systematic monitoring of a vulnerable group (students)
- AI-based early warning systems that create behavioral profiles and predict study behavior
- Biometric processing to identify individuals (facial recognition for identity verification during exams)
- Extensive tracking of learning activities for purposes beyond documenting performance
Universities conduct data protection impact assessments for proctoring, but not for AI-based early warning systems—even though these exhibit structurally the same risk pattern: systematic monitoring of a vulnerable group’s behavior, with a profiling function. State data protection authorities have recently begun scrutinizing this area more closely.
Data Processing Agreement: What a DPA with Platform Providers Must Include
Anyone operating an external learning platform is a processor within the meaning of the GDPR. The higher education institution is the controller. A data processing agreement (DPA) pursuant to Article 28 GDPR is mandatory—without one, any processing is unlawful.
Minimum requirements for a legally compliant data processing agreement for educational platforms
- Subject matter and duration of processing precisely described
- Types of data and categories of data subjects fully listed (including learning activity data)
- Processor’s obligation to follow instructions: The platform provider may only process data in accordance with the university’s instructions
- Technical and organizational measures (TOMs) attached as an annex – detailing specific encryption standards, access controls, and a backup strategy
- Subprocessors: List of all third-party service providers (CDN, cloud infrastructure, support tools) and their server locations
- Deletion deadlines for all data categories after the contract ends
- Right to audit of the higher education institution (audit right)
- Reporting obligation in the event of data breaches (notify the university within 24 hours at the latest so that it can meet the 72-hour deadline for notifying the supervisory authority)
US CLOUD Act: What it means for Canvas, Blackboard, and Microsoft Teams
The US CLOUD Act (Clarifying Lawful Overseas Use of Data Act, 2018) empowers US authorities to require US companies to disclose data, regardless of where that data is stored. This also applies to US companies’ servers in the EU.
Canvas (Instructure), Blackboard (Anthology), and Microsoft Teams are US-based companies. Even if they operate European data centers, US authorities can demand access to data—and the EU GDPR cannot prevent this. For this reason, the Court of Justice of the European Union invalidated the Privacy Shield in 2020 (Schrems II). Its successor, the Data Privacy Framework (2023), mitigates the risk but does not eliminate it entirely.
What this means in practice
Higher education institutions have three options for responding to the CLOUD Act risk: switching to European providers without a US parent company (complete risk mitigation), consistently applying encryption with keys not held by the provider (technical risk mitigation), or formally accepting the risk and documenting the balancing of interests (only for low-risk processing). For examination data and biometric data, accepting the risk is not legally defensible.
German and European alternatives
Providers without a US parent company and with servers located in Germany are not subject to the CLOUD Act. FuxamOne is made in Germany: all data is processed exclusively on German servers, with no US ownership and a comprehensive data processing agreement.
Special requirements for students under 18
Some students at vocational schools and dual-study universities are minors. Stricter requirements apply to them: Article 8 GDPR governs consent for information society services offered to children (under 16 in Germany), for whom parental consent is required. No separate consent is needed for routine teaching and examination administration (Article 6(1)(b)/(e))—but transparency obligations must be met using age-appropriate language.
Communication Tools and Video Conferencing: GDPR Risks
Microsoft Teams, Zoom, and Google Meet were introduced at many universities as temporary solutions during the pandemic—and have remained in use. All three are provided by US companies and carry risks associated with the CLOUD Act. Universities that use these tools for communications involving sensitive personal data (oral examinations, counseling sessions) should have a documented risk assessment.
European-based alternatives: BigBlueButton (open source, self-hostable), Jitsi (open source), Whereby (Norwegian). For all of them, the hosting decision matters more from a data protection perspective than the choice of tool itself.
Vendor Due Diligence: What Universities Need to Check Before Choosing a Platform
A structured data privacy assessment should be conducted before choosing any platform. This questionnaire covers the key areas of risk:
- Is the provider a US company, or does it have a US parent company? (CLOUD Act risk)
- Where are the servers? (An EU server location is necessary, but not sufficient)
- Is a complete data processing agreement pursuant to Article 28 GDPR in place, including a list of subprocessors?
- Is there an up-to-date data protection impact assessment for high-risk processing activities?
- Is learning activity data used for the provider’s own purposes (product analytics, AI training)?
- Is there a comprehensive data deletion plan for when the contract ends?
- Is the provider's data protection officer accessible and responsive to inquiries?
- Is there an accessibility statement in accordance with BITV (if it is a public university)?
Frequently Asked Questions
No. Hosting servers in the EU is necessary, but not sufficient. Other crucial factors include the provider's ownership structure (US companies are subject to the CLOUD Act regardless of server location), complete data processing agreement documentation, purpose limitation for processing, and the chain of subprocessors.
A DPIA is mandatory for proctoring, AI-based early warning systems, biometric identification, and extensive behavioral tracking. For standard learning platforms without these features, it is recommended but not mandatory.
Yes, provided there is a documented legal basis (Article 6 GDPR), students are given transparent information, and no automated individual decision-making takes place (Article 22 GDPR). Notifying teaching staff is permitted; taking automatic action without human review is not.
Three steps: involve the data protection officer and document a formal risk assessment, press the provider for a contractual addendum (data processing agreement, technical and organizational measures), and evaluate GDPR-compliant alternatives in parallel. Continued use without documented risk assessment has liability implications.
Conclusion
GDPR compliance at universities is not a box-ticking exercise—it requires ongoing review of every data processing activity. Server location, a data processing agreement, and consent are minimum requirements, not guarantees. Universities choosing a platform today should ask not only what the system can do—but what it does with their students’ data.
FuxamOne is designed as a data protection-compliant system: servers located exclusively in Germany, no US ownership, a comprehensive data processing agreement pursuant to Article 28 of the GDPR, end-to-end encryption, and a transparent list of subprocessors.

