Today, DTBC launched a new report– What If We Took Stewarding Children’s Data Seriously?, and the first instalment of Let’s Do It Together advocacy tools.
Our report details the concerning implications of the rapid growth of educational technologies and apps (EdTech) in UK schools, with a focus on Black/Black heritage pupils. The Department for Education (DfE) and the Information Commissioner’s Office (ICO) need to provide better support and guidance to schools on reviewing and adopting EdTech. Still, there are also ways in which we can all be better stewards of children’s data. Our first set of advocacy tools is geared towards parents, guardians, and community members to get involved in questioning and checking the use of EdTech in our schools.
The 2020 COVID pandemic lockdowns and the shift to hybrid learning drove a dramatic rise in the use of EdTech in classrooms. This has created a booming multi-billion pound industry in the UK, with many tools collecting vast amounts of children’s personal and special category/sensitive data. Yet the data management practices of many EdTech platforms, which are commercial organisations, remain alarmingly opaque, leaving parents, guardians and educators in the dark about how this data is used now– and how it might be used in the future. The potential risks to our children’s data are grave, and we must act now to prevent any misuse.
Our report presents the findings from a community-led research project directly involving 99 parents and guardians, school staff and community members, research across 90 schools, reviews of 65 EdTech software and apps, and including community events reached almost 200 people. It centres the concerns of Black communities, however, the risks posed by EdTech stretch across other marginalised groups– particularly those from low-income households or with disabilities– and all children.
We seek to challenge the current paternalistic approach to children’s data– where schools and companies make decisions with minimal input from children, parents and guardians. This approach treats children’s data as a by-product of institutional or commercial operations, available to use with limited debate or pushback. With the increased use of data-centric technologies and a more permissive legislative attitude towards automated decision making, the use of children’s personal data can have long-lasting negative effects on their life pathways. Instead we call for a shift towards a stewardship mindset, where care and rights guide how our children’s data is collected, stored and used.
The report urges school leaders, local authority education teams, the DfE, and the ICO to adopt a stewardship mindset regarding children’s data, which focuses on care and rights above commercialisation and economic growth. Children, parents and guardians have an important role in demanding good stewardship to better safeguard children’s futures.
Here are ten key findings from the report:
- Many parents/ guardians and community members were unfamiliar with the term EdTech, but once explained, were able, and wanted to participate in further conversation. Only 36% of parents/guardians (n=14) had received information from their children’s schools about the use of EdTech.
- Parents/guardians with English as a second language faced additional challenges to understanding their children’s engagement with EdTech, with many unaware of its use.
- Parents, guardians and community members struggled to voice concerns about EdTech by themselves. Few civil society organisations with no vested interest in Edtech exist–and those that do are severely underfunded– limiting their ability to provide the context and vocabulary needed for informed public engagement.
- Schools receive limited guidance and support from institutional players such as the ICO and the DfE to help them make the right decision when procuring EdTech applications and platforms.
- There is a concerning lack of regulatory oversight of the activities of the private companies producing EdTech products. Conservative estimates of this £3.8 billion industry suggest there are hundreds of these suppliers in operation in the UK. There were approximately 1,200 EdTech companies operating in the UK as of 2021. Despite this, as of early 2025, only ten had been audited by the ICO in the last five years and the regulator is yet to publish its findings.
- For the majority (80%) of EdTech apps whose privacy notices we reviewed, we were unable to rule out their use of children’s personal data for unexpected commercial purposes now or in the future.
- Most EdTech apps (over 75%) facilitate targeted advertising to children either directly or on third-party sites by placing cookies (their own or other organisations’) on children’s devices.
- Most EdTech apps (over 75%) can potentially expose children’s personal data due to the length of time, amount and general opaqueness of data they hold.
- Many EdTech apps (over 60%) open the door to surveillance and profiling of children (especially those from marginalised groups) – now and in the future –by collecting an excessive amount of special category data and data from which children’s socioeconomic status can be inferred.
- Very little objective research to demonstrate the efficacy of EdTech apps used in schools or to substantiate claims made in suppliers’ literature. This also makes it hard for schools and parents/guardians to make a “value for money” judgement about EdTech apps. This was true for ALL the EdTech apps we reviewed.
As a community research project, surfacing answers to questions is important but not sufficient. Support is required to enable people to take action. Our first installment of our advocacy toolkit Let’s Do It Together provides resources for parents, guardians and community members to learn more about EdTech, understand the legal protections and rights they have to advocate with and for their children about their data; and provides templates for advocacy and queries to enable action. In the future we hope to develop resources for schools.
Read our new report here
Access our Let’s do it together advocacy toolkit: