Skip to main content

Data protection in schools

Sharing personal data

Who you can share personal data with and what you need to consider, for example, when you are safeguarding pupils or when pupils transfer to another school.

To keep children and young people safe in school, schools need to share information appropriately so the correct decisions can be made to protect them.

Schools may need to share staff and parent or carer personal data. For example, to support:

  • safeguarding

  • attendance management

  • training courses or professional development

  • statutory collection such as the school workforce census

  • schools to carry out their statutory functions

There must be a valid reason and a lawful basis to share personal data. If you are sharing special category data then you also need an additional condition for processing this personal data. This is because the data is sensitive and requires an extra layer of protection. Sharing children’s data with third parties can expose them to unintended risks if not done properly. Children’s data requires extra protection because they are less aware of the privacy risks and could have different developmental needs.

If there is a high risk to the rights and freedoms of individuals then a data protection impact assessment (DPIA) must be carried out before sharing personal information about pupils. It may not be necessary to complete a DPIA for a one-off data share, but for routine or planned data sharing activities a DPIA must be considered. You should discuss this with your data protection officer (DPO) to understand whether a processing activity is high risk and requires a DPIA. Whenever you decide that a DPIA is not necessary you should record the reasons for that decision.

Internal policies should be updated, so staff are aware of who is authorised to make decisions on sharing personal data and for staff to consult with your DPO if there is uncertainty. Your privacy notices must be regularly reviewed and updated in line with any changes to the processing of personal data.

The Information Commission has a data sharing information hub that includes further guidance on data sharing. Any data you share must comply with their data sharing code of practice.

Appropriate documentation to support a data share

When routinely sharing personal data outside of the school, there must be appropriate documentation in place. This could include a data sharing agreement. Data sharing agreements promote adherence to data protection laws and should define:

  • roles and responsibilities of all organisations involved

  • aims and purposes of sharing personal data

  • what personal data is going to be shared including any special category data

  • the lawful basis for sharing the personal data

  • procedures for complying with individual rights requests such as a subject access request

  • information governance such as responding to a personal data breach

How to decide the most appropriate lawful basis

Before sharing any personal data, you need to identify the lawful basis. You should always have a compelling reason  for sharing personal data relating to children.

There are different lawful bases that you could consider. The most appropriate lawful basis will depend on the purpose for sharing the personal data. Schools are most likely to rely on:

  • public task, if you need to use or share personal data to allow you to carry out your official duties such as providing learning to pupils

  • consent, if the activity is not part of your core functions and you need consent to share – if you rely on consent, further specific guidance on using consent as a lawful basis in the Taking and using photos and videos, and using CCTV in schools guidance

  • legitimate interests, if the activity is not part of your core functions and you need to use or share personal data because you or a third party have legitimate interests

Depending on the purpose of the sharing, there are occasions where schools can also rely on:

  • contract - where your use of the data is necessary for a contract the school has or will have with the individual concerned

  • legal obligation - where your use of the data is necessary to permit the school to comply with the law

  • vital interests - where your use of the data is necessary to protect an individual’s life

The ICO provides a lawful basis interactive guidance tool that may help you identify the most appropriate lawful basis.

Safeguarding

To keep children safe and make sure they get the support they need, you can share information with other schools, children’s social care teams, health partners and the police.

You should consider the lawful basis to use, such as public task. This is because safeguarding forms part of a school’s official functions. It’s not usually necessary to ask for consent to share personal information for the purposes of safeguarding a child. It is not the most appropriate lawful basis to use because the consent must be:

  • specific

  • freely given

  • unambiguous

  • time limited, with the ability for it to be withdrawn at any point

Sharing information is vital for safeguarding a child, and data protection laws should not be seen as a barrier. The information sharing duty guidance is in development and will provide further detail on this.

Your designated safeguarding lead will decide if personal data needs to be shared. If the designated safeguarding lead is unavailable, then there must be an appropriate officer able to make these decisions in their absence. This is to ensure a child can be safeguarded without any undue delay. They should review your safeguarding policy and must make sure they record:

  • who they’re sharing that information with

  • why they’re sharing the data

  • whether they have (or need) consent from the pupil, parent or carer

You may receive requests from the police as part of an investigation or safeguarding enquiry. The fact that a request comes from the police does not mean that you are automatically required to disclose all information requested.

Each request should be considered on a case-by-case basis. Schools should:

  • establish the identity and authority of the requester

  • understand the purpose of the request

  • consider whether all of the information requested is necessary and proportionate

Where appropriate, schools should limit disclosure to the minimum amount of personal data possible.

Keep a record of:

  • the request

  • the information shared

  • the lawful basis relied upon

  • the rationale for the decision

If there is any uncertainty, advice should be sought from your DPO, unless an urgent safeguarding or life-threatening situation requires immediate action.

Example: sharing information with the police

A school receives a request from a police officer who is carrying out safeguarding enquiries regarding a pupil. There have been several domestic incidents at the family home over the last 6 months. While there are no immediate child protection concerns, the police would like to assess the pupil’s welfare and understand if further support is required.

The police officer requests:

  • pupil’s attendance records

  • information about the pupil’s wellbeing

  • details of safeguarding or behavioural concerns about the pupil recorded in school

  • a copy of the pupil’s full educational record

The school verifies the request is valid and considers the purpose of the request and whether each category of information is necessary and proportionate.

The attendance record, wellbeing information and relevant safeguarding and behavioural concerns may assist the police in their enquiries. However, the school concludes that the pupil’s full educational record is not necessary for the purpose described and contains information that is unrelated to the enquiry.

The school records the request, the information disclosed and withheld, the lawful basis relied upon and the reasons for the decision.

Read Working together to safeguard children to find out more information about sharing a pupil’s safeguarding file. You should also refer to the safeguarding section of Keeping children safe in education.

Sharing data with local authorities and government

You may need to share personal information about your pupils with local authorities, government or children’s services. Such as when a pupil is being reviewed for an education, health and care (EHC) plan.

Sharing information can help provide appropriate services that safeguard and promote the welfare of children. The Data Protection Act 2018 and UK GDPR provides a framework to make sure that personal information is shared appropriately.

Before you share any data, you must:

  • consider all the legal implications of sharing the data

  • identify the lawful basis on which  to share the data

  • confirm who needs the data, what data is needed and what they’ll use it for

  • make sure that you have  the ability to share the specified data securely

  • check that the actions cannot be completed or verified without the data

  • only share the minimum amount of personal data required for the specific purpose

  • share the data securely, keep a record of what was shared and speak to your DPO if you are unsure

You also have a statutory requirement to share personal data about your pupils with DfE through the school census. You do not need to get consent from pupils, parents or carers to share this data with DfE. You can rely on public task because it is a statutory collection that forms part of your functions.

You should provide information about what data you share in your privacy notices. Privacy notice model documents suggest wording to explain to staff, parents, carers and pupils what data the school is collecting and sharing.

Example: sharing data about a looked after child with a local authority

A school is in one local authority area but has a looked after child who is placed by a different local authority. The school receives a request from the placing local authority for information to support the pupil’s care planning, education and safeguarding.

The school checks which local authority has responsibility for the child and why the information is needed. This may include confirming whether the request is from the child’s social worker, virtual school head or another named contact acting on behalf of the local authority.

The school only shares the information needed for that purpose. For example, it may share attendance information, attainment, behaviour, relevant safeguarding concerns or details of support already in place. It should not share the pupil’s full education record unless this is necessary and proportionate.

The school shares the personal data securely with a named contact at the local authority. It records what was shared, who it was shared with, the lawful basis relied on and why the sharing was necessary. If there is uncertainty, the school should speak to its data protection officer before sharing the information.

If the school regularly shares personal data with another local authority, for example because a looked-after child is placed by that authority, it should check whether a data sharing agreement is needed. This can help both organisations be clear about what data is shared, why it is shared, each organisation’s responsibilities, how the data will be kept secure and how long it will be kept.

A data sharing agreement may not be needed for a one-off request, but the school should still record:

  • the request

  • the lawful basis relied on

  • what was shared

  • why the sharing was necessary

You may also need to share personal data about staff. This can include information needed for:

  • statutory returns

  • workforce planning

  • payroll

  • pensions

  • safeguarding

  • professional development

For example, schools and local authorities may share staff information with DfE through the school workforce census. This can include details about teachers and other school staff, such as:

  • their role

  • contract

  • pay

  • qualifications

  • absence

  • vacancies

You do not need to ask staff for consent where the sharing is required by law or is necessary for you to carry out your official functions.

You should be clear with staff about what personal data you collect, who you share it with and why. This should be explained in your staff privacy notice. The privacy notice should also explain the lawful basis you rely on, how long the data is kept, and the rights staff have over their personal data.

Before sharing staff personal data, you should make sure the sharing is necessary and proportionate and only share the minimum amount of information needed for the purpose. You should also use an appropriate secure method and keep a record of what was shared, who it was shared with, the lawful basis relied on and why the sharing was necessary.

Sharing data with other schools

You may need to share personal data if:

  • a pupil moves school

  • you are working with another school

  • you are arranging a collaborative school trip

If a pupil moves to another school, you must transfer their records to the new school. This includes the pupil’s common transfer file and educational record. You must:

  • make sure you transfer the data securely

  • transfer the record within 15 days of getting confirmation the pupil is registered at another school

  • ensure the child protection file is transferred as soon as possible and within 5 days for an in-year transfer or within the first 5 days of the start of the new term, as detailed in the Keeping children safe in education statutory guidance

  • transfer the child protection file separately to the main pupil file and confirm that it has been received by the new school

  • be able to trace the record during the transfer

To securely share and transfer pupil records, you could:

  • use the  school to school (S2S) system

  • send them to a named person using an encrypted email

  • ask your local authority to transfer them

  • deliver any paper records in person or ask the new school to collect them

There may be occasions where you regularly share personal data with another school. For example if a pupil remains on their current school roll but attends other schools or organisations as part of their alternative provision. Also if a pupil has dual registration and attends another school on a temporary basis, such as a pupil referral unit, a hospital school or a special school. You may need to regularly share information to ensure the pupil has a continuation of education.

These data shares should all be secure and handled with the same approach, whether it’s a small request on an ongoing matter or a full file share.

If you are organising a school trip with another school, you will need to share data with them to confirm which pupils and staff are going. You may also need to share details such as dietary requirements or medical information to make sure pupils are safe.

Review and document the lawful basis that you are using to share this information to ensure that it is appropriate. Where you already have consent for holding the information, make sure this also covers sharing it.

Example: Sharing pupil personal data to arrange a school trip

A sixth-form school is arranging a visit to the House of Commons to observe a debate to support the learning of a politics A level. The school is part of a multi-academy trust (MAT) and another school within this has a very small sixth form. The larger school is likely to have space to accommodate more pupils on the trip and offers the places to the smaller school.

The smaller school shares pupil names and relevant health information with the larger school arranging the visit. This is to ensure the needs of all pupils can be accommodated such as appropriate access if there are mobility requirements.

A teacher from both schools will be present, with access to the pupil’s personal data including emergency contact details, so no further personal data needs to be shared with the school arranging the trip.

The school shares this personal data using the lawful basis of public task. While consent is not required to share personal data, parents and carers are advised in advance and it is documented in a privacy notice.

The sharing of personal data is proportionate to the activity, for a specific purpose and can be deleted in line with retention schedules when the trip has ended.

Sharing data with other organisations

There may be occasions when you wish to share pupil or parent information with organisations for the purposes of organising school trips, extra-curricular activities or for providers of EdTech tools to support learning.

For example:

  • pupil dietary requirements

  • health conditions

  • emergency contact details

  • pupils’ personal data such as date of birth or address

  • pupils’ name and school class

  • parent or carer name and email address

Where personal data is being shared, you must identify the appropriate lawful basis for doing so. For any special category personal data, an additional condition is required. Any data that is shared is held securely, not retained by the organisation for longer than is necessary, and that it is only used for the purpose described.

Example: Sharing personal data to use EdTech tools

A school has decided to use a third-party maths tool to support pupils in their learning. The school consults their data protection officer and ensures it has the appropriate agreements in place with the organisation.

The school shares teaching staff names and emails addresses in addition to pupil names and class details using the lawful basis of public task. This is the minimum amount of data required to create accounts and provide content to the pupils.

The privacy notice is updated and parents and carers informed of how the pupils’ personal data will be processed as part of this activity.

School immunisation programmes

You will need to provide data to support immunisation programmes, which includes routine vaccines and outbreak responses in the school. This includes: 

  • sharing information leaflets and consent forms with parents or carers

  • providing a list of eligible children and young  people, and their parent’s or carer’s contact details to the School Age Immunisation Service (SAIS) team

Sharing these contact details does not mean that a vaccine will be given. A parent or carer will need to give their consent for a vaccine to be given to their child.

There is a lawful basis for you to share information with school immunisation teams under article 6(1)(e) of UK GDPR. This states that the information can be shared if processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.

This means that you can share this information with immunisation programmes as it is in the public interest.

Sharing information with immunisation programmes is part of the exercise of your official authority. You also have a duty to support wider public health.

Data protection laws do not prevent you from sharing personal data where it is appropriate to do so in a fair and lawful way, and in this instance it is beneficial to do so

Example: ensuring data subjects have their rights respected when using biometric data

If you use pupils’ biometric data as part of an automated biometric recognition system, such as using fingerprints to receive school meals instead of paying with cash, you must comply with the requirements of the Protection of Freedoms Act 2012.

Parents and carers must be notified, and you must obtain written consent from at least one parent or carer before you take and process any biometric data from their child. If any parent or carer objects, then you cannot process this type of personal data. If a pupil does not want their biometric data processed, you must not process it even if their parent or carer has given consent.  

Provide an alternative means to access the relevant services for any pupil you do not have consent from. For example, pupils must be able to pay for school meals using cash at each transaction, if they wish.

If a parent or carer withdraws consent, or the child objects, then delete any relevant personal data already captured.

Once the child turns 18, they are able to consent themselves and parental consent is not required.

You also need to get consent from any staff members using your biometric system. Staff can withdraw their consent at any time and you must then delete any relevant data already captured.

Guidance is available on protecting children’s biometric information in school.

Publishing exam results

UK GDPR does not stop you from publishing exam results online or in the local press.

You do not need to get consent from pupils, parents or carers to publish exam results. However, you should tell pupils where and how their results will be published before they’re published. This gives them an opportunity to ask you to remove their results from the list should they wish to.

If a pupil makes a subject access request (SAR) for their exam results before they are published, you do not have to respond within the legislative one calendar month. You must respond either within five months of the request or within 40 days from when the results are published, whichever is earlier.

The Information Commissioner’s Office has more information about exam results and data protection.