AI Privacy at School: A Practical Checklist for Teachers

For schools adopting AI, the most consequential privacy decision may happen before a teacher types a prompt: what information goes into the tool? A request for a Grade 5 science worksheet can be useful with only a learning objective. Uploading a student’s essay, learning plan, or family email can expose personal details that the task never needed.

That distinction makes privacy a practical part of lesson planning, feedback, and classroom communication. A tool’s ability to process a document doesn’t establish that a teacher should share it. The checks below help educators assess a proposed use before entering text, uploading files, or inviting students to sign in. School policies and approved tools determine which uses are authorized.

Start with the approved use

Check your school or district’s approved tools list, then confirm that approval covers the task you have in mind. Approval to generate lesson ideas may not extend to uploading assessment records, recording classroom discussions, or creating student accounts. If the tool or intended use isn’t clear, ask the staff responsible for educational technology or privacy before sharing student information.

The U.S. Department of Education advises teachers to check with school or district administrators before using online applications that involve information from students’ education records. The practical point is to assess the specific use, not just recognize the product name.

Give the tool only what the task needs

Many classroom requests work without personal information. A teacher can ask for a rubric, practice questions, or a simpler explanation by providing the learning objective and desired format. For example:

Create a Grade 5 science worksheet with short instructions, a vocabulary box, and an optional oral response.

This prompt describes an instructional need without disclosing a student’s diagnosis or educational history. The same principle applies when drafting feedback or adapting an activity: first consider whether a fictional example or a general description can produce a useful result. See AI Disclosure Statement Examples for Students for related classroom guidance.

Removing a name helps, but it doesn’t necessarily make a document anonymous. A school name, a distinctive incident, a rare medical condition, or a combination of family circumstances could still point to a particular student. Check comments, filenames, screenshots, and anything visible in the background. For demonstrations and experiments, a fictional example made from scratch is a safer choice.

Understand what happens after submission

Before entering school information, look for clear answers about how the service handles prompts, uploads, and conversations. Are they used to train or improve models? Can company staff or other service providers access them? How long are they kept, and what deletion options exist? Do the answers change between a personal account and a school account?

Ask your school’s technology or privacy team to clarify anything the service’s documentation leaves uncertain. Canadian privacy authorities identify limiting collection, explaining data practices, and providing appropriate safeguards as principles for privacy-protective generative AI. A setting that prevents model training may address one question, but teachers should also understand storage, access, and deletion.

Check that you’re signed into the account approved by your school. A familiar logo alone doesn’t tell you which account, contract, or settings apply. Review available controls for model training, conversation history, sharing, and connected applications, and follow the school’s requirements.

Check access before involving students

Before assigning an AI activity, find out whether students need accounts, whether the service permits their age group, and what permissions the school requires. Give students clear instructions about information they may enter. York Region District School Board, for example, tells students not to enter personal information about themselves or others unless specifically approved and guided by an educator.

Don’t ask students to enter an inaccurate birthdate or use a personal account to work around access restrictions. If a student can’t use the tool, arrange an appropriate alternative through school procedures. Student access and permissions need to be settled before the activity begins.

Include files, recordings, and connected services

The prompt box is only one way information can reach an AI service. A worksheet might contain student responses; a photograph can show handwritten work; a recording can capture a classroom discussion. An assistant may also request access to email, cloud storage, a camera, a microphone, or the page open in a browser.

Before uploading or granting access, check exactly what the tool can read and whether that access is needed. If a task concerns one document but a service asks to access an entire drive, review the scope with the school’s technology or privacy team.

Individual education plans, health information, safeguarding concerns, disciplinary records, assessment reports, and confidential family correspondence call for particular care. A tool’s ability to summarize them doesn’t establish permission to upload them. Keep confidential records within systems and processes authorized to handle them; for general planning, describe the teaching need without sharing the underlying record where possible.

Review sharing, retention, and mistakes

Before sharing an AI conversation or generated resource, check who can access it. An output may repeat details from its prompt, and a conversation link may expose more than the final answer. Follow school procedures for retaining and deleting material. Removing a conversation from your screen doesn’t necessarily mean every copy has been deleted.

If personal information is uploaded by mistake, stop adding to the conversation and promptly follow your school’s incident-reporting procedure. Record the tool, account, approximate time, and type of information involved. Avoid copying the sensitive material into more messages while seeking help. The school’s privacy or technology team can advise on containment and next steps, so teachers should know whom to contact before an incident occurs.

A final check before sending

Is this tool approved for this task? Does it need this information? Could the information identify someone? Do I understand what happens after I submit it?

Those questions apply even when AI is used only for a teacher’s own preparation. A student’s privacy can be affected by an educator’s upload as readily as by a student account. Requirements differ by location and school system, so the checklist is a prompt for everyday decisions; the school’s policies and privacy review determine which uses are authorized.

The post Teacher AI Privacy Checklist: What to Check Before Using AI at School appeared first on Educators Technology.