What does Canada's new Children's Privacy Code mean for my app?
Written by Brooke Ash, lawyer at For Founders Law.
Short answer
If children use your app, even if they aren't your main audience, the Privacy Commissioner now expects child-friendly privacy by design. Under the Children's Privacy Code released October 20, 2026, a parent or guardian should consent for children under 13, teens 13 to 17 can consent if they understand what they are agreeing to, settings should default to the most private option, location and profiling should be off, and children's data shouldn't be used for targeted advertising. The Code is guidance under PIPEDA, not a new statute, but the Commissioner will use it when assessing complaints.
We can help at a fixed fee: Privacy Policy, from $500. Book a free 15-minute consult
We hear from founders building learning apps, games and family tools who want to launch in Canada and the US. In October 2026 the federal Privacy Commissioner raised the bar for any online service children use. This is general information about Canadian law, not legal advice.
What is the Children’s Privacy Code?
On October 20, 2026 the Office of the Privacy Commissioner of Canada released the Children’s Privacy Code, described as Canada’s first. It sets out how the Commissioner reads PIPEDA, the federal private sector privacy law, when the personal information belongs to someone under 18.
It isn’t a new statute and it doesn’t create fines on its own. But it tells you what the Commissioner will expect if a parent complains or an investigation opens, so it is the practical standard to build to. The Commissioner is taking comments until January 20, 2027 and may update it after that.
Does it apply to my app?
It applies to a business subject to PIPEDA that runs a website, app, platform or digital tool that is either:
- Directed at children. The subject matter, language, characters, design or marketing is aimed at kids or their parents, or children make up a significant part of your users.
- Likely to be accessed by children. There is a reasonable probability children will use it, even if they aren’t your intended audience. Content that appeals to kids, ads aimed at kids, and research about who uses similar services all count.
You can’t avoid the Code by saying your app wasn’t designed for children. If you decide your service isn’t likely to be used by kids, the Code expects you to write down that decision and why.
Who has to consent?
The Code ties consent to a child’s developing capacity:
| Age | Who consents | What the child should get |
|---|---|---|
| Under 13 | A parent or guardian | A simple notice for ages 6 to 9, a written notice for ages 10 to 12 |
| 13 to 17 | The teen, if they can understand what they are agreeing to | Plain-language explanation at the point of collection |
Consent for anything beyond what the core service needs should be opt-in. You shouldn’t treat silence or continued use as consent, and you shouldn’t withhold the core service because a child or parent says no to optional uses. Withdrawing consent should be as easy as giving it.
Quebec has its own rule. Under the Quebec private sector privacy law, a parent or tutor consents for a child under 14, unless the collection is clearly for the child’s benefit. If you have Quebec users, build your consent flow to that age.
What has to be off by default?
- Most private settings. Anything that affects how a child’s information is collected, used, shared or made public should start at the most protective option. A less private default has to be justified and documented.
- Location. Off by default, and no more precise than the feature needs. A regional setting shouldn’t collect exact or real-time location.
- Profiles. Private by default and not indexed by search engines.
- Sharing with third parties. Off by default. A line in your terms of service won’t be enough.
- Profiling. Off by default, and only used where you can show it is in the child’s best interests.
What can’t you do with children’s data?
The Code says businesses shouldn’t use children’s information for targeted or behavioural advertising, shouldn’t infer traits to target them commercially, and shouldn’t share their profile data with others for marketing. It also calls out design tricks: pre-ticked boxes that maximize sharing, countdown timers or social pressure in consent screens, and points, streaks or rewards used to get more data. Consent gathered that way won’t be treated as valid.
Do I need age checks?
Not always. The Code takes a risk-based approach. A low-risk service may rely on simpler measures, while a higher-risk one, such as a social feature with direct messages or location sharing, is expected to have more certainty about users’ ages. That could mean parental confirmation or an age assurance tool that collects as little as possible. If you can’t be confident about age, the Code expects you to apply the child protections to everyone.
How should we explain it to kids?
Write privacy information in plain language for the age and reading level of your users, keep it short, and show it before or when you collect the information. Short videos, icons and layered notices are encouraged for younger children. The Code also expects the information to be available in English and French. Your full privacy policy still needs to be accurate and complete for parents.
The Commissioner strongly encourages a privacy impact assessment before you launch, and again before any significant change, especially for profiling, location or wide sharing.
What if I also have US users?
The US COPPA Rule applies to services directed at children under 13, or that know they are collecting from them. The FTC’s amended rule took effect June 23, 2025, and most businesses had to comply by April 22, 2026. It requires verifiable parental consent, and separate consent before sharing children’s data with third parties such as advertisers. Apple’s Kids category and Google Play’s Families program add their own limits on ads and analytics. If you plan for the Canadian Code, Quebec and COPPA at the same time, you build the consent flow once.
What to do before launch
- Decide honestly whether children will use the app, and write down your reasoning.
- Map every piece of personal information you collect, why, and who receives it.
- Turn off location, profiling and third-party sharing by default.
- Build a parent consent step for under 13 (under 14 for Quebec) and a clear teen notice.
- Remove ad and analytics tools that profile children.
- Write a short child-friendly notice and a full privacy policy in English and French.
- Run a privacy impact assessment and keep it on file.
Sources
- Office of the Privacy Commissioner of Canada: Children's Privacy Code news release (October 20, 2026)
- Office of the Privacy Commissioner of Canada: Children's Privacy Code
- Personal Information Protection and Electronic Documents Act (PIPEDA)
- U.S. Federal Trade Commission: Children's Online Privacy Protection Rule (amended 2025)
- Quebec: Act respecting the protection of personal information in the private sector
Citation copied
How we can help
- Privacy PolicyMatched to what your product actually does with personal information. From $500
- Terms of ServiceFor your website, app or platform. From $500
Fixed fees. Government filing fees are extra.