Join our Newsletter — 33% off our NHI Course
Home› Guides› Cyber Security for Nurseries and Childcare Providers Guide:…
Guide Risk Management

Cyber Security for Nurseries and Childcare Providers Guide: Protecting Parent Apps, Photos and Child Data

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, under the editorial direction of Lalit Choda Updated 18 November 2026 17 min read
On this page

Nurseries, pre-schools and childminders hold some of the most sensitive personal data in any small organisation, and the accounts that protect it are usually a handful of shared logins to a parent app, an email inbox and a bank. This guide explains the threats that early years settings face, why photos and parent app accounts deserve special attention, what UK guidance expects, and a practical plan that a nursery manager, owner or group IT lead can follow without a dedicated security team.

It is written for settings in England and the wider UK, but the controls apply to any childcare provider. For primary and secondary schools, academy trusts and colleges, read our Cybersecurity for Schools Guide, which covers filtering, monitoring and the Department for Education standards.

Key takeaways

  • Early years records combine names, dates of birth, home addresses, family contacts, health and allergy notes, safeguarding information and photographs. That mix is valuable to criminals for extortion and identity fraud, even when a setting is not targeted directly.
  • The 2025 attack on the Kido nursery chain in London showed the extortion model in practice: attackers reportedly stole photos, names and addresses of around 8,000 children and published some profiles to pressure the business.
  • The parent app or nursery management platform is now the main system of record. Its administrator accounts, staff logins and integrations matter more than any single laptop.
  • Shared logins are the biggest identity weakness in small settings. Every person who can see child records should have a named account, protected by two-step verification, and removed the day they leave.
  • The NCSC's early years guidance gives four basics: back up, use strong passwords and 2SV, protect against malware with updates, and handle phishing. Most incidents in small settings trace back to one of these.
  • A personal data breach that is likely to risk people's rights and freedoms must be reported to the ICO, where feasible within 72 hours. Prepare the facts and contacts before you need them.

Why nurseries and childcare settings are different

A nursery is a small business with the data profile of a health and social care provider. A typical setting holds, for every child, a registration form with full name, date of birth, address and parents' details; emergency contacts and people authorised to collect; medical, allergy and dietary information; special educational needs notes; safeguarding records; funding and fee details; and a growing gallery of photos and videos captured during the day for learning journals and parent updates.

Several features of early years make that data harder to protect than in a school:

  • Very small teams. Many settings have no IT staff at all. The manager or owner often acts as administrator for every system, and support comes from a local IT provider, the software vendor, or a family member.
  • Shared devices. Tablets used to capture observations and photos are passed between practitioners through the day, often on a single shared login.
  • Heavy use of cloud platforms. Parent communication, observations, invoicing, registers and staff rotas usually live in one or two software as a service products. The security of those accounts is the security of the setting.
  • High staff turnover and apprentices. Accounts and devices are handed over frequently, which makes leaver processes important.
  • Families as users. Parents and carers log in to see their child's day. Their accounts, invitations and contact details become part of the setting's attack surface.
  • Payment flows. Fees, funded hours and supplier invoices create the conditions for invoice fraud and payment redirection scams.

The NCSC guidance for early years practitioners makes the key point plainly: the information that a setting holds is of value to a criminal, even if the setting is not directly targeted.

Threat picture

The threats facing nurseries are the same as those facing other small organisations, but the consequences are sharper because the data concerns young children.

Data theft and extortion

Ransomware groups increasingly steal data first and encrypt second, or skip encryption entirely. Children's photos and addresses give an extortion group strong leverage, because publishing even a few profiles creates public pressure and distress for families. The Kido case, described in the incident section below, is the clearest UK example.

Phishing and account takeover

Most compromises of small settings start with an email or text that steals a password. The NCSC lists the common lures: official sounding requests about password resets, compensation, device scans or missed deliveries, technical jargon, and pressure to act urgently. Once an attacker holds the nursery's email login, they can reset passwords for the parent app, read invoices and impersonate the manager.

Invoice and payment fraud

An attacker with access to a mailbox, or one who simply spoofs a familiar supplier or parent, can ask for bank details to be changed. Settings that pay suppliers and receive fees by bank transfer should treat any change of payment details as a high risk event.

Insider and accidental exposure

Photos sent to the wrong family, a newsletter with children's names left public, a former employee who still has an app login, or a tablet lost on an outing all count as personal data breaches. These are far more frequent than criminal attacks.

Regulation and guidance that applies

This section summarises the main obligations as of 18 November 2026. It is not legal advice; confirm details with your local authority early years team, Ofsted guidance and the ICO.

  • Early years foundation stage (EYFS) statutory framework. The Department for Education EYFS statutory framework sets the standards that childcare and school providers in England must meet for children from birth to five. The current versions came into force on 1 September 2026, with separate documents for childminders and for group and school based providers. Safeguarding, record keeping and confidentiality requirements in the framework apply to digital records and devices as much as to paper. Check the framework version for your provider type for the exact wording on safeguarding policy, use of devices and confidentiality.
  • UK GDPR and the Data Protection Act 2018. Every setting is a data controller for the records it keeps. You must keep personal data secure, limit access to those with a need, and choose processors (such as your parent app vendor) who give sufficient guarantees. Children's data and health information call for particular care.
  • Breach reporting. The ICO says that where a personal data breach is likely to result in a risk to people's rights and freedoms, you must notify it as soon as possible and where feasible within 72 hours. If the risk to individuals is high, you must also tell the affected people without undue delay. See the ICO personal data breach reporting page.
  • NCSC guidance. The NCSC publishes guidance specifically for early years settings, plus its Small Business Guide. Neither is mandatory, but both describe what a regulator or insurer would see as reasonable steps.
  • Cyber Essentials. The government backed Cyber Essentials scheme is voluntary for most settings, but local authorities and larger groups may ask for it, and it gives a useful structure. Our Cyber Essentials Guide explains the five control areas.

Parent apps and nursery management platforms

For most settings the parent app is the single most important system. It typically holds registers, observations, photos and videos, daily diaries, medication and accident records, invoices and messages with families. Treat its accounts the way a bank treats its own.

Administrator accounts

  • Keep the number of full administrators small: usually the owner or manager and one deputy. Record who they are.
  • Turn on two-step verification for every administrator, and for every staff account if the platform supports it. The NCSC recommends 2SV on important accounts so that a stolen password alone is not enough.
  • Give practitioners the lowest role that lets them do their job, for example adding observations for their room without access to finance or safeguarding records.
  • Never let the software vendor, IT provider or a consultant use your manager's own login. Ask for their own named support access, time limited where possible.

Staff logins on shared tablets

Shared room tablets are practical, but a single shared login means you cannot tell who did what, and you cannot remove one person's access without changing it for everybody. Where the platform allows it, use per staff PINs or named logins on the tablet. Set the device to lock after a short idle period, and require a PIN, pattern or biometric to unlock, as the NCSC recommends for all laptops, PCs and tablets.

Parent and carer accounts

  • Send invitations only to contact details confirmed on the registration form, and confirm any change of email address or phone number through a second channel before updating it.
  • When a child leaves, or when a court order or safeguarding concern changes who may see information, remove or restrict the relevant parent accounts promptly and record that you did so.
  • Check what a parent can download or share. Some platforms let families save photos that include other children; set expectations in your photo policy.

Questions to ask a platform vendor

  • Does the platform support two-step verification for staff and administrators, and can we make it mandatory?
  • Can we see an audit log of logins, exports and record access?
  • How will you tell us about a security incident, and how fast?
  • Can we remove a staff member's access immediately, including on devices that are offline?

Photos, images and children's records

Photographs are central to early years practice and are also the data that causes the most distress when exposed. A photo with a first name, a room name and a setting address can identify a child's location and routine.

  • Capture only on setting devices. Staff personal phones should not be used to photograph children. Use setting owned tablets or cameras that are enrolled, locked and can be wiped.
  • Store in one place. Photos should go straight into the parent app or a single approved storage location, not into device camera rolls, personal cloud accounts or messaging apps. Clear local copies regularly.
  • Separate consent from security. Parental consent decides whether a photo may be used, for example on a website or social media. Security decides who can see it. Record both.
  • Newsletters and social media. The NCSC advises password protecting newsletters that contain photos or child details, and reviewing social media privacy settings so only a child's carers can see content.
  • Retention. Decide how long learning journals and galleries are kept after a child leaves, delete or hand over to families in line with that policy, and confirm that the vendor deletes data too.

Where identity fits

For a small setting, identity is most of security. Nearly every serious incident involves someone using an account they should not have: a stolen manager password, a former employee's login, a shared tablet PIN known to everyone, or an attacker in the mailbox.

  1. One person, one account. Give every staff member a named login to email and the parent app. The NCSC notes that shared computers should ideally have separate accounts.
  2. Protect email first. The NCSC stresses a separate strong password for email because email access exposes payments and children's data and allows impersonation. Turn on 2SV for email before anything else. Our 2FA vs Two-Step Verification vs MFA guide explains the options.
  3. Strong, unique passwords. The NCSC suggests three random words and warns against reusing passwords. A password manager, or a browser's saved passwords, removes the temptation to reuse.
  4. Joiners, movers and leavers. Create accounts on the first day, adjust them when roles change, and remove them on the last day. The NCSC advises changing passwords when staff with access leave; with named accounts, you simply disable the leaver's account.
  5. Know your non-human accounts. Integrations, scanner and printer email accounts, payment provider connections and API keys used by the parent app are identities too. List them, know who owns each one, and remove the ones you do not use.
  6. Bank and payment accounts. Use 2SV, limit who can add payees, and require a call back on a known number before changing any supplier's bank details.

Implementation: a phased plan

First month: the basics

  • List every system that holds child or family data: parent app, email, cloud storage, accounting, funding portals, social media.
  • Turn on 2SV for email, the parent app and online banking for every administrator.
  • Replace shared logins with named accounts where the platform supports it.
  • Remove accounts for anybody who has left.
  • Turn on automatic updates on every laptop, PC, tablet and phone. The NCSC calls applying software updates one of the most important things you can do.
  • Check that backups exist for anything not held by the parent app, and test a restore.

First term: policies and devices

  • Write or refresh a short acceptable use, mobile phone and camera policy covering staff devices, photos and messaging apps.
  • Enrol setting tablets in a device management tool or the vendor's equivalent so that you can lock and wipe a lost device.
  • Agree a written process for changes to bank details and for suspicious messages.
  • Review the parent app vendor's data processing agreement and security commitments.

First year: assurance

  • Consider Cyber Essentials, either for a single setting or across a group. Our Cyber Essentials Readiness Checklist helps.
  • Run a one hour tabletop exercise: the parent app administrator account has been taken over on a Friday afternoon. Who does what?
  • Review access every term: who is an administrator, which integrations are connected, which parent accounts belong to children who have left.

Decision guidance: childminder, single nursery or group

Setting typeTypical positionPriorities
ChildminderOne person, personal devices, consumer email, one parent appSeparate work email with 2SV, device lock, automatic updates, photos only in the app, encrypted backups of any local files
Single nursery or pre-schoolSmall team, shared tablets, one manager as administrator, local IT supportNamed accounts, second administrator, leaver process, written bank details process, supplier questions
Nursery group or chainCentral office, many sites, shared platform, larger finance functionCentral identity provider with single sign-on, role based access by site, audit logging, managed devices, incident plan, supplier assurance, Cyber Essentials

Groups should be especially careful with central administrator accounts. One compromised head office account can expose every site's records, which is why larger groups benefit most from single sign-on, enforced 2SV and regular access reviews. If you rely on an outside provider, see Choosing an IT Support Provider or MSP Securely.

Detection and response

Small settings rarely have monitoring tools, but they can still notice the early signs of trouble:

  • Alerts from email or the parent app about a sign-in from a new device or location.
  • Rules in the mailbox that forward or delete messages, which nobody set up.
  • Requests to change bank details, or invoices that do not match.

If something goes wrong, the NCSC's early years guidance says to recover any hacked accounts, contact your bank if banking details were given, change passwords on any accounts that share a compromised password, and, if money was lost, report it to your bank and as a crime: to Report Fraud on 0300 123 2040 in England, Wales and Northern Ireland, or to Police Scotland on 101. Forward suspicious emails to the NCSC Suspicious Email Reporting Service and suspicious texts to 7726.

Then consider your data protection duties. Work out what data was affected and whether the breach is likely to risk families' rights and freedoms. If so, report to the ICO within 72 hours where feasible, and tell families without undue delay if the risk is high. Inform Ofsted and your local authority in line with their notification expectations, and keep a record of the breach and your decisions. The Data Breach Notification Checklist gives a step by step list, and for a ransomware event see the Ransomware Response and Recovery Guide.

Do not pay or negotiate with extortionists without professional advice and police involvement. Payment does not guarantee deletion; in the Kido case authorities had not independently verified the group's claim that it deleted the data.

Common failure patterns

  • One manager login used by everyone, with no 2SV, written on a note near the office PC.
  • Former staff and agency workers still able to sign in to the parent app months after leaving.
  • Photos of children kept in personal phone camera rolls or personal cloud accounts.
  • The software vendor or IT provider using the manager's own account for support.
  • Newsletters, websites or social media posts showing children's names and faces without the right consent.
  • Supplier bank details changed on the strength of a single email.
  • No idea who to call, or what to tell families, when a breach happens.

Lessons from incidents

In September 2025 the Kido nursery chain in London was hit by a group calling itself Radiant. According to a security vendor report by Bitdefender (a secondary source), the attackers stole photos, names, addresses and family contact details relating to around 8,000 children, demanded a ransom of about 600,000 pounds in Bitcoin, and posted some children's photos and profiles online when the company refused. The incident was reported to Action Fraud on 25 September 2025. On 7 October 2025 the Metropolitan Police announced the arrest of two 17 year olds in Hertfordshire on suspicion of computer misuse and blackmail. The group later claimed to have deleted the data, which had not been independently verified. Public reporting did not set out how the attackers got in.

The lessons for every setting are practical:

  • Children's photos are extortion material. Minimise where they are stored and who can bulk export them.
  • Assume that a determined attacker will target families as well as the business. Prepare a plain language message for parents in advance.
  • Refusing to pay was supported by police action; having an incident plan and contacts ready makes that decision easier under pressure.

For how stolen child data is later abused, see our Child Identity Theft Guide.

Practitioner checklist

  • Every system holding child or family data is listed, with a named owner.
  • Two-step verification is on for email, the parent app and online banking for all administrators.
  • Every staff member has a named account; no shared manager login remains.
  • At least two people can administer the parent app; vendors and IT providers use their own support access.
  • Leavers lose access on their last day, and parent accounts are reviewed when children leave.
  • Photos are taken only on setting devices and stored only in the approved system.
  • All devices lock automatically, require a PIN or biometric, and install updates automatically.
  • Backups of local files are made and a restore has been tested.
  • Bank detail changes require a call back on a known number.
  • Staff know the phishing warning signs and how to report a suspicious message.
  • An incident contact sheet lists the vendor, IT provider, bank, Report Fraud, the ICO, Ofsted and the local authority.
  • Access, integrations and policies are reviewed every term.

Standards and references

Related NHI Mgmt Group resources: Cybersecurity for Schools Guide · Small Business Cybersecurity Basics Guide · Cyber Essentials Guide · Child Identity Theft Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick both boxes to continue.