Privacy Policy
Last updated: 31 August 2026
1. Who we are, and the two roles we play
LessonSolutions is a service provided by Just-Solutions, KvK 42024979, VAT NL005439088B10, Panna 3, 5126 DJ Gilze, the Netherlands. Questions about this policy or about your data: privacy@lesson-solutions.online.
We play two different roles in this service, and that is the most important thing to take away from this policy.
- Towards the tutor we are the controller. Your account, your subscription, our invoices to you and the security logs are our responsibility. That is clause 2.
- For everything a tutor records about pupils and parents we are the processor. The tutor is the controller for that data; we store and process it only on their instructions. That is clause 3, and the arrangements are in the data processing agreement.
Are you a parent? Then your point of contact is your child's tutor, not us. See clause 12.
The Dutch text is the authoritative version. If the German or English translation differs from it, the Dutch text prevails.
2. Data we are responsible for (the tutor and the visitor)
- Account: username, email address, first and last name, language preference, password (only as a hash, never readable) and whether the account is active.
- Subscription and billing: the plan you chose, its status and period, and the billing details you enter (company name, address, country). The payment itself runs through Mollie; we never see card or bank numbers.
- Practice profile: practice name, address, chamber-of-commerce number, VAT number, IBAN, logo, accent colour, timezone and your default rate. These appear on what you send out.
- Security log: sign-in and sign-out, failed sign-in attempts, a locked account, password change, email change and subscription events — with a timestamp and an IP address.
- Contact form and email: what you send us, so we can reply.
- Preferences in your browser: see the Cookie Policy.
Legal bases: performance of the contract with you (account, subscription, support), a legal obligation (our own bookkeeping), and our legitimate interest in a secure service (the security log, preventing abuse).
3. Data we process on the tutor's behalf (pupils and parents)
The tutor decides which of this data they record. We do not, and we use it for nothing else.
| What | Which data | About whom |
|---|---|---|
| Parent / contact | first and last name, email address, phone number, address, country, free-text notes | the parent |
| Pupil | first and last name, year group, school, date of birth, hourly rate, start and end date, whether active, free-text notes | the child (roughly 4–12 years old) |
| Lessons | date and time, duration, subject, rate and status (planned, held, cancelled, make-up, trial, no-show) | the child |
| Lesson log | the free-text note the tutor writes after the lesson, the topics covered, whether homework was set and whether it was done | the child |
| Assessments | a judgement from 1 to 5 per topic, dated, kept as history | the child |
| Progress reports | the draft, the final text, the PDF and the send date | the child |
| Invoices to parents | invoice number, period, lines with lesson date and amount, VAT treatment, status, payment date, reminders and the PDF | the parent |
| Materials | worksheets and other files the tutor uploads | the child |
| Messages from the parent portal | an absence, a request for an extra lesson or a message, with the text the parent writes | the parent and the child |
| Portal access | a counter that lets links be revoked, and when the portal was last visited | the parent |
| Trial-lesson request | the child's name, year group, the parent's name, email address and phone number, message | the parent and the child |
Special categories of personal data. The service never asks for them and has no field for them. The free-text notes and the lesson log are free text, so a tutor can put something in them that counts as a special category (a mention of dyslexia or a medical situation, say). Our Terms prohibit that to the extent it is not needed for the tutoring practice. We do not read those fields, but we could technically see them.
4. What we use it for
| Purpose | Legal basis |
|---|---|
| Creating your account, signing you in and providing the service | performance of the contract (Art. 6(1)(b) GDPR) |
| Charging your subscription and keeping our own invoices | performance of the contract and a legal obligation (Art. 6(1)(b) and (c) GDPR) |
| Storing pupil and parent data and showing it to the tutor | we act as processor; the legal basis rests with the tutor (Art. 28 GDPR) |
| Having a language model write a draft report | we act as processor on the tutor's instructions — see clause 6 |
| Securing the service, preventing abuse and investigating faults | legitimate interest (Art. 6(1)(f) GDPR) |
| Website statistics, where enabled | consent (Art. 6(1)(a) GDPR) — see the Cookie Policy |
We do not sell data, we do not use the data in the service to improve our products, and we do not train models on it.
5. Children's data
The pupils in this product are children of roughly four to twelve years old. They do not create accounts and have no access to the service themselves; only their tutor and their parent see their data.
We have no contact with the child and no contract with the parent. The tutor agrees with the parent that they keep these records, and the tutor is the one who needs a lawful basis for that and who must inform the parent. We support the tutor in doing so, but we cannot make that arrangement for them.
6. AI-drafted reports, and the transfer to the United States
This is the most far-reaching processing in this product and it deserves its own clause: for this feature, notes about a named child leave the EU.
From the Tutor plan onwards the tutor can have the service write a first draft of a monthly report. For that we send Anthropic PBC (United States) exactly the following: the child's first name, year group, subject, the period, and per lesson the date, the topics, the tutor's note and whether homework was done, plus the assessments from 1 to 5. Surname, date of birth, school, address, the parent's details and the invoices are not sent.
The safeguards are built in, not merely promised: the model only sees what the tutor recorded and may not invent anything; the output is always a draft the tutor must review; nothing is ever sent to a parent automatically; and the feature only exists on the plans it belongs to. Without it the report editor still works and the tutor writes the first draft themselves.
Anthropic is a sub-processor in the United States. The transfer relies on the European Commission's Standard Contractual Clauses, incorporated in Anthropic's data processing terms. What Anthropic does with data supplied through the API is set out in their privacy policy.
If a tutor or a parent does not want this, the answer is simple: the tutor does not use the feature. Nothing then goes to Anthropic.
7. The parent portal
A parent receives a personal link from the tutor. Whoever opens it does not have to sign in, and sees only their own family's data: the next lessons of their own children, the worksheets the tutor shared, the reports the tutor sent, that family's outstanding invoices, and the practice's name and IBAN to pay to.
What we record on that visit: when the portal was last opened (so the tutor can see it is in use), and whatever the parent sends in (an absence, a request for an extra lesson, or a message). No account is created and nothing about the parent's browsing is tracked.
The link is signed, points at one family, and cannot be altered to show another. It deliberately has no expiry date, because a parent will not maintain a password with their child's tutor. In exchange, the tutor can revoke access for a family in one step; every link previously sent to that family stops working immediately. Anyone who forwards the link passes on that access — treat it as a key.
We have no contract with the parent. The tutor is the one who informs the parent about the portal and who decides who receives the link.
8. Who else processes the data
| Party | For what | Where | Which data |
|---|---|---|---|
| Contabo GmbH | hosting of the servers, the database and stored files | Germany | all data in the service |
| TransIP B.V. | domain name and DNS | the Netherlands | no content data |
| Our own mail server | sending email (activation, password, notifications) | EU, the same infrastructure as the hosting | email address and the content of the message |
| Mollie B.V. | payment of your subscription with us | the Netherlands | name, email address and payment details |
| Anthropic PBC | writing a draft progress report (clause 6) | United States | first name, year group, subject, period, lesson notes and assessments |
| Google Ireland Limited | website statistics — only where analytics is enabled for this environment and you consent in the cookie banner | Ireland, with possible processing elsewhere | anonymised usage statistics |
We have a data processing agreement with every party that processes personal data for us. We do not sell data and share nothing with advertisers.
9. Transfers outside the EU
The service runs on servers in Germany and the data stays there. There is one exception, the AI feature in clause 6: it sends lesson notes to Anthropic in the United States, on the basis of the European Commission's Standard Contractual Clauses. If the tutor does not use that feature, nothing leaves the EU.
If analytics is enabled and you have consented, Google may also process that data outside the EEA, likewise on the basis of the Standard Contractual Clauses.
10. How long we keep data
We describe what happens today, including where that is not yet what it should be.
- Pupil and parent data, lessons, logs, assessments and reports: these stay for as long as the tutor keeps them. There is no automatic pruning. The tutor can erase a family and all its history in one action, and the service shows exactly what that will destroy before it does it.
- Sent invoices to parents: these stay. A family with sent invoices cannot be erased, because the tutor must keep invoices for seven years under Art. 52 of the Dutch General Tax Act. The GDPR expressly leaves that obligation standing (Art. 17(3)(b)). A draft invoice is not bookkeeping: it was never sent, it blocks nothing, and it is erased along with the family.
- Your account: for as long as you have it. If you delete it yourself we anonymise the account — username, email address, name and billing address are cleared and your sessions are ended — and we erase your practice with it: pupils, parents, lessons, lesson logs, assessments, reports, schedules, materials and parent portal messages. That happens in one action, before the anonymisation: if the erasure fails the account is not deleted either, so nothing is ever recorded as erased when it is not.
- What deleting your account leaves standing: families with sent invoices. Of such a family only the name and address remain — the billing address, without which an invoice is not a valid invoice. Email address, phone number, notes and parent portal access are removed, and every portal link ever mailed to them stops working. The pupil, the lessons and the lesson logs are erased in that case too. Invoice lines do carry the child's name and the lesson date, because an invoice has to state what was delivered; that is the one place the name survives the seven years.
- Security log containing IP addresses: not automatically pruned today. We will set a fixed period for it as part of the legal review of this policy.
- Our own invoices to you: seven years, a statutory retention obligation.
- Email you send us: for as long as needed to handle your question and a limited period afterwards for the record.
11. Security
What we actually do:
- all connections over HTTPS;
- passwords stored only as a hash, never readable;
- the session cookie is HttpOnly, Secure and SameSite, so scripts cannot reach it;
- a session access token is short-lived and refreshed;
- every query in the service is bound to the account that owns the record, so one practice can never read another practice's data; the same holds for a portal link and the family it belongs to;
- rate limiting on sign-in and on the rest of the API, and a temporary lock after repeated failed sign-ins;
- security headers on every response;
- form spam protection that runs on our own server (ALTCHA, proof-of-work in the browser) and involves no third party;
- a security log of sign-in and account events;
- servers in Germany, inside the EU.
Complete security does not exist. If you suspect a vulnerability or see something odd, email the address at the bottom of this policy straight away.
12. Your rights
You have the right of access, rectification, erasure, restriction, objection and portability, and you can withdraw consent you gave at any time.
Are you a tutor and our customer? You can change your profile, export your data and delete your account from your settings. If something does not work, email privacy@lesson-solutions.online. We respond within one month.
Are you a parent? Please address your request to your child's tutor. They decide what is recorded about your child and are the controller for it; we may not change or delete that data on our own initiative. If you do not know who to contact, or the tutor does not respond, email privacy@lesson-solutions.online — we will point you in the right direction and help the tutor handle your request.
13. Complaints
If you disagree with how we handle your data, tell us first — we would rather resolve it ourselves. You can also complain to the Dutch data protection authority: autoriteitpersoonsgegevens.nl.
14. Changes and contact
We update this policy when the service changes. The date at the top shows the last change. For a material change we notify account holders by email.
Controller: Just-Solutions, KvK 42024979, VAT NL005439088B10, Panna 3, 5126 DJ Gilze, the Netherlands.
Privacy and data protection: privacy@lesson-solutions.online
Other questions and support: support@lesson-solutions.online
Given the nature and scale of our processing we are not required to appoint a data protection officer; please send privacy requests to the address above.