Consumer messengers in school communication

In many schools, communication has long since moved to consumer messengers, often to WhatsApp: the class group with parents, the arrangement among staff, the sick note as a message in the morning. Most of what makes that awkward is not tied to any one country. Whoever runs the school stays answerable for school data, a consumer app is nobody's processor, health details in a class group reach thirty families instead of one office, and a private phone number handed to parents does not come back. Some jurisdictions have gone further and restricted the practice outright – in Germany, several state data protection authorities and education ministries have limited or prohibited the official use of consumer messengers – but a school does not need such a ruling to have a problem. This page sets out the questions that apply wherever you are, and what a school-run channel has to do instead.

Coming soon

  • GDPR-compliant
  • Hosted in Germany
  • Free for teachers

A product of SavePaper.work

Benefits

What a school needs instead

A channel the school manages

Responsibility for school data stays with the school. That only works when the accounts belong to the school and do not hang on a private phone line.

Roles instead of private numbers

Teachers write from their role. The private mobile number stays private, and availability has a beginning and an end again.

Sensitive details with the right role

A sick note goes to the school office, not to thirty families. In the EU and the UK, health details enjoy special protection under Article 9 GDPR; elsewhere the same detail is protected by other names.

Reachable for every family

Without a smartphone and with little of the school's language as well: browser access and multilingual texts mean nobody drops out of the class group.

How it works

How a school settles its communication routes

Before a new channel is introduced, a short stocktake pays off: who writes about what today, which of it is official, and which rule should apply to which occasion in future?

1 2 3 4
  1. 1

    Take stock first

    First gather what actually happens: class groups with parents, arrangements among staff, sick notes sent as messages. Without that picture, every rule is decided past the real practice and quietly worked around day to day.

  2. 2

    Check what binds your school

    Two sources answer this: whoever supervises your school on data protection, and whoever runs it. In Germany that means the state authority and the school's own data protection officer, and many states have published guidance specifically on messengers. Where no ruling exists, the general duties on the school as controller still decide the question.

  3. 3

    Settle on a channel

    Then comes the decision about where official messages will run in future: a channel the school manages, with roles instead of phone numbers and with a route for families without a smartphone.

  4. 4

    Put the rules in writing

    Finally the school records the outcome, usually in a communication policy. Where staff use is affected, an agreement with the staff body is often added on top – whether that is required, and in what form, depends on the employment law your school sits under.

In comparison

A school-managed channel and a private group

School-managed channel
Accounts and accessAccounts belong to the school, access ends with the role
AvailabilityA role instead of a number, within agreed hours
TraceabilityOfficial messages stay findable
Sensitive detailsA sick note is visible only to the role in charge
Private messenger group
Accounts and accessA private account the school does not manage
AvailabilityA private number, visible around the clock
TraceabilityThe history sits on private devices
Sensitive detailsThe whole group reads health details along
In detail

Messengers, data protection and school life

Why official use is delicate

Responsibility for school data lies with the school, not with the individual teacher, and that alone creates the difficulty. If communication runs through a private account, a service processes personal data without the school having set the framework for it: no processor contract, no commitment on where the servers are, in many cases processing outside the school's own jurisdiction, and no way to delete data later in a targeted manner. In the EU and the UK the contract in question is the one under Article 28 GDPR; elsewhere it has a different name and the gap is the same. Two further points are easily overlooked in daily life. Many messengers sync the phone's address book during setup, so numbers of people who know nothing about it travel along – a data minimisation problem in any regime. And even where content is encrypted end to end, metadata still arises about who wrote to whom and when.

The teacher's private number

Alongside data protection there is a second question, one about working life, and it needs no legal citation at all. Anyone writing from their own line hands their private number to parents and classes and will not get it back in a hurry. Messages arrive in the evening, at the weekend and during the holidays, the online status shows that someone could be reached right now, and an unanswered message easily turns into a reproach. Work and private life are hard to keep apart on the same device. Traceability comes on top: when a teacher leaves, the history leaves with them, and nobody can show later which arrangement was made when – which matters most in exactly the cases where it is asked, a safeguarding concern or a dispute with a family. A school-managed channel for parent communication hangs on a role rather than on a number, and access ends when the job ends.

Sick notes and health details

It becomes clearest with the sick note. That a child is ill is a health detail, and in a class group every family reads it; for schools in the EU and the UK, Article 9 GDPR puts exactly that category under stricter requirements, and school systems outside that area protect it under their own rules rather than not at all. What a school needs is therefore not a second chat but a channel in which a digital sick note reaches only the role in charge, in which a digital parent letter with a read receipt replaces the return slip, and in which separated guardians hold the same information. A parent portal bundles exactly that, including browser access for families without a smartphone and multilingual texts for families who speak little of the school's language. That is how SchuleVernetzt is built; which requirements apply to you in detail is something the school clarifies with its own data protection officer.

The way out of the class group

The switch does not start with technology but with an agreement: which route applies to which occasion from now on? Once that is settled, the school needs a channel it manages itself – create classes, bring families in by invitation link, done. SchuleVernetzt is one of those routes, hosted inside the EU.

FAQ

Frequently asked questions about messengers in school

There is no answer that holds everywhere, because this is decided at the level that supervises your school. In Germany, school law and data protection supervision sit with the federal states, several of which have restricted or prohibited the official use of consumer messengers while others draw the line more narrowly. Many school systems have issued no ruling at all, which is not the same as approval: the underlying duties on the school as controller apply regardless. What counts is the rule for your school and, where none exists, the advice of whoever supervises you.

That is their private matter, and the school is not responsible for it. It only becomes delicate once official information is fed into it: school communication then hangs on a group that nobody at the school manages and that by no means reaches every family.

It solves the question of the private number, but not the question of who processes the data and how official communication stays traceable. Both depend on the channel and not on the device.

Yes, for two reasons that hold regardless of jurisdiction. In a class group the information that a child is ill is read by every family, when one office needed it. In a teacher's private chat it sits on a device the school does not manage and cannot later clear. In the EU and the UK there is a legal edge on top, because Article 9 GDPR treats health details as a special category. Both problems fall away once sick notes run through a channel the school controls itself.

A class group only reaches those who have a smartphone, use the app and understand the text. Everyone else learns things by chance or not at all. A school channel should therefore run in the browser as well, offer texts in several languages and leave a route open for the office to add a reply on someone's behalf. Reachability is a question of fairness as much as of technology, and in many school systems it is also a duty rather than a courtesy.

Four points are usual, and none of them depend on where the school is: which route applies to which occasion, within what period an answer may be expected, what is expressly not discussed digitally, and how the school reaches families who cannot use the chosen channel. Whether a separate agreement with the staff body is additionally required is the one point that does depend on local law – in Germany, for instance, it depends on the federal state and on the body running the school.
Coming soon

Be there when SchuleVernetzt launches

We're building SchuleVernetzt at full speed. Leave your email and we'll notify you the moment your school can get started – free and with no obligation.

We use your address only to notify you at launch, and you can unsubscribe at any time.