The short version
We collect what the app needs to work: who you are, where you study, your timetable, your coursework, your messages and — only if you ask to be verified — your identity documents. We do not sell any of it, we do not use it to profile you for advertising, and your app-lock PIN never leaves your phone. You can get a copy of your data, correct it, or have it deleted, by writing to privacy@learnumt.app.
1. Who is responsible for your data
LEARN (“we”, “us”) operates the LEARN mobile app, its API and its web panels, and is the controller of the personal data described in this policy. Contact us at privacy@learnumt.app.
One important division of responsibility runs through this whole document:
| Data | Who decides what happens to it |
|---|---|
| Your account, wallet, messages, device settings, identity documents | LEARN is the controller. |
| Your timetable, exam dates, seat allocation, classroom membership, marks | Your university or institution decides this; LEARN processes and displays it for them. |
| Your mobile money account and the payment itself | Your mobile money operator and our payment provider. We never see your credentials. |
Where your institution is the origin of the data, a request to change it may need to go to them. We will tell you if that is the case rather than leaving you waiting.
2. What we collect
2.1 Information you give us
- Account details — your name, email address, and a password. If you sign in with Google or Apple we receive your name and email address from them; we never receive your Google or Apple password.
- Profile details — your institution, programme type, faculty, department, level and role (student or lecturer); optionally a phone number, a student or staff identity number, and a profile photograph.
- Content you create — chat messages, coursework and submissions, files and materials you upload, and anything you type into an AI feature.
- Identity documents — only if you request verification. See section 3.
- Correspondence — what you send us when you contact support, and our replies.
2.2 Information we receive from your institution
Your class timetable, examination timetable, examination seat placement, classroom membership, assignments set for you, and marks or feedback recorded against your submissions.
2.3 Information generated by your use of the app
- Device and technical data — platform (Android or iOS), app version and build number, a push notification token, IP address and request timestamps, and diagnostic information when something fails.
- Activity data — when you last signed in and were last active, which is used to award activity points and to identify dormant accounts.
- Usage counters — how much of a daily AI allowance or a plan limit you have used, counted per account per UTC day.
- Notification records — what was sent to you, and whether your device acknowledged delivery.
2.4 Financial information
Your LAN Coin balance and its transaction history; purchases, subscriptions and ticket orders; withdrawal and payout requests; receipts; and a reference number plus the name of the mobile money service you chose (for example Orange Money or Afrimoney) for reconciliation.
What we never receive
We do not receive, process or store your mobile money PIN, your bank details or a card number. A payment is completed inside your mobile money service, and what comes back to us is confirmation and a reference.
2.5 What stays on your phone and never reaches us
Some data is deliberately kept on the device only:
- Your app-lock PIN. It is stored in your phone’s secure keystore as a salted, repeatedly-hashed value. It is never transmitted to us, we cannot read it, we cannot reset it, and we could not disclose it if we were asked to. If you forget it, the answer is to sign out and sign in again.
- Biometric data. Where you unlock with a fingerprint or face, the match happens on your device through the operating system. LEARN receives only a yes or no, never the biometric itself.
- Device preferences — alarm opt-in, class colours, per-class reminder choices — because they describe this handset rather than you.
- Cached copies of your timetable, the theme and reference data, so the app works offline.
3. Identity documents
If you request verification, we ask for identity documents — typically a national identity document, a photograph of yourself, and a student or staff identity number. This is special category-sensitive material and we treat it accordingly.
- It is submitted only when you choose to be verified. Verification is not required to hold an account or to use the core of the app.
- It is stored privately and is not addressable by URL. Unlike ordinary images in the app, no shareable or signed link is ever issued for an identity document. It can be read only through an endpoint that re-checks, on every single request, that the person asking is you or an authorised administrator.
- Access is limited to the administrators who review it, for that review.
- It is used for one purpose — confirming you are who you say you are — and for no other.
- It is deleted when it is no longer needed, as set out in section 8.
You may withdraw a pending verification request, or ask us to delete documents already submitted, by writing to privacy@learnumt.app. Deleting them may remove features that require a verified account.
4. Why we use it, and on what legal basis
We use personal data only for the purposes below. The legal bases named are those in the UK and EU General Data Protection Regulation, which we apply as our standard everywhere — see section 10.
| Purpose | Data used | Basis |
|---|---|---|
| Creating and running your account | Account and profile details | Performance of a contract |
| Showing your timetable, exams and seat placement | Profile, institutional data | Contract; legitimate interests of your institution |
| Scheduling class alarms | Timetable, device preferences | Contract |
| Delivering messages and notifications | Content, push token, preferences | Contract; consent for optional categories |
| Classroom, coursework and submissions | Content, institutional data | Contract |
| Taking payment and keeping a wallet | Financial data | Contract; legal obligation (records) |
| Verifying an account | Identity documents | Explicit consent; substantial public interest in preventing impersonation |
| Providing AI features and metering them | Prompts, audio, usage counters | Contract |
| Security, fraud prevention and abuse investigation | Technical, activity, financial data | Legitimate interests; legal obligation |
| Diagnosing failures and improving the Service | Technical and aggregate usage data | Legitimate interests |
| Responding to support requests | Correspondence, account data | Contract; legitimate interests |
| Complying with law and answering lawful requests | Whatever is required | Legal obligation |
Where we rely on legitimate interests, we have satisfied ourselves that the processing is necessary, proportionate and not overridden by your rights. You can object — see section 11.
5. What we do not do
- We do not sell your personal data. Not to advertisers, not to data brokers, not to anyone.
- We do not build advertising profiles from your coursework, your messages or your movements around campus.
- We do not read your private messages except where we must investigate a specific report of abuse, respond to a lawful request, or restore the service.
- We do not use your content to train AI models. Prompts are sent to a provider to answer that request. Our arrangements require them not to be used for model training.
- We do not give partners your personal data. See section 7.
- We do not gate the in-app record behind payment. Where an institution charges for notification delivery, the in-app copy of a timetable or exam change is still written for every recipient, because withholding a safety-relevant record for non-payment would be indefensible.
6. Who processes data for us
We use the service providers below. Each acts on our instructions under a contract that limits what they may do with the data.
| Provider | What it does | Data involved |
|---|---|---|
| Google (Firebase) | Authentication, database, push messaging | Account, profile, content, technical |
| Railway | Hosts the LEARN API | All data in transit and in processing |
| Hostinger | Database holding uploaded files and images | Files, materials, submissions, identity documents |
| Monime | Payment processing and payouts | Payment amount, reference, chosen mobile money service |
| Expo | Delivers push notifications to devices | Push token, notification content |
| AI/ML API, Google (Gemini), OpenAI | AI responses, transcription, speech | Prompts and audio you submit to an AI feature |
| Clerk | Sign-in for the administration and partner web panels | Staff and partner email addresses |
| Email delivery provider | Sends receipts, notices and account email | Email address, message content |
| Google Drive | Holds files uploaded before storage moved in-house | Older classroom files and materials |
We review this list as providers change. Because it is published here rather than only in our records, you can see who touches your data without having to ask.
7. Who else sees your data
7.1 Your institution
Administrators and teaching staff at your institution can see what their role requires: your enrolment and profile, your classroom membership, coursework you submit to them, and marks. Your institution’s own privacy notice governs what they then do with it.
7.2 Other users
Other people see what the feature is for. A message goes to its recipients. A classroom post goes to the classroom. A profile photograph and display name are visible to people you interact with. Online status and last-seen are visible unless you switch them off in the app’s privacy settings.
7.3 Data partners
We license published timetable data to approved outside platforms under written agreements, per institution. This is academic scheduling data — what is taught, when and where.
It does not include your name, email address, messages, coursework, wallet, identity documents or any other personal record. Where a timetable entry names a member of teaching staff, that name identifies a person against a room and a time, so it is treated as personal data and stripped from every partner response unless a specific permission has been granted, which no partner holds by default.
7.4 Legal and safety
We disclose personal data where we are required to by law, to respond to a valid request from a competent authority, to establish or defend legal claims, or where urgently necessary to prevent serious harm. We disclose the minimum required, and will tell you unless we are prohibited from doing so.
7.5 Business transfer
If LEARN is involved in a merger, acquisition or transfer of assets, personal data may transfer with the service. We will give notice before it happens, and the receiving party will be bound by terms no less protective than these.
8. How long we keep it
| Data | Retention |
|---|---|
| Account and profile | While the account is open, then deleted within 30 days of a deletion request. |
| Identity documents | Deleted within 90 days of a verification decision, or immediately on request. Never kept as a general record. |
| Chat messages | While the account is open. A delivered message may remain in the recipient’s copy of the conversation. |
| Coursework and submissions | Held for the institution, under its academic record-keeping rules, and may outlive your LEARN account. |
| Financial and transaction records | Up to 7 years, to meet accounting and anti-fraud obligations. This survives account deletion. |
| Technical and diagnostic logs | Up to 12 months. |
| Usage counters and allowances | Reset daily; aggregates kept up to 12 months. |
| Support correspondence | Up to 24 months after the matter is closed. |
Where we must keep a financial record after you delete your account, we keep the record and not the person: it is reduced to what the obligation requires and is no longer used to identify you for any other purpose.
9. Where your data goes
LEARN serves Sierra Leone, but the infrastructure behind it is international. Our hosting, database, push delivery, email and AI providers operate servers outside Sierra Leone, principally in the United States and the European Union. Using the Service necessarily involves transferring your data to those countries.
For transfers of data covered by UK or EU data protection law, we rely on the European Commission’s Standard Contractual Clauses or an adequacy decision, together with the technical measures described in Security. A copy of the transfer terms we rely on is available on request.
10. The legal position in Sierra Leone, stated plainly
We would rather say this accurately than sound better than the facts allow.
Sierra Leone has no comprehensive data protection statute in force. The Data Protection and Right to Access Information Bill, 2025 completed national validation in November 2025 and is expected to establish an independent regulator, but it has not yet been enacted. What is in force is the Cyber Security and Crime Act, 2021, which creates offences around the misuse of computer systems and includes provisions on privacy and child online protection. The Constitution of Sierra Leone also protects the privacy of the home and other property.
Why this matters to you
Some apps operating here claim rights for their users under a “Sierra Leone Data Protection Act” that does not exist. We will not do that. Instead, we grant every LEARN user — wherever they are — the full set of rights in section 11 as a matter of contract under these policies. They are enforceable against us on that basis, and we will meet them whether or not a statute yet compels us to.
When the Bill is enacted we will comply with it, register with the regulator it creates if required, and update this policy.
If you are in the United Kingdom or the European Economic Area, the UK GDPR or EU GDPR applies to you directly and nothing in this section limits it.
11. Your rights
You may ask us to:
- Give you a copy of the personal data we hold about you, in a portable, machine-readable format.
- Correct anything inaccurate or incomplete.
- Delete your data — see Account & Data Deletion for how, and for what we must keep.
- Restrict our processing while a dispute about accuracy or legitimacy is resolved.
- Object to processing based on legitimate interests.
- Withdraw consent at any time where consent is the basis — for example, optional notification categories or verification. Withdrawal does not undo processing already carried out lawfully.
- Not be subject to a decision based solely on automated processing that produces a legal or similarly significant effect. We do not make such decisions: verification, account suspension and payout approval are all reviewed by a person.
How to exercise them
Write to privacy@learnumt.app from the email address on your account, or from another address with enough detail for us to identify you safely. We will:
- acknowledge within 7 days;
- respond substantively within 30 days, and tell you if a complex request needs longer, up to a further 60 days;
- not charge you, unless a request is manifestly unfounded or repetitive, in which case we will say so before doing anything; and
- tell you if part of a request must go to your institution, and who to address it to.
We may ask you to confirm your identity before we act. That is a protection for you: handing your data to somebody claiming to be you is the failure a verification step exists to prevent.
Complaints
If you are unhappy with our response, write to legal@learnumt.app and it will be reviewed by someone who did not handle the original request. If you are in the UK or EEA you may also complain to your national supervisory authority. In Sierra Leone, once the regulator contemplated by the 2025 Bill is established, you will be able to complain to it, and we will name it here.
12. Children
LEARN is for university students and staff and is not directed at children under 16. We do not knowingly collect personal data from them. If we learn that we have, we delete it promptly. A parent or guardian who believes a child has given us data should write to privacy@learnumt.app.
13. How we protect it
Data is encrypted in transit. Access to production systems is restricted to people who need it. Passwords are handled by our authentication provider and are never stored by us in readable form. Identity documents and coursework submissions are stored so that no shareable link exists for them and every read re-checks the requester. Balance changes are written inside database transactions so a payment cannot be half-recorded.
No system is perfectly secure. Our full description of what we do, what the in-app lock does and does not protect, and how to report a vulnerability, is on the Security page. If a breach affects you and presents a risk to your rights, we will notify you without undue delay.
14. Changes to this policy
The current version is always at https://legal.learnumt.app/privacy, with its effective date at the top. Where a change materially affects how we use your data we will give at least 14 days’ notice in the app or by email. Where a change requires consent we will ask for it rather than assume it.