By · Last updated 2026-03-16

Back to BlogLegal Tech

COPPA April 2026: What EdTech Platforms Must Do Before the Deadline

COPPA updated rule takes effect April 22, 2026. Reddit was fined £14.47M for children's data failures. EdTech platforms face the same risk.

March 16, 20266 minute read
COPPAFERPAchildren data privacyEdTech compliancestudent data2026 deadline

The April 22 Deadline

Updated for 2026

The FTC updated COPPA. The new rule takes effect on April 22, 2026. This is the first major change since 2013. EdTech platforms serving children under 13 must act now. Weeks remain, not months.

The changes are deep. Platforms built on the 2013 rules must audit and update core systems. Small fixes will not be enough.

Reddit's Fine: A Clear Warning

In March 2026, the UK's ICO fined Reddit £14.47 million. Why? Reddit failed to keep children away from harmful content. Age checks were weak. Minors got through.

That fine was under UK GDPR, not COPPA. But the failure is the same kind. COPPA 2026 targets platforms that know minors are present but do not protect them.

EdTech is in a harder spot. These platforms know who their users are. They sell to schools. They market to parents. They see student email addresses. The "we didn't know" defense is not available.

What COPPA 2026 Changed

The FTC update added five key rules for EdTech platforms.

1. Minimization Is Now Required

Collect only what the service truly needs. The 2013 rule let platforms collect a lot with parental consent. The 2026 rule bans extra collection even with consent. Device IDs, tracking signals, and location info not needed for the service must stop now.

2. No Targeted Ads to Minors

EdTech platforms cannot use children's records for behavioral ads. Consent does not change this. Some platforms used blanket consent to justify broad data use. That loophole is now closed.

3. Separate Consent for AI Features

Any AI feature that uses children's input needs its own consent form. AI tutors, writing tools, and adaptive engines all count. Consent for the main service does not cover AI add-ons.

4. Deletion Rules with Real Teeth

Delete children's records when they are no longer needed. Platforms that run automated deletion on a set schedule face lower liability in FTC actions. This is a real safe harbor — use it.

5. Higher De-identification Bar

Removing a name is not enough. Platforms must show that re-identification is not reasonably possible. For aggregate analytics, this means k-anonymity or differential privacy.

FERPA and COPPA: Both Apply

For K-12 platforms working with schools, FERPA runs alongside COPPA. Here is what matters:

  • FERPA lets schools share student records with vendors — but only for contracted services
  • COPPA still applies for children under 13, even when FERPA allows the sharing
  • School consent under FERPA does not replace COPPA parental consent

FERPA compliance is not COPPA compliance. Both must be met separately.

What to Do Before April 22

Work through this checklist before the deadline.

Inventory

  • List all records collected from users under 13
  • Find every third-party tool that receives children's records — analytics, CRM, monitoring
  • Check consent for each collection type

Anonymization

  • Add PII detection to student content before it is logged
  • Strip names, email addresses, and student IDs from analytics events
  • De-identify aggregate reports used for product work
  • Clean AI training sets that include student input

Consent

  • Build separate consent flows for each AI feature
  • Log consent with timestamps
  • Add a withdrawal flow that triggers deletion right away

Retention

  • Set a retention period for each record type
  • Automate deletion when periods end
  • Check backup systems for gaps

Vendors

  • Review agreements with all sub-processors
  • Confirm that analytics vendors do not use children's records for ads
  • Update agreements to match the 2026 de-identification standard

How Anonymization Helps

The new de-identification rule is the most technical part of COPPA 2026. Stripping names alone does not meet the standard. You need a system that finds and removes all PII across every data flow.

anonym.legal detects 285+ entity types across 48 languages. Many EdTech platforms serve students who speak many languages. Student PII appears in Spanish, Mandarin, Arabic, and dozens of others — not just English. Wide language coverage is not a nice-to-have here. It is a compliance need.

The platform also catches edge cases that manual review misses. Phone numbers, student ID patterns, and indirect identifiers are common in student content. Automated detection finds these at scale. Manual review does not.

The batch processing feature lets teams run existing databases through the tool. That covers old student content that now must meet the higher standard. Retroactive de-identification is part of the compliance picture under the 2026 rule.

See our security and compliance overview for how we handle sensitive records. The legal compliance page covers both FERPA and COPPA in detail.

The Cost of Inaction

COPPA fines run up to $51,744 per violation per day. For a platform with 100,000 student accounts, a systemic gap in de-identification could mean tens of millions in fines.

Reddit's fine was £14.47 million. Reddit has billions in revenue. For a mid-sized EdTech platform, that scale of fine would be company-ending.

April 22 is close. The work is doable if it starts now. Regulators have made clear they will enforce the new rule. Waiting is not a strategy.

Start anonymizing student records today →


Sources

  • FTC COPPA Rule Update, Federal Register, 2025 (effective April 22, 2026)
  • ICO Reddit enforcement notice, March 2026 — £14.47M penalty
  • FERPA, 20 U.S.C. § 1232g, and implementing regulations 34 CFR Part 99
  • FTC COPPA FAQ: AI-powered features and parental consent, 2026

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.