School privacy

Access, deletion and correction

A practical routine for requests about student data, anonymous Spaces, accounts and school use.

First version. Last updated: 5 August 2026.

Who should receive the request?

When 321school is used by a school, requests from students or guardians should normally go through the teacher or school first.

• The school decides how the tool is used in teaching.
• The teacher can often identify the correct Space, assignment or student display name faster.
• 321school can assist the school with technical deletion or access where needed.

Anonymous Spaces

Anonymous Spaces use a technical user ID and a display name chosen by the student. The student may not have a stable account across devices.

• Teacher can remove or archive a student from a Space.
• If the student used several devices, several anonymous technical users may exist.
• Requests should include Space name/code, display name and approximate time of use when possible.

Student accounts

For signed-in students, data can be connected to the account and may include saved work, feedback and profile information.

• Requests should include the account email or user ID if known.
• Deletion can affect saved work and access across devices.
• For children under 13, account use should be clarified with school or guardians.

Response and follow-up

The school should confirm the request and decide whether it concerns access, correction, deletion or restriction.

• Correct obvious errors in display names or membership where appropriate.
• Delete or archive data that is no longer needed for the school purpose.
• Escalate technical requests to 321school when school tools cannot handle the request directly.

Working version

This is a practical routine for early school use. A more formal process can be included in a data processing agreement when a school or school owner adopts 321school broadly.