Data protection in the yearbook: what you really have to watch

A yearbook is full of personal data: names, photos, quotes, judgements by people about people. And a large part of the year group is still under 18, which raises the requirements rather than relaxing them.

That is no reason to panic. It is a reason to settle three things in the autumn instead of in May — because after printing, none of it can be repaired.

Not legal advice. This text is practical orientation. In a concrete conflict, the school leadership and, if it gets serious, a data protection officer or a lawyer are the right people to talk to.

1. Consent: who, what for, and in what form

For photos and named contributions you need the agreement of the people concerned — for minors, that of their parents or guardians as well.

What a usable consent has to do:

• Name what it is about. “Photos and contributions in the 2027 year group’s yearbook” — not “for school purposes”.
• Limit the purpose. The yearbook, yes; the year group’s Instagram account is a separate item you ask about separately.
• State the print run. A printed run of 120 copies is something different from a file on the internet.
• Be voluntary. Anyone who doesn’t want to may say no without consequences.
• Be revocable — with the honest addition that a withdrawal after the print handover no longer reaches the printed copies. Which is exactly why the consents have to be in early.

Practically: one form, at the start of the project, for everybody. Not 90 individual conversations in the spring. Ask the school whether a template already exists — many schools have one for school events that works as a starting point.

And document who agreed. A consent nobody can evidence doesn’t help in a conflict.

2. What is particularly sensitive

Not all data is equal. These categories need more than a general agreement:

• Grades and performance. “Best average grade” as a named award is performance data. Ask that person specifically.
• Health. Illnesses, absences, therapies — they don’t belong in the book, not even as an anecdote.
• Relationships. “Dream couple” is harmless when both agree and unpleasant when they don’t. With couple categories, ask both.
• Addresses and phone numbers. Nobody needs them in a yearbook. If you want to collect contact details for a reunion, do it separately and not in the book that goes into circulation 120 times.
• Anything about people who aren’t in the year group. Teachers, the caretaker, siblings. See Collecting teacher quotes.

3. Collect only what’s needed

Don’t collect data “just in case”. What isn’t going into the book doesn’t need to be gathered — that saves you the effort of deleting it later and the question of where it actually is.

Concretely that means:

• No collecting in private chats. Photos in a WhatsApp history sit on 90 devices and in a backup nobody controls. That is the most common real data protection breach in this project — and nobody notices it.
• One place for everything. A system where it is clear who has access.
• Tidy up after printing. Once the book is out, nobody needs 400 unused photos any more.

4. What AbiHive does about it

So you know what you can rely on and what you can’t:

• EU servers. AbiHive runs in a data centre in Frankfurt.
• Nothing is public. Profiles, photos, quotes and comments are only visible to your own year group — not on the open web, not to other cohorts. That is checked server-side per year group, not merely hidden in the display.
• No Google Fonts, no tracking baggage on the content pages. We serve the fonts ourselves, so that opening a page doesn’t send your year group’s IP address to third parties.
• Reporting and hiding. Every comment, every quote and every photo can be reported; the report goes to the person in charge of your year group. Anyone named in a quote can additionally take it off the wall themselves — no application needed. Hidden content also drops out of the book.
• Quotes about yourself only. There is a setting with which each person only sees or receives quotes on their own page — useful for year groups where the topic is sensitive.
• Access and deletion, self-service. Every person can download their own data as a file (Art. 15/20 GDPR) and delete their account along with its content (Art. 17). Both without going through you. Votes and orders remain afterwards without a name attached, because payment and print records are subject to statutory retention periods.

What AbiHive cannot do: spare you the consents. No tool decides whether a quote is acceptable.

5. The point where it usually goes wrong

Not with the forms — with the order. The typical sequence is: collect, design, print, and at some point in May somebody notices that there is no consent for three photos. That’s expensive, because the layout is already done.

The order that works:

1. Autumn: collect the consents before anything else is collected.
2. Winter: collect — in one place only, and only what goes into the book.
3. Spring: get approvals for quotes before they’re in the layout.
4. Before the handover: go through once — is there a photo or quote where nobody can say who agreed? Out with it.
5. After printing: tidy up.

6. And the digital edition?

If you pass the PDF on: not publicly on the internet. A file with profiles and photos of minors that search engines can find is categorically different from 120 printed copies — and not covered by a consent for “the yearbook”. Distribute it within the year group, via a link that isn’t indexed. More on that: Yearbook: digital or printed.

Takeaways

• One form for everybody, in the autumn, naming the purpose and the print run — and documented, so you know who agreed.
• For minors, the parents or guardians as well.
• Grades, health, relationships and contact details need their own question, or none at all.
• Don’t collect in private chats. That is the breach nobody notices.
• Get quotes approved before the layout, not after.
• Don’t put the PDF up publicly.

More: our privacy policy, the features at a glance and Collecting teacher quotes — without the trouble.