Contents
An education app for schools has to do two things at once: genuinely improve learning and protect children's data as strictly as schools, parents and data protection authorities expect. Products that focus only on features usually fail at the approval stage with school authorities or data protection officers. This article shows how to plan privacy and pedagogy together from day one.
Who decides whether a school app is used?
School apps are rarely "just installed" by individual teachers. Several levels are usually involved: the head teacher, the school authority (in Germany often the municipality), the data protection officer and, depending on the federal state, guidance from the ministry of education. Parents of younger children have a say, and teachers have to actually use the app in class.
For vendors this means your product must not only convince students but also pass a review by administration and data protection. A complete privacy package – data processing agreement, records of processing activities, a description of technical and organisational measures – is often more important for sales than another feature.
Data protection in education apps: the ground rules
Student data deserves special protection. The GDPR explicitly emphasises the protection of children, and in a school context the school laws and data protection rules of the German federal states apply on top, with differences in the details. Typically the school or its authority is the controller and the app vendor the processor. The checklist below is guidance and does not replace a case-by-case review – it is not legal advice.
- Data minimisation: pseudonyms instead of real names where possible. No dates of birth, addresses or photos unless the function requires them.
- No advertising and no tracking through third-party SDKs. Analytics, if any, aggregated and self-hosted.
- Hosting in the EU, ideally in Germany, with clearly documented sub-processors.
- Role and permission model: teachers see their classes, students only their own data, parents only their child's.
- Deletion concept: data is automatically deleted or exported at the end of the school year or when a student changes school.
- Data protection impact assessment: check whether one is required, especially for performance data, learning analytics or AI features.
- Transparency: child-friendly, plain-language privacy information in addition to the formal notice.
If students use the app privately, the question of whether they can consent themselves may also arise; in Germany the age limit under Art. 8 GDPR for information society services is 16. Read more about requirements for young users in our article on child and youth protection in apps.
Pedagogy: what makes a good learning app
Many education apps do not fail on privacy but because they add no real value in class. Good learning apps follow a few pedagogical principles:
- Learning objective before feature: every exercise should map to a clear competency goal, ideally aligned with the curriculum.
- Immediate, constructive feedback: not just "wrong" but a hint why, followed by a suitable next task.
- Differentiation: tasks at several difficulty levels so weaker and stronger learners are challenged at the same time.
- Short units: exercises that fit into a few minutes can be built into lessons more flexibly.
- Teacher at the centre: teachers must be able to assign tasks, see progress and adapt content without lengthy training.
- Gamification in moderation: progress bars and badges motivate, but leaderboards can discourage weaker students.
Involve teachers from different school types early and test prototypes in real lessons. Many assumptions about usage do not survive classroom reality, for example Wi-Fi quality, device variety or the time available for logging in.
Technical requirements in everyday school life
| Requirement | Background | Solution |
|---|---|---|
| Fast login | Five minutes of login chaos costs half a lesson | QR-code login for classes, integration with existing school logins |
| Device variety | School tablets, private phones, older devices | Web app or cross-platform, light on resources |
| Weak Wi-Fi | Many devices on the same network at once | Preload content, offline mode, small payloads |
| Accessibility | Inclusive teaching, different needs | Screen reader support, scalable text, read-aloud function |
| Device management | School tablets are managed centrally | Support distribution via MDM, do not force private accounts |
Accessibility matters especially in education; our article on building accessible apps explains the technical side.
AI features in education apps: opportunities and limits
AI can explain tasks individually, give feedback on texts or help teachers create exercises. At the same time, its use in schools is sensitive: the EU AI Act classifies certain AI systems in education, for example those used to evaluate learning outcomes or decide on admission, as high-risk. Pure practice aids without an assessment function are usually less critical, but the line should be examined carefully. Proven practices include processing without real names, not using student input to train external models, teacher approval for generated content and clear labelling of AI answers.
Cost and approach
As a guide value, a learning app with exercises, a teacher dashboard and a solid privacy concept costs 15,000 to 50,000 € with 2 to 4 months of development. An MVP for a clearly scoped subject area is possible from around 5,000 to 15,000 € in 4 to 8 weeks. Platforms for many schools with interfaces to school management systems and AI features start at around 50,000 €. AI-assisted development reduces cost and time by up to 40 %. For learning apps outside schools, see our article on building a learning app. You can get a fixed-price offer after a free analysis through our offer wizard.
Agentic coding workshop for your team? From €799 net – request a quote by e-mailConclusion
Successful education apps for schools combine clear pedagogical value with a privacy concept that school authorities and data protection officers can accept without lengthy renegotiation. If you involve teachers early, minimise data and take classroom realities seriously, you create an app that is not only approved but used with pleasure.
Frequently Asked Questions
Who is the data controller for a school app?
Usually the school or school authority is the controller and the app vendor the processor, which requires a data processing agreement. Details depend on the federal state and use case; this article is not legal advice.
May education apps contain tracking or advertising?
For use in schools you should avoid both completely. Third-party advertising and tracking SDKs are hardly compatible with the expectations of schools and data protection authorities.
How much does an education app for schools cost?
As a guide value, an MVP costs 5,000 to 15,000 € and a full learning app with a teacher dashboard 15,000 to 50,000 €. Platforms with many interfaces start at around 50,000 €.
Are AI features allowed in school apps?
In principle yes, but AI used to assess learning performance may count as a high-risk system under the EU AI Act. Practice aids without an assessment function are usually less critical but should be implemented transparently and with minimal data.