Reporting a vulnerability
Email security@learnumt.app. We acknowledge within 3 working days. Test only against your own account, never against another user’s data, and section 4 protects you while you do.
1. How we protect an account
- Encryption in transit. Every connection between the app, the panels and our API uses TLS.
- Passwords are never stored by us in readable form. Authentication is handled by our provider; we hold no copy of your password and cannot tell you what it is.
- Roles are re-checked on the server. A request does not get to act as a lecturer or administrator because the app said so — the server re-reads your record on every request, so a stale or forged claim gets nowhere.
- Sensitive files have no shareable link. Identity documents and coursework submissions are stored so that no public or signed URL is ever issued for them. They can be read only through an endpoint that re-checks who is asking, every time. Revoking access takes effect on the very next request.
- Uploads are checked by their contents, not their label. What a file is comes from its own header bytes rather than the type a browser claimed, so a script cannot be stored as an image and later served as a page.
- Balance changes are transactional. A payment and the record proving it are written together, so a charge cannot be half-applied, and a retried request cannot charge twice.
- No provider keys on your phone. AI requests go through our servers. The app holds no third-party API key, so a compromised handset does not expose a billable credential.
- Least-privilege access. Production access is limited to people who need it for their work.
2. The app lock, and what it does not do
LEARN offers a PIN — with biometric unlock where your phone supports it — that locks the app and is required before a transaction that spends your balance.
Read this before relying on it
The PIN protects this phone, not your account. Somebody who has your email address and password can sign in to LEARN on a different device, and your PIN will not stop them. If you believe your credentials have leaked, change your password — setting a PIN is not a substitute and will not help.
Three further properties are deliberate:
- The PIN never leaves your device. It is held in your phone’s secure keystore as a salted, repeatedly-hashed value. We cannot read it, cannot reset it, and could not disclose it if compelled to.
- A forgotten PIN is answered by signing out and signing in again. There is no recovery, because a recoverable lock is a lock with a second door in it.
- It fails closed. If the keystore cannot be read, the app treats the lock as unavailable rather than deciding no PIN was set. An error opens nothing.
3. What you should do
- Use a password you use nowhere else, and change it if it has ever been exposed.
- Do not share your credentials. Nobody at LEARN will ever ask for your password, your PIN or your mobile money PIN — any message that does is fraudulent, whoever it appears to come from.
- Keep the app updated. Updates carry security fixes.
- Set the app lock if other people handle your phone, understanding the limits above.
- Check that a payment request names the transaction you expected before you confirm it.
- Tell us at support@learnumt.app immediately if you think somebody else has reached your account.
4. Vulnerability disclosure
We welcome reports from security researchers and we will not pursue anybody who follows this policy in good faith.
4.1 Safe harbour
If you comply with section 4.2, we will:
- treat your research as authorised, and not initiate or support legal action against you for it;
- not report you to your institution or to the authorities for the research itself; and
- work with you on timing and on credit.
This protection is ours to give and does not bind third parties. Testing our providers’ systems is out of scope — see section 4.4.
4.2 Rules
- Use only your own account and your own data. If a flaw exposes another person’s data, stop at the point you have proved it and report what you saw — do not enumerate, download or keep it.
- Do not degrade the service. No denial of service, no load testing, no automated scanning that generates significant traffic.
- Do not use social engineering against our staff, our users or our providers, and no physical attacks.
- Do not move money you are not entitled to. Proving a wallet flaw is enough; exploiting it is theft, and this policy does not cover it.
- Give us reasonable time before publishing — see section 4.5.
- Obey the law. Nothing here authorises anything unlawful under the Cyber Security and Crime Act, 2021 or any other applicable law.
4.3 In scope
- The LEARN mobile app for Android and iOS.
- The LEARN API.
- The administration panel, partner developer portal and gate scanner.
- This website.
4.4 Out of scope
- Our providers’ own infrastructure — report those to the provider.
- Your university’s portal or website, which is theirs.
- Findings from automated scanners with no demonstrated impact.
- Missing hardening headers, or a weak TLS cipher, with no working exploit.
- Rate limiting on an endpoint that causes no harm when exceeded.
- Anything requiring physical access to an unlocked device, or an already-compromised device.
- Social engineering, phishing, spam reports.
- Reported behaviour that is documented and intended — for example, that the app lock does not protect the account (section 2), or that a notification’s in-app record is written even when delivery is withheld.
4.5 How to report and what happens next
Email security@learnumt.app with a description, the steps to reproduce, what an attacker could achieve, and anything that helps — a request, a screenshot, a short video. Write in English.
| Stage | Our commitment |
|---|---|
| Acknowledgement | Within 3 working days. |
| Initial assessment | Within 10 working days, with our view of severity. |
| Progress | Updates at least every 14 days while the issue is open. |
| Fix | Critical issues as fast as we can; others on a timeline we will share. |
| Disclosure | Coordinated. Please wait until a fix is released, or 90 days, whichever is sooner. |
We do not currently run a paid bug bounty. We would rather say so than imply a reward that does not exist. We do offer public credit where you want it, and we are glad to confirm your finding in writing for your own record.
5. If something goes wrong
No system is perfectly secure, and a policy that claimed otherwise would not be worth reading.
If a breach affects your personal data and presents a risk to your rights, we will notify you without undue delay, telling you what happened, what data was involved, what we have done and what you should do. Where a regulator must be notified, we will notify it within the period the law requires. We will not delay telling you in order to finish an investigation — an early, incomplete notice is more use to you than a late, complete one.