Skip to content

Data Protection & GDPR

Data Protection & GDPR Compliance

We take data protection seriously. Here is exactly how your data flows through our system, who handles it, and what rights you have under GDPR.

How do your students enter their availability?

Everything runs as our service, hosted in Germany. This one choice decides how much identity data is stored: the standard way, or a paper list with QR codes where no identity is recorded digitally.

Weak protectiontypical US-hosted SaaS — not us
Strong protectionEU / GDPR baseline
Highest protectionoptional: no identity recorded digitally

Suitable for these professions

Music teachersTutoring & private lessonsDriving instructorsLanguage schoolsPsychotherapists & counselorsMedical & health practices

General guidance based on typical confidentiality needs, not legal advice — assess your own obligations, e.g. under professional confidentiality duties (§ 203 StGB) or Art. 9 GDPR special category data.

Data collected

  • ✓ Student display names
  • ✓ Email address, optional (for the magic link)
  • ✓ Availability times

Where it is stored

  • → Our servers in Germany, on your behalf
  • → Governed by a Data Processing Agreement, part of the terms of use

GDPR status

  • ● Pseudonymous at the solver
  • ● Identified in storage
  • ● You remain the controller
YOU enter the data
IDENTIFIED
Your roster

stored on our infrastructure

  • Name: Max Mustermann
  • Email: max@example.com
  • Availability: Mon/Wed 18–19h
HTTPS, pseudonymized
WE (processor, during the solve only)
PSEUDONYMOUS
Solver input

in memory, discarded after

  • ID: p7f3a9c2e18b04d6a
  • Availability: Mon/Wed 18–19h
  • Priority + reliability score
  • ✗ No name, no email, no address
Schedule back
WE (storage, on your behalf)
IDENTIFIED
Your schedule

shown to you via magic link

  • Student #42 → Max Mustermann
  • → Re-linked on our side

The badges say who can re-identify at each step. For you as the controller the data stays personal data in every setup — GDPR keeps applying to your practice. What differs between the two setups is who else can re-identify: in the standard setup we can, because we hold the names on your behalf; with the paper list and QR codes we cannot.

⚠️ The trade-off you are making here

In this setup we are the processor for the whole pipeline, not just the brief computation — your roster lives on our servers in Germany under a Data Processing Agreement.

Because our system maps the ID back to a name, the data we process stays pseudonymous rather than anonymous.

If students sign in by magic link, an email address is needed — and an email address identifies a person. If you need the highest level, choose the paper list with QR codes instead.

Terms that get mixed up — we keep them apart

This distinction decides whether GDPR still applies to the data. Most providers blur it; the honest answer differs per setup.

PSEUDONYMOUS
Pseudonymous (Art. 4(5) GDPR)

The name is replaced by an ID, but somebody still holds the key that maps it back — in the standard setup our system, on your behalf; with the paper list, you. The data therefore stays personal data and GDPR keeps applying, even though the solver never sees a name. This is the honest label for every setup in which the mapping still exists anywhere — on paper just as much as digitally.

ANONYMOUS
Anonymous (Recital 26 GDPR)

Nobody can ever map the data back to a person — not even you. That state is only reached once the mapping itself is gone, so as long as you need your paper list to know who is coming at 6 pm, your data stays pseudonymous: Recital 26 covers every means, on any medium. What the paper list with QR codes does reach is the strongest position actually available — on our side the mapping never exists at all, so for us and our sub-processors the data is anonymous. Technically, not merely contractually.

What the solver receives — in every setup

Before the data reaches the solver, each student ID is replaced by a cryptographic pseudonym. The lookup table stays in our system in Germany and is never sent to the solver.

The solver holds the data in memory for the duration of the computation and discards it afterwards. It is never written to a database, and log lines contain only salted hashes, never plaintext.

The dispatcher runs on servers in Germany (Strato); for the computation load, the optimization may additionally run on AWS in the eu-central-1 region (Frankfurt). Your data does not leave the EU.

The licence server — what it does and does not learn

Our licence server in Germany manages your account and counts usage to bill tokens and to enforce the free tier. For each computation it receives the number of students and a timestamp.

To keep the free tier honest we do keep the list of pseudonymous student IDs for your account — otherwise the same free allowance could be reused endlessly under new IDs. These are the same nameless pseudonyms as above, and they are deleted when you request erasure.

In the standard setup the display names and optional email addresses of your students are stored in the same system in Germany; they are never passed on to the solver. With the paper list and QR codes they do not exist at all.

Your rights under GDPR
  • Access (Art. 15): export your data from your account at any time.
  • Rectification (Art. 16): edit student details directly in your account.
  • Erasure (Art. 17): request full deletion — account, students, tokens and audit logs, including the stored pseudonym list.
  • Portability (Art. 20): export schedules as JSON or CSV.
  • Withdraw consent (Art. 7): revoke processing consent at any time.
  • Data Processing Agreement (Art. 28): automatically part of our terms of use — you are the controller, we are the processor.
Sub-processors
  • Strato AG — hosting of licence server and dispatcher, Germany
  • Amazon Web Services EMEA — solver compute, eu-central-1 (Frankfurt), no persistent storage
  • ProWebMa — hosting of this website, Germany
  • Stripe Payments Europe — payment processing
  • Anthropic — automated review and translation of feature-wish submissions; no student or account data
  • Google Ireland — sign-in via Google OAuth (optional)
  • CleanTalk — anti-spam screening at registration

For providers that may transfer data to the USA we rely on EU Standard Contractual Clauses (Art. 46(2)(c)) or the EU-US Data Privacy Framework, as set out in each provider's own agreement.

Frequently asked questions
Do you use my data to train AI?

No. Student data is never used to train models or for any purpose beyond computing your schedule. We do not share, sell or monetise it.

Who owns the computed schedules?

You do. Once the schedule is returned, you own and control it. We keep no copy.

Do I need a Data Processing Agreement?

Yes — and it comes automatically. We process your students' data on your behalf: you are the controller, we are the processor. The Data Processing Agreement (Art. 28 GDPR) becomes part of our terms of use, and your teacher area is only unlocked once it has been accepted. With the paper list and QR codes no names and no contact details reach us at all and we cannot attribute the data to any person — but you stay the controller, so your own obligations and the agreement remain in place.

Can I delete everything?

Yes. An erasure request removes your account, all students, tokens, audit logs and the stored pseudonym list. Invoices are the one exception: German tax law (§ 147 AO) requires us to keep them for ten years.

What about cookies?

Session cookies for your login, plus optional analytics only after you consent. You can revoke consent at any time via the cookie banner.

Exercising your rights

For any data protection request or question, contact hallo@stundenplan-berechnen.de. We aim to respond within 30 days; complex requests may take up to 90 days under Art. 12(3) GDPR.

Documentation & Legal

Privacy Policy

Our full privacy and data protection statement, including cookies and third-party tools.

Imprint

Contact and business information for stundenplan-berechnen.de.