Skip to content

Privacy and digital self-determination

Digital learning tools also need scrutiny behind the interface: what data is processed, who receives it and how its use is limited.

Understanding where data goes

Teachers and learners see assignments, materials and feedback on a learning platform. Sign-in services or embedded content are less visible but may also process data. Those responsible therefore need to understand purposes, data flows and access rights, not just the functions on screen. Open code can help with technical inspection. It does not by itself establish how a service is configured, what contracts apply or how permissions and stored information are handled. Open source is not an automatic privacy guarantee.

Clarifying responsibility before use

Purpose, necessary data, access rights and deletion belong in the planning stage, including external services and embedded components. Addressing these questions early is preferable to discovering them after a tool has become part of everyday teaching. Public project accounts can generally explain the technology and experience without including learners’ personal information. Its presence in an example or screenshot is not a reason to publish it.

Sources and further information