Industry Guides

Student Data Privacy in an LMS: What to Ask Before You Build

The questions to settle before an LMS holds real student records: which laws may apply, what to collect, who can see it, how long it stays, where it is hosted and what every vendor does with it.

Student Data Privacy in an LMS: What to Ask Before You Build

Student data privacy is easier to design in than to add afterwards. Once an LMS is live, every extra profile field, plugin and report already holds records about real students, and taking them out means migrations and awkward emails to parents. The cheap moment to decide what you collect, who sees it and how long it stays is before the build starts.

This is a set of questions to work through with your project team and, for anything legal, with your own counsel. We build learning platforms and we are not lawyers. Nothing here is legal advice, and no checklist, plugin or hosting plan makes a system meet a law by being in place.

Three laws that may apply, depending on where you operate

Which rules reach you depends on where you operate, where your students live, how old they are and how your institution is funded. Three laws come up most often in LMS projects. The table says what each is broadly concerned with, not what it requires of you.

LawWhere it comes fromWhat it is generally concerned with
FERPAUnited States, federalEducation records at schools that receive US Department of Education funding. It gives parents the right to see those records, to ask for corrections and to have some control over disclosure of personally identifiable information from them. The rights pass to the student at 18 or on entering a postsecondary institution.
COPPAUnited States, federal, enforced by the FTCOnline services directed to children under 13, or that knowingly collect personal information from them. It centers on notice and parental consent. FTC guidance describes when a school may consent on behalf of parents, limited to educational use with no other commercial purpose.
GDPREuropean UnionPersonal data of people in the EU, including when the organization is based elsewhere and offers them services. It sets principles such as collecting only what is needed and limiting how long it is kept. The age below which a child needs parental consent for online services is set by each member state, between 13 and 16.

Many US states have their own student privacy laws, and countries outside the EU have their own data protection acts. Which of them reach your institution is a question for counsel. For background, read the US Department of Education's explanation of FERPA and the European Commission's overview of data protection. The FTC publishes detailed COPPA guidance with a section for schools.

Student data privacy starts with a map of the data

Before requirements are written, make a spreadsheet with one row per kind of data and five columns: what it is, why you need it, where it comes from, who uses it and where it goes next. An LMS usually holds more than people expect:

  • Identity: name, email, student ID, date of birth, photo, parent contacts.
  • Academic records: enrollments, grades, submissions, quiz attempts, teacher feedback, certificates.
  • Behavior: login times, pages viewed, time spent, IP addresses, device details.
  • Communication: private messages, forum posts, comments on work.
  • Media: recordings of live classes, uploaded video and audio of students.
  • Support notes: accommodations, learning plans or anything a teacher types into a free-text field.

Rows with nothing in the "why" column are the first candidates to drop.

Collect less than the platform offers

Every LMS ships with more fields and logs than a school needs. Trim them at setup.

  • Remove optional profile fields such as phone, address and social accounts unless a named process uses them.
  • If you only need to know a student's year group, store the year group and leave out the date of birth.
  • Keep government ID numbers out of the LMS. The student information system holds them, and the LMS needs only its own ID.
  • Be wary of free-text "notes" fields on a profile. They fill up with sensitive remarks nobody planned to store.
  • Create accounts from the school's records, not through open self-registration, when students are young. Moodle has a "digital age of consent" check for self-registration under its privacy settings if you do allow sign-ups.
  • Do not record live classes by default. Record when there is a reason, and say so at the start.

Decide who can see what, role by role

Write the access rules as sentences before anyone configures roles: "A teacher sees grades for students in their own classes." "A counselor sees progress for their caseload and no private messages." "A parent sees their own child's grades and due dates." Then test each sentence with a real test account.

The places this usually goes wrong:

  • Too many administrators. Site administrators see everything. Keep the list to a few named people and review it every term.
  • Impersonation. Features such as Moodle's "Log in as" are useful for support and should be limited to those who need them.
  • Exports. A gradebook downloaded to a laptop has left every control you built. Decide which roles can export, and to where.
  • Vendor and developer access. Give outside support its own named accounts, on staging with anonymized data wherever possible, and remove them when the work ends.

On a WordPress LMS the same thinking applies to roles and capabilities, which we cover in WordPress user roles and least privilege.

Set retention and deletion rules before launch

Ask what happens to a student's data when they finish a course, leave the school or ask for a copy or for deletion. The answer has to cover four places.

Course data. Decide how long old courses stay online with student work in them, and who archives or resets them each year.

Logs. Activity logs grow without limit unless told otherwise. Moodle's standard log store has a "Keep logs for" setting, and other platforms need a scheduled cleanup job.

Individual requests. Moodle includes tools for this under Site administration > Users > Privacy and policies: a data registry where you set purposes and retention periods, and a queue for export and deletion requests. The Moodle data privacy documentation explains how they fit together. WordPress has Tools > Export Personal Data and Tools > Erase Personal Data. Check that your LMS and form plugins register their data with those tools, and test with a dummy student.

Backups. Deleting a record does not remove it from last month's backup. Set a backup retention period short enough that deleted data ages out, and write that period down.

Put every vendor and plugin through the same checks

Video hosting, live class tools, plagiarism checking, proctoring, email delivery, analytics and AI features all receive student data. Ask each one the following, and keep the answers in the same spreadsheet as your data map:

  1. Which student data do you receive, and can we send less?
  2. Where is it stored, and in which country are your support staff who can access it?
  3. Which other companies process it for you?
  4. Do you use it for advertising, profiling or training models?
  5. Will you sign the data agreement our counsel requires?
  6. How do we get our data out, and how is it deleted when the contract ends?
  7. How and when would you tell us about a breach?

Plugins deserve the same scrutiny. Moodle's plugin privacy registry lists what each installed plugin declares that it stores. Keep advertising pixels and marketing analytics off logged-in pages entirely.

Choose the hosting region on purpose

Where the server sits can matter legally, because some laws restrict moving personal data to other countries. Choose the region with counsel. Backups, the email service, the video host and the CDN each have a location too. Then do the plain security work: HTTPS everywhere, two-factor sign-in for staff with wide access, encrypted backups, prompt updates, and staging copies that do not contain real student records.

What to bring to a builder and what to bring to counsel

Counsel decides which laws apply, what notices and consents are needed and which agreements vendors must sign. A development team turns those decisions into a system: trimmed fields, tested roles, retention jobs, export and deletion flows, a hosting region and a short, documented vendor list. Involve both early, because a consent screen or a retention rule added a month before launch always costs more. If you want a team that has built these controls into Moodle and WordPress platforms, see our work for education and eLearning providers or our Moodle development service.

Frequently asked questions

Does FERPA apply to our LMS?

It may, if you are a US school that receives federal education funding and the LMS holds education records. Whether a particular system or record falls under it is a legal question for your counsel. From a build point of view, plan as if grades, submissions and feedback are protected records with limited access.

Can students under 13 use an LMS?

Many schools run one for young students. Rules about children's data, such as COPPA in the United States and the GDPR's provisions on children, may affect how accounts are created and what consent is needed. Have the school create the accounts, keep outside tools to a minimum and confirm the approach with counsel.

Is a self-hosted LMS better for privacy than a hosted one?

Self-hosting gives you control over location, plugins, logs and retention, and makes patching and monitoring your job. A hosted service takes on that work, and you depend on its contract and settings.

How long should student records stay in the LMS?

There is no universal period. It follows your institution's records policy and the laws that apply to you. In most schools the transcript lives in the student information system, so the LMS can keep detailed activity data for a much shorter time.

Add WorldWin Coder to your preferred sources

Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

Swati Priyadrshni
· Founder & CEO at WorldWin Coder

I'm Swati Priyadarshani, Founder & CEO of LMS Advisor and Co-Founder of WorldWin Coder Pvt. Ltd. (est. 2019). Over the last 10+ years, I've helped enterprises build learning platforms that actually get used - not just deployed.

Keep reading

Have something to build, fix or move?

Tell us where you are. A developer reads every inquiry, and you get next steps and a free quote within one business day.