Your LMS Holds Personal Data. That Makes You a Data Controller.
Under Kenya's Data Protection Act, 2019, that makes your institution a data controller with real obligations, whether or not you have thought of your LMS choice in those terms.
Every learner enrolled on an LMS has personal data sitting inside it. Names, contact details, academic records and, in many cases, payment history.
Four categories of learner data
If your platform holds any of these, the question is not whether you are a data controller. It is whether you can answer the questions that follow.
Why this matters more than it used to
The Office of the Data Protection Commissioner (ODPC) has been steadily increasing enforcement since the Act came into force. Institutions, not just software vendors, carry responsibility for how student data is collected, stored and shared.
Choosing an LMS without asking where that data actually lives is a compliance gap waiting to surface, usually at the worst possible time.
An enforcement notice or an audit request rarely arrives in a quiet week. It usually lands during exams, admissions or a funding review, when nobody has time to reconstruct what your data handling actually looks like.
Questions worth asking any LMS provider
- Question 1 Where is our data physically hosted, and does that location create any cross border transfer concerns?
- Question 2 Who has access to student records, and under what agreement?
- Question 3 How often is data backed up, and where are backups stored?
- Question 4 What happens to our data if we switch providers? Can we export it cleanly?
- Question 5 Is there a data processing agreement we can review before signing anything?
This is not a hypothetical concern
Across East Africa, the pressure is rising from several directions at once.
- Pressure point Government agencies tightening data expectations
- Pressure point Examination bodies asking stricter questions
- Pressure point Accreditation boards requiring evidence
Institutions that can answer these questions confidently are the ones that avoid scrambling when asked. Institutions that cannot tend to discover the gap in the middle of an audit, not before it.
Generic platform defaults versus a local setup
One default answer for everyone
- Data hosted wherever the vendor chooses
- Access governed by their internal policy
- Export format decided by their roadmap
- Data processing agreement may be non negotiable
- Cross border transfer is often unavoidable
Answers you can actually give
- Data hosted where you choose
- Access governed by your own permissions
- Full export of courses, grades and users
- A data processing agreement you can review
- Cross border transfer avoided where needed
What compliance looks like in practice
- A documented record of where learner data is physically stored
- Role based access so only the right staff can see learner records
- A named person responsible for data protection questions
- Backups stored in a known location with a tested restore process
- A clean export route if the institution ever changes providers
- A signed data processing agreement before the first learner logs in
Your LMS already holds personal data. The only question that matters now is whether you can answer the five provider questions clearly and in writing.
If you can, you are in a strong position. If you cannot, that is the work to do before the next intake, not after.
Want a setup you can answer questions about?
Stonehenge Digital KE hosts Moodle on your own domain, in a known location, with full export access and role based permissions under your control.
Explore the Moodle LMS Hosting Service →Interested in Moodle LMS Hosting?
Let's build this for your business
Fully hosted Moodle LMS on your own custom domain — built for Kenyan and East African schools, colleges, TVETs, and training providers.