Privacy policy
What data we process, why, and for how long.
Last updated: July 2026
Who decides what
The training provider that opens a session is the data controller: it decides to train a person, whether to record the session, and how long to keep the results. EduShell acts as a processor on its instructions. A learner wishing to exercise their rights should first contact the provider that enrolled them; we assist.
Data processed
| Data | Why | Retention |
|---|---|---|
| Trainer account: email address, name, organisation, role. | Create the account, authenticate by email link, apply permissions. | For the life of the account, then deleted on request. |
| Learner: email address, first name, optional pseudonym, join time, progress. | Grant access to the environment, track progress, evidence attendance as a training provider must. | As set by the training provider. |
| Terminal session recording, where one takes place. | Teaching review and, in exam mode, evidence of the assessment. | As set by the provider; deletable by them at any time. |
| Usage: environment run time, credit-hours, monthly statements. | Bill the organisation and let it check what it is billed. | Statutory accounting retention period. |
| Technical: IP address and browser tied to an open session, audit log of sensitive actions. | Account security, abnormal-use detection, traceability. | Short, tied to session validity. |
Session recording
Recording only happens if the training provider enabled it for the session. In that case the learner is told and must agree before entering: without agreement, entry is refused rather than silently recorded. When a session is not recorded, no consent is requested and nothing is captured.
Where the data is
Data is hosted with Contabo GmbH, in the European Union (Allemagne (Union européenne)). It is not transferred outside the European Union.
Your rights
You have the right to access, rectify, erase, restrict and object, and to lodge a complaint with your data protection authority. If you are a learner, contact the provider that enrolled you first: it holds the decisions concerning you.
Contact for any data-related question: to be completed
Cookies and local storage
We only store what the service needs: a secure session cookie (not readable by scripts) to keep you signed in, an anti-forgery token, and a few display preferences kept locally (theme, dismissed getting-started checklist). No advertising trackers, no third-party analytics - which is why no consent banner is shown.