Open the management system archive to search for the record of a child enrolled this year. The list also includes names of children who left the facility five years ago, photos from a party that no one has looked at since 2021, certificates uploaded and never opened again. No one decided that they should stay there: simply, the opposite was never decided.
This is the most common situation in nurseries and preschools, and it is the opposite of the risk that is usually feared. Let's see why accumulation is a problem, why improvised cleaning is another, and which method allows for organization without removing what was needed.
Almost no facility has a retention procedure
Ask a coordinator how long the data of a child who no longer attends remains in the systems. Almost always, the answer is not a number: it is a puzzled expression. Not out of superficiality, but because the topic has never come up as a decision to be made. There has been attention to consents, information, and access security. What happens afterwards has never been brought to the table.
The result is that everything remains. Forever. And since no one has decided, no one has even written it down: there is no document stating how long a category of data is kept and who should intervene when that time has passed. The management system does its job, retaining, and the archive grows without anyone governing it.
What accumulates, without anyone noticing
It is worth looking at the material that layers in a 0-6 facility. They are very different categories, and that is already the first clue: they cannot have the same fate.
- Registration forms of enrolled children and contact details of families, including authorized persons for pickup.
- Health documents and certificates uploaded at the time of enrollment or during the year.
- Diary photos and videos, the heaviest part of the archive and the one that grows the fastest.
- Administrative and accounting documents, receipts, attestations delivered to families.
- Communications and messages exchanged with families over the years.
- Staff data: educators, teachers, and caregivers who no longer work in the facility, with documents and schedules.
Each serves different needs: some are required for administrative and accounting obligations, others only while the child attends, others exist because a family has given consent that can be withdrawn. Treating them as a single block makes decision-making impossible.
The second problem: hasty cleaning
Sooner or later, something forces intervention: space runs out, an audit arrives, a new coordinator comes in and finds the archive unmanageable. Then the opposite and equally delicate reaction kicks in: everything is deleted quickly, in one afternoon, alone.
Those who clean in these conditions think in terms of enrollment year, not data category. They delete everything related to children who left three years ago and also take away the receipts that were needed for administration and the annual report that was necessary for accreditation. Months later, one realizes when someone asks for a document that no longer exists.
Accumulating without deciding and deleting without distinguishing are the same mistake seen from two sides: a conscious choice is missing upstream.
The method: decide first, extract, then delete
The sequence is simple and must be followed in order: skipping a step turns a good intention into a mess.
- Decide first. Write down the categories of data you handle and, next to each, the retention period and the reason. The timeframes are set by the consultant or DPO, but you build the map of categories: no one knows your archive better than those who use it every day.
- Extract. Before touching anything, bring out of the system what must survive: records, annual reports, individual child reports, accounting documents. Save them where you have established, in a format that you can reopen in years. This is the step that almost everyone skips, and it makes the difference between a cleanup and a loss.
- Delete. Only now intervene on the archive, category by category, following the table from point one. And note what you have deleted and when: a procedure without a trace of its execution is worth half.
Retention periods are not decided by the software
On this, it is important to be clear, as it is the point where most misunderstandings arise. No management system can tell you how long to retain the data of your facility. That period depends on the type of data, the legal basis for processing, administrative and accounting obligations, the rules of your Region, and agreements made with families. It is an assessment that falls to your consultant or DPO, and it must be put in writing.
The task of the software is another, and equally important: to enable you to apply that decision. If one category must be retained and another must not, you must be able to extract, disable, and delete selectively, without needing help from a technician and without choosing between keeping everything and losing everything. A management system that does not allow you to perform targeted cleaning is imposing a retention policy that you have not chosen.
Questions to bring to the consultant or DPO
If the topic has never been addressed, come to the meeting with the questions ready. Here they are.
- For each category of data we handle, how long do we retain it and based on what?
- What changes when a child no longer attends: which data remains, which must be removed, which can remain in reduced form?
- Do the photos and videos of the diary follow the same rule as other data, or do they have a path linked to family consent?
- Do the data of staff who have left the facility follow different timeframes than those of children?
- What must we extract and archive outside the management system before deleting, and in what format?
- Who executes the deletion, how often, and where do we note that it has been done?
- How do we respond if a family requests deletion or a copy of their child's data?
The answers become your retention document. One single page, reviewed once a year, is already more than almost every facility has today.
What the management system must allow you
Once the decision is made, tools are needed to make it applicable. Easy.School is a cloud management system for nurseries and preschools, from a Roman software house active since 2010 and used by over 1000 facilities. Here are the points concerning retention.
- Disable instead of delete. Children and staff who are no longer part of the facility can be disabled while keeping the history, or deleted entirely. Two distinct choices: you decide which to apply and to whom.
- Mass deletion of photos and videos. Older content can be deleted in bulk to free up space, without selecting them one by one.
- Unlimited and included export. Records, annual reports, individual child reports, bulk download of accounting documents, export in PDF, Excel, and CSV. This is what makes the "extract" step possible.
- Documents always re-downloadable. They are uploaded choosing visibility — single child, section, campus, or entire facility — and can be re-downloaded when needed, even in compressed archive.
- Access and traceability. Permissions are customizable by role and there is a log of actions on the database tables: knowing who did what is part of the procedure.
- Where the data is stored. Each facility has a dedicated database and data is stored in the European area. Photos and videos are not public links but signed addresses that expire after one hour, on space dedicated to the single license.
- Ready documentation. The appointment act for the data processing manager is downloadable and there is a designated DPO: two documents that the consultant will ask for.
Regarding space, to have a rough idea: the included provision starts from 4 GB for the first 20 children and grows by 0.2 GB for each additional child, and it is possible to purchase additional space. Knowing this helps to plan cleaning calmly, instead of improvising when the archive is full.
In summary
In 0-6 facilities, the problem of retention is not excessive deletion: it is the accumulation that no one has chosen. And the late reaction — emptying the archive in one afternoon — also takes away what was needed. The sequence is always the same: decide first with the consultant or DPO, extract what must survive, then delete selectively.
The management system does not set the timeframes for you: it must allow you to apply your decision, category by category. Do you want to see how exports, disabling, and archive cleaning work? Try Easy.School for free.
