In short
The LEARN mobile app sets no cookies — it is not a browser. It keeps a small amount of data in your phone’s own storage so it can work offline. The administration and partner web panels use cookies, but only the ones needed to keep you signed in. This legal site sets no cookies and runs no analytics at all.
1. This website
legal.learnumt.app sets no cookies. There is no analytics script, no advertising tag, no social embed and no third-party resource of any kind. The pages are static files and the only data your browser sends is the ordinary HTTP request needed to fetch them.
We mention it because a cookie page that only describes cookies elsewhere invites the reasonable assumption that this page is tracking you. It is not.
2. The mobile app
The app is not a web browser and does not use cookies. It stores data locally on your device, which is what lets your timetable open with no signal and your alarms ring with the app closed.
| What is stored | Why | Leaves your device? |
|---|---|---|
| Session token | Keeps you signed in between launches | Sent to our API to authenticate you |
| Cached timetable and reference data | So the app works offline | No |
| Cached theme and settings | So the app paints correctly before the first request returns | No |
| Alarm schedule and preferences | Alarms are scheduled on the device, not sent from our servers | No |
| Class colours and per-class reminders | They describe this handset rather than you | No |
| App-lock PIN | Unlocking the app on this phone | Never. Held in the phone’s secure keystore as a salted, repeatedly-hashed value |
| Push notification token | Lets a notification reach this device | Yes — sent to us and to the push service |
| Update and prompt state | So a prompt you dismissed does not reappear every launch | No |
Uninstalling the app deletes all of it, including the PIN. Deleting your account is separate — see Account & Data Deletion.
2.1 The university portal inside the app
Where your institution has published a portal address, the app can open it in an embedded browser. That is your university’s website. Any cookie it sets is theirs, governed by their policy, and we neither set nor read it.
3. The web panels
The administration panel, the partner developer portal and the event gate scanner are websites, and they use cookies and browser storage.
| Category | Purpose | Set by |
|---|---|---|
| Strictly necessary | Keeps an administrator, partner or organiser signed in; protects against cross-site request forgery. | LEARN and our sign-in provider |
| Functional | Remembers interface preferences, such as an open navigation section. | LEARN |
| Offline storage | The gate scanner keeps ticket data and queued scans in the browser’s database so a door works with no signal. | LEARN |
There are no advertising or cross-site tracking cookies on any LEARN surface.
Strictly necessary cookies do not require consent, because a panel that cannot keep you signed in is a panel that does not work. We do not ask for a consent banner for cookies we are not setting.
3.1 The gate scanner’s offline store
The scanner holds a manifest of ticket codes for the event it is working, plus scans not yet sent to our servers. The manifest deliberately contains no names — it is designed to survive on a lost phone without exposing who bought a ticket. It is cleared when the organiser signs out.
4. Controlling storage
- In the app — sign out to clear the session, or uninstall to clear everything on the device.
- In a browser — block or delete cookies in your browser settings. Blocking strictly necessary cookies will stop the panels working, because sign-in depends on them.
- Push notifications — turn them off in your device settings, or in the app’s notification preferences. The in-app record is still written either way.
5. Changes
If we ever add analytics or any non-essential storage, we will update this page before doing so and — where consent is required — ask for it first rather than adding a banner that assumes it.
Questions: privacy@learnumt.app.