You are trusting a vendor with children's names, faces, health details and family contacts. You would not hand a stranger the keys to the nursery. Treat the software the same way, and ask these questions before you commit.
Sign-in and accounts
- How do parents sign in? Password, one-time code or a personal link. Each has trade-offs (see our article on passwordless sign-in). Look for something parents can use easily without sharing logins.
- How do staff sign in, and can I force strong passwords or extra checks? Staff accounts have far more access than parents.
- Can I remove a staff member's access immediately? When someone leaves, same day.
Who sees what
- Are there roles? Owner, manager, teacher, parent, each with different access.
- Can a teacher see only their own class? Not every child in the nursery.
- Can a parent ever see another family's information? The answer must be no, and it should have been tested.
- Is access logged? You should be able to see who viewed or changed a record.
Photos and documents
- Are photos private by default? Not on an open web address that anyone could guess.
- Do photo links expire or require sign-in? Better still if they are tied to the family.
- Can I delete a child's photos and records on request?
Hosting and backups
- Where is our data hosted, and who else has access to it? Some laws restrict where children's data may go.
- How often is it backed up, where are the copies, and has restoring been tested? A backup you have never restored is a hope, not a backup.
When things go wrong
- How will you tell us if there is a breach, and how fast? Some laws require notification within 72 hours.
- How are software updates applied? Is there a rollback if an update fails? Is a backup taken before each update?
- What happens to our data if we cancel, or if you close? Can we export it? How long until it is deleted?
What good answers look like
| Question | A good answer | A warning sign |
|---|---|---|
| Parent sign-in | Clear method, per-parent, revocable | Shared nursery password |
| Roles | Defined roles with limits | "Everyone sees everything" |
| Photos | Private, signed or expiring links | Public URLs |
| Hosting | Named location, written | "In the cloud" |
| Backups | Frequency, retention and restore tests | "We back up" with no details |
| Breach | Written process and timeline | "It won't happen" |
| Exit | Export and deletion promised in writing | No answer |
Do some checks yourself
- Ask for a trial and set up a test parent and a test teacher. Try to look at something you should not.
- Open a photo link in a private browser window. Does it open without signing in? Does the address stop working after a time?
- Ask for the privacy policy and terms and read the parts about data ownership and sub-processors.
- Ask for references from nurseries of a similar size.
FAQ
Do I need an independent security audit?
Not for a small nursery, but you can ask whether the vendor has had one and what changed afterwards.
Is a free tool less secure?
Not necessarily, but ask who pays for security if you are not paying for the software.
Should staff use their own phones?
Only with a clear policy: screen locks, no storing photos, immediate removal when they leave.
What if I only use a spreadsheet?
The same questions apply to where it is stored and who can open it. A shared spreadsheet link is a common weak point.
Try a platform built around private, role-based access: book a demo.
Try all of this in your nursery
See it under your own nursery name and logo in a short call with our team.
