A classroom platform cannot function without recording some student activity.
Assignments have to be submitted.
Progress has to be saved.
Teachers need to know who completed the work.
The privacy problem begins when data collected for school starts serving a different business.
Educational use and commercial use are not the same purpose
Digital learning systems can record logins, assignment submissions, quiz results, discussion participation, timestamps, device information, and other activity needed to operate the service.
That can support obvious educational functions: grading, feedback, attendance, troubleshooting, and progress reporting.
In 2023, the Federal Trade Commission obtained an order against education-technology provider Edmodo after alleging that it collected personal information from children and used persistent identifiers for advertising. The FTC said Edmodo improperly relied on schools and teachers for parts of its COPPA compliance while failing to give them the information needed to make those decisions. See the FTC’s Edmodo case page and enforcement announcement.
The useful distinction is not data collection versus no data collection.
It is collection for the educational service versus secondary use for something else.
Learning analytics can become a behavioral record
A single quiz score says little.
A long record can say much more.
Repeated logs may reveal when a student studies, which subjects are difficult, how quickly assignments are completed, which resources are opened, and how participation changes over time.
Those records may be useful to a teacher.
They can also become sensitive if they are retained indefinitely, combined across services, used for advertising, or exposed to people who do not need them for education.
That is why context matters.
A student may reasonably expect a math platform to remember completed math exercises.
That expectation does not automatically extend to building an advertising profile.
Families need the data relationship explained in plain language
A useful disclosure should make several things clear:
- What student activity is recorded?
- Which information is necessary to provide the educational feature?
- Does the school control the account or does the vendor?
- Are third-party services embedded?
- Is data used for advertising, product development, analytics, or other secondary purposes?
- When does the information get deleted after a class, account, or school relationship ends?
For children under 13 in the United States, COPPA adds specific legal requirements for covered services. Other student-privacy rules can also apply depending on the institution and jurisdiction.
But even before the law enters the room, the architectural question is simple.
The student entered the system to learn.
If the data later serves another purpose, that second purpose should not be smuggled inside the word education.