AI guidelines

Guidelines for AI use in 321school

A practical overview of how AI should support learning, teacher work and school-controlled use without replacing adult judgement.

Working version. Last updated: 29 August 2026.

Core principles

AI output is a draft or suggestion, not a final professional judgement.
Teachers review and approve AI-supported content before it is used with students.
Students and guardians cannot publish public learning content from 321school.
Public publishing is limited to teacher, creator or admin roles and requires an active choice.
Student data should be kept out of prompts unless it is necessary, appropriate and approved for the school purpose.

Teacher review

AI may help create, adapt or suggest learning content, but the teacher remains the person who decides what is suitable for students.

Generated or pasted text should be reviewed before it becomes an assignment.
AI feedback suggestions should be checked and edited before they are saved or shown as teacher feedback.
Teachers should consider age, subject, language level and local school expectations before sharing AI-supported content.

Students and guardians

Student and guardian roles are designed for participation, self-study and follow-up, not public publishing on behalf of the school.

Students can answer tasks, receive feedback and use self-study features where enabled.
Guardians can follow or support learning flows where relevant.
Students and guardians cannot publish public library content or public course material from 321school.

Public publishing

Public publishing requires an active choice from a role with publishing access.

Teachers and creators should review title, text, tasks, images and metadata before publishing.
Published content should not include unnecessary personal information, student names or identifiable student work without clarification.
321school may unpublish, restrict or remove content that appears unsuitable or conflicts with terms, safety or privacy.

Images and media

Images can make learning content better, but they also need extra care in school contexts.

Avoid using identifiable photos of students or children unless this has been clearly approved for the school purpose.
AI-generated images used in public-facing material should be presented in a way that does not mislead people into believing they are real documentary photos.
Image prompts should avoid private, sensitive or identifying student information.

Personal data

AI prompts should use the least amount of personal data needed for the learning purpose.

Avoid health data, private family matters, special category data and unnecessary names or contact information.
Use anonymous or general examples when they are sufficient.
School use should follow the school's own assessment, routines and data processing agreement where applicable.

Moderation and reports

321school can take action when content or use appears to create risk, but moderation is not a promise of advance review.

Technical safeguards may block or limit some prompts, outputs or usage patterns.
Reports and support requests may be reviewed manually.
Access may be limited if needed to protect users, privacy, service stability or compliance with terms.

For school assessment

These guidelines are meant to support school review and everyday use. They should be read together with the privacy overview, sub-processor list, terms and any data processing agreement with the school owner.

Privacy for schools Sub-processors