COPPA and GDPR-K, explained for parents (not lawyers)

2 min read

Two laws come up whenever children and apps share a sentence: COPPA and GDPR-K. They’re usually wielded as acronyms and rarely explained, so here’s the plain version: what they are, what they actually require, and the questions they should prompt you to ask any kids’ app. Including ours.

COPPA, the American one

The Children’s Online Privacy Protection Act has a simple heart: an online service aimed at children under thirteen can’t collect a child’s personal information without a parent’s verifiable consent. Not a checkbox a seven-year-old can click; a real parent, really agreeing. Around that core sit supporting rules: collect only what you actually need, tell parents plainly what you have, and let them review it and delete it.

GDPR-K, the European one

GDPR-K isn’t officially its own law; it’s the nickname for the children’s provisions inside Europe’s GDPR. Same spirit: children get special protection, a parent consents on their behalf below a certain age (which varies by country), and families keep real rights over the data: to see it, take it with them, and erase it. Erasure matters extra for children, because a child shouldn’t arrive at adulthood trailing a data file they never agreed to.

The same three demands

Squint at both laws and they converge:

  1. Parents decide, not kids.
  2. Collect as little as possible.
  3. Families can see what’s there, export it, and delete it for good.

How that looks at Lullawick, in the same order

Parents decide: there are no child accounts. The account is yours; you create the profile and provide what the story needs. Your child never signs up, browses, or talks to anyone online. They just hear a story.

Collect little: the story needs surprisingly little, a first name, an age (so chapters come out the right size), and the preferences you choose to share, like themes to weave in. No microphone, no conversations, no location tracking of your child, no behavioral profile. The richest record Lullawick builds is the saga itself, and the saga is about the dragon.

Family rights: you can see what we hold, export the whole saga and take it with you, and delete it permanently. Delete means delete, not hide.

Two honest notes

First: this is not legal advice, and a blog post is not a compliance certificate. These laws are detailed, and the detailed version belongs in a privacy policy written in plain language, which is where ours lives.

Second: the useful takeaway isn’t about us, it’s the checklist. Whatever app your child uses next, ask it three questions: Who consented? What exactly do you collect? How do I delete everything? A good product answers all three quickly and plainly. If the answers are slow, vague, or quietly proud of how much data they gather, that’s your answer too.


The plain-language version of everything above lives in our privacy policy, and the story-safety half has its own explainer. See how it works.

More in AI & Trust

All AI & Trust articles
AI & Trust
Sep 15, 20263 min read
AI & Trust3 min read

What we filter, and what you control: our approach to story safety

AI & Trust
Sep 1, 20263 min read
AI & Trust3 min read

Why a human still steers every story, even with AI writing it

AI & Trust
Aug 4, 20263 min read
AI & Trust3 min read

How an AI actually "remembers" your child's story, explained simply

All articles