Why this guide

Digital projects in class create valuable learning opportunities but also raise privacy concerns for students. This guide turns the principle of "privacy by design" into concrete actions teachers can apply day to day, without advanced technical skills.

Core principles (practical explanation)

  • Minimize data collected: ask which information is truly necessary for the learning goal. Avoid collecting sensitive data (e.g., health, religious beliefs) unless strictly necessary and justified.
  • Privacy by default: configure activities so they share the least possible data by default. For example, use private accounts or workspaces with limited visibility.
  • Clear transparency: explain to students and families in plain language what data will be collected, why, how long it will be kept, and who can access it.
  • Protect from the start: include simple measures such as strong passwords for shared accounts, limiting who can download or edit files, and choosing tools with secure default settings.
  • Document decisions: keep a simple project sheet that records data-related decisions (who approved, when, purpose, retention period).

Before starting a project: quick checklist

  1. Define the educational purpose and expected outcomes.
  2. List the types of data that will be produced or collected (names, photos, texts, audio/video recordings, answers).
  3. Consider whether the same outcome can be achieved with less or non-identifying data (anonymous/pseudonymous).
  4. Select tools and services checking:
    • ability to set private accounts;
    • where data are stored (local or cloud) and whether this is clear from the provider's policy;
    • whether the provider allows limiting external sharing.
  5. Plan how to obtain consent: inform families, request permissions when needed, and keep authorizations.
  6. Define retention period and deletion method.

Managing consent and communicating with families

  • Use plain language: avoid jargon and explain in a few sentences what will happen to the data.
  • Differentiate between general information (privacy notice) and formal consent (when written authorization is needed).
  • For minors, follow your local school authority rules: parental consent may be required for publishing photos or videos.
  • Organize and store permissions (paper or digital) and note expiration dates.

Protecting data in the classroom (practical measures)

  • Prefer anonymization or pseudonymization when possible: use codes or initials instead of full names.
  • Limit access: only teachers or involved students should access project materials. Remove access when no longer needed.
  • Set automatic deletion reminders: schedule reminders to delete recordings or files at the end of the project.
  • Secure storage: use password-protected folders and school-managed backups. Avoid storing sensitive data on unprotected personal devices.
  • Passwords and encryption: where permitted, use tools that support strong passwords and encrypt particularly sensitive data.

Choosing digital tools

  • Assess privacy in terms of terms of service: prefer options where student data are not used for advertising profiling.
  • Choose school-approved solutions or those recommended by your IT office.
  • When using external services, arrange simple agreements with the provider about data handling (ideally via your institution).
  • Prefer tools that allow teacher control (e.g., virtual classrooms with roles and permissions).

Teaching privacy as part of the project

  • Include practical exercises for students: how to choose strong passwords, how to recognize sensitive information, how to set privacy on a profile.
  • Use concrete examples and role-play: simulate requesting permission, decide which data are necessary for a research task.
  • Give students responsibilities: small groups can manage the security of materials and verify authorizations.

In case of doubt or incident

  • Identify the privacy contact person at school or the IT office.
  • Isolate the problem: limit access to compromised materials.
  • Document what happened, when, and which data might be involved.
  • Inform school leadership and, if required by school procedures, families promptly.
  • Follow your institution's guidance for notification and remediation.

Simple operational model (adapt as needed)

  1. Before the project: complete a project sheet with purpose, data, tools, required permissions, retention period.
  2. During the project: keep a log of key accesses and changes.
  3. After the project: delete unnecessary materials, archive what is kept according to rules, and update the project sheet.

Conclusion: practical and repeatable

Privacy by design in schools is not about complex technical work: it's a routine of deliberate choices, clear communication with families and minimal documented procedures. With a short checklist and a repeatable routine, teachers can protect students' privacy without advanced IT knowledge.

Resources and tools

  • Consult your school's procedures and the local IT office's guidelines.
  • Look for privacy notice and consent templates for schools and adapt them to local rules.

Legal note

This guide provides practical advice and does not replace legal counsel or national/local regulatory requirements. Always verify rules with your school authority and applicable laws.