This page translates the French document for ease of reading. French reference text.
1. Parties and scope to complete
- School or other controller: complete identity, address, representative, data protection officer and contact details.
- Project contact: Laurent BOST — Studiophel, a personal, non-professional project; contact@studiophel.fr. Contractual identity and necessary contact details must be specified in the agreement.
- Selected service: specify whether use is entirely local, on a school-managed server or on the public Studiophel server. Processing is not identical.
- Duration, individuals and operations: define project dates, audiences, strictly necessary data, access and exit arrangements.
2. Roles and purposes
The school must determine its processing’s legal basis, inform students and legal guardians and assess whether an impact assessment is needed. GDPR Article 6(1)(e) does not automatically apply to a game publisher merely because a school uses it.
Where Studiophel actually acts on the school’s behalf and documented instructions, the agreement must govern that processing. Processing whose purposes the publisher determines itself must be identified separately.
3. Data and recipients to describe
The scope may include technical identifiers, names or nicknames, school levels, groups, homework, answers, results, histories, backups and necessary settings. The privacy policy details the transmissions actually provided for. Profile data may be sent to the online server; an online-hosted public room must not be treated as a LAN room.
Main hosting uses IONOS in Europe. Services and contracting entities must be checked in the contracts. Browser features, voice and remote fonts must be assessed separately; no general absence of transfers outside the EEA is guaranteed.
4. Clauses to provide when Article 28 applies
- Process data only on documented instructions, including transfers, and report instructions contrary to applicable rules.
- Restrict access to authorised people bound by confidentiality.
- Define appropriate security measures, incident handling, permissions and backups. The technical description is not certification.
- Identify sub-processors, authorisation conditions and contractual safeguards; do not assume an agreement with the hosting provider has already been signed.
- Provide assistance for individuals’ rights, risk assessment and security obligations.
- Notify the controller of a personal-data breach without undue delay after becoming aware of it. The controller then assesses its obligations to notify the supervisory authority and affected individuals.
- At the end of the service, arrange return or deletion according to the applicable choice, including copies and any legal retention duties.
- Provide useful information and define appropriate audit or inspection arrangements.
5. Retention and project end
Effective periods appear in the privacy policy. The contract must not replace them with automatic purges that do not exist in the software. In particular, uninstalling does not erase accounts on the public server and no general school-year-end closure is automated.
The school must specify who deletes classes, homework and accounts, how backups are handled and how any restoration respects erasure requests already received.
6. Checks before agreement
- Parties’ identity and capacity; each party’s exact role.
- Necessary and optional processing; recipients and information for individuals.
- Legal basis and handling of minors’ requests.
- Hosting, processors, access, security and possible transfers.
- Periods, return, deletion, incidents and inspection arrangements.
- Validation by authorised representatives of the school and project.
7. Acceptance to formalise outside this page
School, representative and date: ____________________________________
Project contact, capacity, contact details and date: _______________________
The parties must retain the accepted final document, its annexes and instructions. To prepare this discussion: contact@studiophel.fr.