Nursery and kindergarten software: enrolment, attendance, fees, parent app
A parent asks the group chat whether the child ate lunch. The head chases fees in Excel. Kindergarten software collects intake, attendance and messaging — with the GDPR bar a child’s file needs.
A private kindergarten or nursery is intake, care and fee collection at once. Plus children’s data — GDPR recital 38 says outright that children deserve specific protection because they are less aware of the risks. A Messenger group named after the class is not a system: consents vanish, allergies (a special category under art. 9 GDPR) vanish, and so does proof that auntie may collect the child today, not the neighbour from the stairwell. Kindergarten and nursery software collects enrolment, attendance, fees and messaging — with roles a chat does not have.
The head is not looking for “edtech”. They want not to guess who is at the door at 4.20 pm, and not to rebuild September fees from three spreadsheets. Below: what breaks without a panel, which consents you really must split (GDPR vs image rights), why a teacher should not see a parent’s bank account, and when we do not pretend to be a statutory register.
What breaks in a kindergarten and nursery when intake, allergies and collection live in a Messenger group
A typical private setting has 2–8 groups, a waiting list for September and a kitchen that must know the diet in the morning, not “when mum writes on chat after 10 am”. The office chases a contract, a work certificate (if intake is scored) and a trip consent. A teacher should see an allergy at the table, not a fee arrears. If all of that lives in one notebook, someone will eventually post a child’s photo without consent or hand the child to a person who is not on the list.
- The waiting list in three spreadsheets (head, office, “the email lady”) — doubles, lost points, parents who “were first”.
- Attendance on paper — a fight over meal charges and whether absence over X days cuts the fee under the contract.
- Allergies, diet, standing medicines and an adrenaline kit in a cupboard, not at handover and not at the table. That is health data (GDPR art. 9), not a “loose note”.
- Fees, a sibling discount, a second child, absence — monthly mental arithmetic, errors, shame when chasing payment.
- Trip photos and CCTV frames dropped into a “closed group” with no consent log and no split between storing an image and publishing it.
- Nobody knows who may collect the child today: a parent, the other parent after a divorce, a grandmother, a neighbour with a one-day authorisation.
- A “no class tomorrow” message dies between the head’s SMS and a Facebook story. Half the parents still arrive.
What private kindergarten and nursery software should do before you buy a “catalogue e-register”
A good system is not another chat. It is a child file, a list of authorised collectors, consents per purpose, attendance, the menu, fees and a message with a read receipt. Same idea as course enrolment: intake, group, instalment — only the “pupil” is three years old and does not sign the consent themselves.
- Intake: form, documents, criteria, main and waiting lists, a decision, a contract, a joining fee.
- A child file: group, hours of stay, allergies, diet, medicines, authorised collectors (with an expiry date and a photo if you run it that way), emergency phones.
- Consents split: operational contact, marketing, image in the corridor, publication on the site / Facebook / Instagram, CCTV, trips, screening checks.
- Attendance and the day’s menu — the parent sees it in the portal in the morning; the kitchen sees today’s diet list, not the family’s full file.
- Fees and meals: invoice / reminder / discounts. A KSeF path if you raise invoices from the panel.
- A message to the group, to one parent, or to “only those collecting today”, with a read receipt.
- An app / PWA: absence, later collection, a trip consent, a “collect by 4.30 pm” notice.
Collecting the child is a process, not “someone familiar from the face”
At the door what counts is the authorised list, a one-off authorisation and — in disputed family situations — what is in the contract and the court order, not who shouts louder. The system does not replace a teacher’s live judgement, but it can show: this person is on the list, this one had an authorisation until Friday, that one is blocked. A photo of the authorised adult on a tablet at exit is more practical than a notebook in the cloakroom. A collection log (who, when) helps on a “the child left too early” complaint, provided retention and access are limited — that is data too.
GDPR in kindergarten and nursery: allergies, image, CCTV and a consent that is not a terms footer
A setting processes ordinary data of the child and parents (name, personal id number, address, phone) usually on the contract and care law, plus health data (allergies, diet, injuries, chronic illness) — a special category under art. 9. You need a clear basis (explicit consent or another ground your DPO / lawyer names), minimisation (the kitchen sees “gluten free”, not the whole hospital history) and people who do not dump scans of medical notes onto a private Google Drive. GDPR art. 8 (a child’s consent to information-society services) and the age-16 threshold in Poland is mainly about online accounts; in a nursery the parent still acts as guardian. Recital 38 sits behind every decision on photos and CCTV.
Image rights are two things that heads often glue into one checkbox. GDPR consent to process a photo (store it in the panel, send it to the parent). Permission to disseminate the image (copyright / image-protection law) on the website, a brochure, Instagram. Withdrawing publication consent does not always mean instantly deleting the photo from internal trip records — and the other way round. The system should keep consent versions, date, purpose and a “I withdraw” control, not “I accept the terms and everything”. Corridor CCTV: purpose (safety), retention, who watches the tape, a ban on publishing “funny frames”. More on roles and logs: GDPR in web applications. EU hosting.
- Teacher: attendance, allergies, collection, a pastoral note. No fee balance and no parent bank account.
- Kitchen: the day’s diet and allergen list. No addresses and no parents’ court cases.
- Accounts: fees, invoices, arrears. No pool photos and no behaviour notes.
- Parent: their child, their consents, their payments, group messages. Not the phone list of the whole class.
- After leaving: a retention and deletion / restriction path — not “we keep the file because the shelf would look empty”.
Fees, meals, discounts and messaging that does not block the office line
The fee model in a private setting is often more complex than “a flat sum per child”: joining fee, tuition, meals, a sibling discount, a cut after absence above the contract threshold, extra hours, a deposit. Monthly mental arithmetic ends in an error and a complaint. The system calculates from the price list and the contract, raises a reminder, shows the parent a balance. The teacher does not see it — and should not, because the pastoral relationship is not debt collection. A message about tomorrow’s trip goes out with a read receipt; anyone who has not opened it gets a second channel before the bus leaves.
A package, a school e-register or your own panel — what makes sense in a 40-child nursery
Ready-made parent apps and e-registers written for schools exist. Some of them will carry attendance and chat and fall over on your price list or a one-day collection authorisation. One group, a simple lump sum — price a licence first. Custom software when you have a chain of sites, scored intake, a kitchen with diets, your own brand, and you do not want children’s personal-id numbers sitting in a cloud whose terms will change over the summer. Comparison: package or custom software. Start: intake + file + attendance + consents. Fees and a native app — once the office no longer chases “is Jan in tomorrow”.
How kindergarten software pays back before the next intake
The head’s hours on “is Jan in tomorrow” and chasing fees cost more than a panel. A parent who logs an absence in 30 seconds does not block the line and does not leave the child “just in case”, for whom the kitchen still cooks. An empty place in the group shows up in the intake report, not two weeks after “it feels quieter”. Bain / HBR: keeping (here: a sibling next year, a review, no January outflow) is cheaper than another billboard at the roundabout. Same arithmetic as service booking: less peak chaos, more repeat fees.
GDPR recital 38, art. 9 (allergies) and image rights: two consents, not one terms checkbox
Recital 38 says outright that children deserve specific protection because they are less aware of the risks. A personal id number, address and a parent phone are ordinary data, usually on the contract and care law. Allergies, diet, standing medicines, injuries and chronic illness are a special category under art. 9 — the kitchen sees “gluten free”, not a clinic scan. Art. 8 (a child’s consent to information-society services, age 16 in Poland) is mainly about online accounts; in a nursery the parent still acts as guardian. A DPO / lawyer names the ground; the system keeps the consent version, the date and a withdraw control.
Image rights are two things heads glue together. GDPR consent to store a photo in the panel and send it to the parent. A separate permission to publish (site, brochure, Instagram) — image-protection law, not only GDPR. Withdrawing publication does not always delete the frame from internal trip records. Corridor CCTV: purpose safety, retention, who watches, a ban on “funny frames”. More in GDPR in web applications. EU hosting.
The collection list, a one-day authorisation and a family dispute at the door at 4.20 pm
At exit what counts is the authorised list, an expiry date, a photo of the adult (if you run it that way) and a one-day authorisation for today. In a post-divorce dispute the system shows who is on the contract and who is blocked — it does not replace a teacher’s live judgement or a court order. A “who collected, at what time” log helps on a “left too early” complaint, with limited retention. That is data too, not a cloakroom notebook every waiting parent can read.
Fees, meals, sibling discount and KSeF: a teacher does not chase debt at the cubby
The fee model: joining fee, tuition, meals, a sibling discount, a cut after absence above the contract threshold, extra hours, a deposit. Monthly mental arithmetic ends in an error. The system calculates from the price list, raises a reminder, shows the parent a balance. The teacher does not see it — the pastoral relationship is not debt collection. If invoices go from the panel, KSeF is an accounts topic, not a marketing tile. A statutory journal, if it applies, stays beside us — we do not pretend to delete it.
Describe group and child count and whether intake, fees, collection or parent comms hurt. An MVP for enrolment, the child file and attendance can land before the next intake, not “after next summer”. GDPR will not be a footer in the footer — it will be a list of consents and roles from the first form.
Frequently asked questions
- Must the parent install a Google / Apple store app?
- No. At the start a phone browser panel (PWA) is enough. Native Android or iOS when you really want “collect by 4.30 pm” push and have the volume that pays for it. We do not force an install to report a cold.
- Several sites and shared intake?
- Yes — a shared list or a separate one per site, shared accounts, a teacher’s rights only for their group and building. A parent with two children in two sites logs in once.
- Diets, allergies and medicines?
- On the card and on the day’s menu. The kitchen sees today’s list (allergen, diet); a nurse or teacher sees a standing-medicine dose. Not the family’s full divorce file. That is art. 9: minimisation, not “everything in one PDF for everyone”.
- Will a teacher see fee arrears?
- Not if you set roles that way. Heads often require that, and they are right. Collection stays in the office and accounts; the room stays pastoral.
- Will the system replace a journal the founding body requires?
- We do not promise to delete an official form. We can lighten attendance, messaging and fees and leave the journal or export data. State education has its own systems — we do not pretend to switch them off.
- How long to keep data after the child leaves?
- That is the controller’s decision with a lawyer / DPO: the contract, claims, meal records, image. The system must be able to restrict access and delete or anonymise after the term, not “keep forever because of the backup”. We do not drop a ready-made paragraph in place of your assessment.
- How long to go live before intake?
- An enrolment form, lists, child file, consents and attendance — usually weeks if you are not migrating 15 years of scans. Fees, diets, a native app — the next phase. Better to run intake on time than wait for a “full parent ecosystem”.
Describe your project