Teacher Tools Rated
Menu
Skip to content

Using AI well How-tos Low effort15 min

Read an AI tool's privacy page before uploading pupils' work

A 15-minute, six-step check of an AI tool's privacy page: laws named, where data sits, AI training, pupil accounts and any data processing agreement.

Teacher Tools Rated 4 min read

What do you need before you start?

You need four things and about 15 minutes per tool. Gather them first so you do not stop halfway.

  • Your school’s AI and data policy, open in another tab.
  • The tool’s privacy policy link, taken from the tool’s own site.
  • A blank note with seven lines: tool, date read, laws, storage, training, pupil accounts, data processing agreement.
  • The name of your data protection lead, in case you need to ask a question.

Paste no pupil names or pupil work into the tool while you read. Reading a policy needs none of it. This guide is not legal advice, and a tidy note from you does not replace your school’s own approval.

What are the six checks, in order?

Work through six checks in a fixed order, 15 minutes in all.

  1. Open the tool’s own privacy policy and note the date on it (2 minutes).
  2. Find the laws it names (3 minutes).
  3. Find where data is stored (3 minutes).
  4. Find whether it says it trains AI on what you upload (3 minutes).
  5. Find whether pupils need accounts (2 minutes).
  6. Find whether a data processing agreement is published (2 minutes).

Write what the page says, using its words where you can. Where the page is silent, write “not stated on its site”. That is the wording our report cards use on the data and privacy line, and the method is set out in How we assess the tools. Silence is information. Do not fill it with a guess.

Which laws does the page name?

Write down exactly which laws the page names, because they differ from tool to tool. TeachMate’s page names UK GDPR and says it is ICO registered. MagicSchool’s policy names EU GDPR and UK GDPR, though the company is US first. Diffit says it is FERPA and COPPA compliant and does not mention GDPR or UK GDPR. Eduaide’s privacy center names no laws or certifications. Planit Teachers has a privacy policy written under UK law and names no certifications. FERPA and COPPA are US laws. For a UK school, a page that names UK GDPR gives you a claim to check against your policy. A page that names only US laws leaves a question to ask. Record each one as the tool’s claim, in the form “MagicSchool says”. Never record it as your own verdict.

Where is the data stored, and is it used to train AI?

Storage and training are two separate lines, so read for each one. Some pages name a place. TeachMate says data is stored in London on AWS with copies in Dublin. Chalkie says its main servers are in Amsterdam with backups in London. If the page gives no place, write “not stated on its site”. For training, look for one plain sentence. MagicSchool says it does not use personal or student data to train AI models. Brisk says student and teacher inputs are never used to train AI models. Diffit does not say either way, and neither does Planit Teachers. Aila’s wording has two parts. Oak says it sends no personal information to OpenAI and has opted out of OpenAI training on it, and it says inputs and outputs are stored to improve the service. Copy such wording whole. A silent page leaves the question open.

Do pupils need accounts, and is a data processing agreement published?

Pupil accounts and a data processing agreement are two separate lines, and each gets a yes, a no or “not stated”. Curipod says pupils have no accounts and offers a signed data processing agreement. Chalkie says pupils need no accounts and publishes an agreement, with UK/EU and US versions. Brisk publishes a data processing addendum. TeachMate offers a standard agreement. Planit Teachers needs no pupil accounts. It publishes no data processing agreement and asks schools that need a data-processing review to get in touch. Aila’s page mentions no agreement and says Aila is for teachers, not pupils. Note whether the page says “published”, “offered” or “mentioned”, because the three are different. For tools with clear answers on these lines, see 5 AI tools for teachers with the clearest data terms.

What if the page is vague or you run out of energy?

Stop after check 4 if you are tired, and mark checks 5 and 6 as not done yet. Then work through a fixed set of fallbacks.

  1. Write “not stated on its site” against every gap.
  2. Email the company one specific question, such as whether it trains AI on uploads.
  3. Hand your note to your data protection lead before anyone uploads.

Until your school has approved the tool, put no pupil names or pupil work into it. If you want to try it, use made-up sample text. Follow your school’s AI and data policy throughout. The guide Use AI safely in school: data, pupils and your policy covers that side in more detail.

What goes wrong, and how do you make it easier next time?

Avoid three mistakes, then keep one table so you only do this once per tool.

  • Reading the home page or a row of badges instead of the policy.
  • Treating FERPA and COPPA as if they were UK GDPR. They are different laws.
  • Skipping the date. Pages change, and a note with no date cannot be trusted later.

For next time, keep a table with one row per tool and the same seven lines as your note. Share it with your department, so one person’s 15 minutes covers everyone. Recheck a row when the tool changes its terms and at the start of each school year, and add the new date. Our own report cards are dated for the same reason.

Frequently asked questions

Is it safe to put pupils' work into an AI tool?

Only once your school has approved that tool. We never call a tool safe in our own voice, because a privacy page only tells you what the company says. Follow your school's AI and data policy, and ask your data protection lead if the policy is unclear. This is not legal advice.

What is a data processing agreement?

It is a contract between a school and a tool's company about how pupil data is handled. Of the tools we list, Chalkie publishes one, Brisk publishes an addendum, Curipod offers a signed one and TeachMate offers a standard one. Your data protection lead decides whether a given agreement is enough.

Does FERPA and COPPA compliance cover UK schools?

FERPA and COPPA are US laws, so a page that names only them says nothing about UK GDPR. Diffit's page, for example, does not mention GDPR or UK GDPR. If your school is in the UK, ask your data protection lead what it needs to see.

How can I tell whether a tool trains AI on what I upload?

Look in the privacy policy for one plain sentence about training. MagicSchool, Brisk, Curipod and TeachMate each say they do not use data to train AI models. If the page is silent, as Diffit's is, write "not stated on its site" and ask the company.

How often should I reread an AI tool's privacy page?

Reread it when the tool changes its terms and at the start of each school year. Put the date next to every note you make. A dated note shows how old your information is.