Artificial intelligence (AI): dos and don'ts for data protection

Take a look at our tips to make sure you stay compliant with data protection around the use of artificial intelligence (AI) tools. Share them with your team to make sure everyone is on the same page.

Last reviewed on 24 May 2024See updates
School types: AllSchool phases: AllRef: 46617
  1. Don't enter sensitive information into a tool you don't trust
  2. Don't allow pupils' original work to be used to train AI without their consent
  3. Don’t click on suspicious links or reply to an email you don’t trust
  4. Do make sure staff training is up to date
  5. Do share AI privacy information with pupils
  6. Do update your data protection policy 
  7. Do look out for updates from your suppliers
  8. Do think about the impact of new apps and services that use AI
  9. Try out The Key's new AI-powered assistant

Don't enter sensitive information into a tool you don't trust

You shouldn’t enter sensitive data into a generative artificial intelligence (AI) tool if you’re not sure how it will use or store the data. Many tools are available as personal or consumer products, so they may not meet the legal requirements for data handling.

Technology platforms and products (such as MIS and cloud storage) are increasingly using AI. However, many of these are designed to be used by companies and will comply with your data handling requirements.

You should avoid entering data into:
  • Consumer products that aren't designed for sharing institutional data
  • Tools which don't align with your data practice processes – for example, ones that allow your data to be used for AI training
See the section below for advice around making sure your current suppliers remain compliant.

Personal data: information from which someone can be directly identified, or

The Key has taken great care in publishing this article. However, some of the article's content and information may come from or link to third party sources whose quality, relevance, accuracy, completeness, currency and reliability we do not guarantee. Accordingly, we will not be held liable for any use of or reliance placed on this article's content or the links or downloads it provides. This article may contain information sourced from public sector bodies and licensed under the Open Government Licence v3.0.