Privacy statement
What we know about you, why we know it, and how to get rid of it. Without an account we keep nothing about you.
Last updated on 26 October 2026
The short answer
The tools work without an account. Used that way, we store no data about you. What you set — the time on the timer, the sound, the language — stays in your own browser.
Create an account and we keep your name, your email address and whatever you save yourself: your groups, your favourite tools and the points you earn by practising. Work with a school or pay for Reppilo, and a little more is added. Everything is listed below, with how long we keep it and who else sees it.
We sell no data and we send no marketing email.
Who is responsible
The controller for the data set out below is Eduhuis V.O.F., Biesterveld 9, 7251 VR Vorden, Chamber of Commerce 42200688.
Questions about your data or about this statement go to info@eduhuis.nl.
What we process
With an account:
- Your name and email address, so you can log in and we can reach you about your account.
- Your password, stored hashed. We cannot read it.
- If you log in with Google or Microsoft, which account there belongs to yours: an identifier from that service and the email address. We never get your Google or Microsoft password.
- Your language, so the site opens in the same one on every device.
- Your groups: the names you put in a list yourself.
- Your favourite tools: which tools you starred.
- Your points: for every round that was finished, which tool it was, how many questions it asked, how many were right and how long it took, and later on what you spend them on as well. Nothing that is written or answered on the board goes in there.
- If you use two-factor authentication or a passkey, what is needed to check it.
- When you were last on the site, to within a few minutes. That tells us whether an account or a school is still in use.
- If you belong to a school: which school, whether you are an administrator or a teacher there, and which classes you teach.
- Your school's log: what happened in the school and who did it, with your name. For example that you created a class or invited a colleague. Only the school's administrators can read it.
- If you ask your school's administrators for the school license, that you asked and when. That way they do not get the same request in their inbox every day.
- If you pay for a school license, your billing details: the name and address on the invoice, the email address for invoices, a VAT number and a purchase reference if you fill them in. If you pay an invoice, we and Moneybird see which account the money comes from.
- Your session: a technical identifier, your IP address and your browser type, so you stay logged in and we can spot abuse.
Without an account too
Our server keeps technical logs of every visit: the address requested, the time, an error if something goes wrong, and the IP address. We need those to fix outages and stop abuse. We keep them briefly.
Our error monitoring sees which pages are requested, how fast they load and what goes wrong. It does not get codes in the address or your IP address. If you are logged in, all it gets from your account is the number: no name and no email address.
We count page views ourselves, without a cookie. For that we keep the address of the page, the site you came from and a hash: a code made from your IP address and your browser, with a key that is new every day. Within one day that lets us recognise the same visitor. The next day the key is gone and nobody can work out who it was.
If you send us a message through the contact form, we receive your name, your email address and your message by email. It comes with the page you came from, your browser and, if you are logged in, your account and your school.
What you set in a tool stays in your browser and never reaches us. The cookie statement lists exactly what is stored.
Statistics and session recordings only run if you agree to them in the cookie notice. Say no and they stay off. Children are never measured: on a child account and at the class door they are always off.
Why we are allowed to
To perform our agreement with you: your account, your groups, your favourites, your place in a school and the payment for a school license. Without them we cannot provide what you created an account for.
On a legitimate interest: securing the site, the technical logs and the error monitoring, so the site keeps working and abuse shows up. The page counter and when you were last on the site fall under this too, so we can see what is used, and so does the school's log, so a school can see who did what. And a message through the contact form, so we can reply.
On your consent: statistics and session recordings. You can withdraw that consent at any time.
To meet a legal duty: invoices and payments have to stay in our books for seven years.
Pupils' names
A name list usually holds pupils' names. That is personal data about someone other than you, and we treat it carefully.
Put in no more than you need. A first name is enough to split a class; a surname, a register number or a note about a pupil does not belong in it. Sensitive details never do.
We do not read those lists, use them for nothing else and share them with nobody. They sit under your account alone, and they are gone the moment you delete the group or your account.
If you use the site on behalf of a school, the school is usually the controller and we are the processor. If your school needs a data processing agreement for that, email info@eduhuis.nl.
If you sign on behalf of a school
A Dutch school can sign the data processing agreement of the Privacyconvenant Onderwijs with us. If you sign it on behalf of a school, yourself or through a personal link, we keep who signed: your name, your email address, the IP address you signed from and the time. This is also in the PDF of the agreement, which we send to you, to the school's managers and to our own records.
We may do this to meet a legal duty: the GDPR asks for a written agreement, and that we can show it exists. And for a legitimate interest: proof of what was agreed and who agreed to it.
We keep it for up to seven years after the agreement ends: after the school is deleted, or after a newer agreement is signed. So if a school deletes itself, the signature stays, because it belongs to our records. After the seven years we empty the details about people and delete the PDF. What is left is which school signed which version, and when.
How long we keep it
An account unused for three years is deleted. We send an email before that happens. If you are an administrator of a school with a license, or the only administrator of a school with colleagues or students, we do not delete your account on our own. We then ask the other administrators, or look at it ourselves if there are none.
Apart from that, we keep each kind of data for as long as the table below says. After that it is gone.
| What | How long |
|---|---|
| Your account, your groups, your favourites and your points | As long as you have the account. Delete it and we remove it straight away. |
| When you were last on the site | As long as you have the account |
| Which school you belong to and in what role | Until you leave the school or delete your account |
| Your requests for the school license | Until you delete your account or the school is deleted |
| The school's log | 400 days, or until the school is deleted. A line with your name stays even if you delete your account, because it belongs to the school. |
| Your billing details | Until you delete your account or the school is deleted |
| Who signed the data processing agreement on behalf of a school | Seven years after the agreement ends, also if the school is deleted. After that we empty the details about people. |
| Invoices and payments | Seven years, because that is how long they must stay in our books. They are kept in our bookkeeping, at Moneybird. |
| Technical logs | At most fourteen days |
| Error monitoring | At most thirty days |
| The page counter | Thirty days. After that we keep only the number of views per page per day, without the hash. |
| A message through the contact form | As long as we need it to deal with your question |
| Sessions | They expire on their own once you are idle for a while |
| Backups | Thirty days. Whatever you delete stays in an encrypted backup until then. |
Who else sees it
We use a few providers to keep the site running. Hetzner, Lettermint, Nightwatch, Forge, Moneybird and PostHog work on our instructions: each of them is bound to use the data for us alone.
If you log in with Google or Microsoft, their own privacy statement covers what happens there. All we get from them is your name, your email address and an identifier.
| Provider | What for | Where |
|---|---|---|
| Hetzner Online GmbH | The site's servers and database. Every day an encrypted backup goes to a second location. | Germany (Falkenstein), backups in Finland (Helsinki) |
| Lettermint B.V. | Sending our email, such as confirmations, invitations and password resets. Lettermint gets your name and email address. | The Netherlands |
| Laravel Nightwatch (Laravel Holdings Inc.) | Error monitoring: which page was requested, how fast and what went wrong, with your account number. No name, no email address and no IP address. | Stored in the European Union, company in the United States |
| Laravel Forge (Laravel Holdings Inc.) | Managing our server and putting new versions on it. Forge can reach the server, but keeps no data from the site itself. | No storage, company in the United States |
| Moneybird B.V. | Our bookkeeping, the invoices and paying with iDEAL: the name and address on the invoice, the email address for invoices, a VAT number if you fill one in, and which account a payment comes from. | The Netherlands |
| PostHog Inc. | Statistics and session recordings, only if you agreed to them. Children are not measured. | Stored in Germany (Frankfurt), company in the United States |
| Google and Microsoft | Logging in, only if you choose to. | See their own privacy statement |
Outside Europe
The site, the database and the backups are in the European Union: in Germany and in Finland. Our email and our bookkeeping go through Dutch companies.
Nightwatch keeps our data in the European Union and PostHog in Frankfurt, but the company behind each is American. We manage our server with Forge: Forge keeps nothing itself, but can reach the server from the United States. Laravel, the company behind Nightwatch and Forge, is part of the EU-U.S. Data Privacy Framework: the arrangement between the EU and the US for passing on personal data. An American company can be asked under American law to hand over data, even when that data is in Europe. That is why Nightwatch gets no names, no email addresses and no IP addresses, and PostHog only measures after consent and never for children.
How we secure it
All traffic with the site runs over an encrypted connection. Passwords are stored hashed and cannot be read back. The backups are encrypted.
You can add two-factor authentication or a passkey to your account. We recommend it if you keep groups with pupils' names.
If something does go wrong with your data, we tell you when the law requires it.
Your rights
You may see your data, correct it, take it with you and have it deleted. Two of those you do yourself, right now:
- See it and take it: your profile settings download your data in one file. For anything that is not in it, such as your school's log or your billing details, email info@eduhuis.nl.
- Delete it: your profile settings delete your account and everything under it.
- Correct it: your name and email address you change yourself; for anything else, email info@eduhuis.nl.
- Object to processing or have it restricted: email info@eduhuis.nl.
A complaint
If you think we are not handling your data properly, tell us first at info@eduhuis.nl. Then we fix it.
If we cannot settle it together, you can complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens), or to the supervisory authority in your own country.
Changes
When something about the site changes, we update this statement. The top of the page says when that last happened.
For an important change we say so on the site or by email.