Children's Privacy in Canada: OPC Code and Age Assurance
Children's privacy is now governed by a dedicated OPC Children's Privacy Code that interprets PIPEDA for online services directed at or likely to be accessed by children under 18. It calls for parental consent under 13, high-privacy defaults, no behavioural advertising, limits on deceptive design and risk-based age assurance, alongside Quebec's statutory under-14 rule.

Key takeaways
- The OPC Children's Privacy Code applies to services directed at or likely to be accessed by children under 18.
- Parental consent is expected for children under 13 in all but exceptional circumstances.
- Location collection and public profiles should be off by default.
- Targeted and behavioural advertising to children should not be used.
- Age assurance must be risk-based and proportionate, not a default condition of access.
- Quebec requires parental consent to collect information from children under 14.
Children's privacy in Canada: where the law stands
Children's privacy has moved from a niche topic to a central compliance issue for any business with a website, app, game or platform that young people use. Canada still has no stand-alone federal children's privacy statute. Instead, the Office of the Privacy Commissioner of Canada (OPC) has interpreted the Personal Information Protection and Electronic Documents Act (PIPEDA) through a dedicated Children's Privacy Code, published in 2026, and has issued separate guidance on age assurance. Quebec adds statutory rules on parental consent for children under 14 and privacy-protective default settings.

This insight summarizes the Code's scope and expectations, the OPC's approach to age assurance, Quebec's rules and the practical design obligations that follow for apps, games and online services. It is general information, not legal advice.
The legal foundation: PIPEDA and the best interests of the child
PIPEDA does not expressly distinguish between children and adults. The OPC's long-standing position, restated in the Code, is that children's personal information warrants heightened protection and that PIPEDA's obligations should be interpreted with that sensitivity in mind. The Code relies on the Supreme Court of Canada's recognition of children's inherent vulnerability in A.B. v. Bragg Communications Inc. (2012) and on R. v. Jarvis, as well as on Canada's obligations under the United Nations Convention on the Rights of the Child, including the best interests principle and the recognition of evolving capacity.
The Code also draws on a 2023 resolution of federal, provincial and territorial privacy regulators calling on organizations to put the best interests of young people at the forefront of the design and delivery of digital services. In practice, the Code is the OPC's view of what PIPEDA already requires. It is not a regulation, but it signals how the OPC will assess complaints and investigations involving children's privacy.
Who the Children's Privacy Code covers
The Code protects all children under 18 and applies to organizations subject to PIPEDA that collect, use or disclose personal information in a commercial activity involving an online service (websites, applications, platforms and digital tools) that is either directed at children or likely to be accessed by children. The second limb is the important one: an organization cannot avoid the Code's expectations simply because its service was not designed for children if children use it in practice.
The OPC lists indicators for each category. A service is likely directed at children if its subject matter is primarily of interest to children, it uses child-directed language, imagery or characters, it is marketed through channels targeting children or parents, or children make up a significant portion of its users. A service is likely to be accessed by children where research about its user base, child-directed advertising placed on it, content or features that appeal to children, or child use of similar services point that way. If an organization concludes that children are not likely to access its service, the Code expects it to document that decision and its reasons.
Key expectations for children's privacy
| Expectation | What the OPC expects |
|---|---|
| Consent | Meaningful consent calibrated to evolving capacity; express, opt-in consent with separate choices for non-essential uses; withdrawal at any time |
| Under 13 | Parental or guardian consent in all but exceptional circumstances |
| Ages 13 to 17 | Assess whether the child has capacity to understand the specific practice, particularly for sensitive information |
| Privacy impact assessments | Encouraged, especially for higher-risk products and services |
| Default settings | Highest available privacy setting by default; location collection and public profile visibility off by default |
| Data minimization | Collect only what is directly necessary; do not retain longer than needed |
| Transparency | Clear, accessible and age-appropriate privacy information |
| Correction and deletion | Practical means for children to correct and delete their information |
| Profiling | Avoid profiling children; no targeted or behavioural advertising to children |
Consent and evolving capacity
The Code accepts that consent mechanisms designed for adults will generally not meet PIPEDA's meaningful consent standard when applied to children. Privacy information written in complex language, or in formats that assume adult comprehension, cannot support valid consent from a child. Organizations must calibrate their approach to the age and developmental stage of the children who use the service.
For children under 13, organizations must obtain consent from a parent or guardian in all but exceptional circumstances, and should inform the child through an age-appropriate notice. Exceptions must be narrow and demonstrably in the child's best interests, such as a child's own request to delete information. For children aged 13 to 17, organizations should assess whether the child has sufficient capacity to understand what they are consenting to in the context of the particular practice. Non-essential data uses should require express opt-in consent, with a separate choice for each optional feature, and children and parents should be able to withdraw consent at any time.
Default settings, location data and minimization
The OPC treats privacy-protective defaults as one of the most effective safeguards, because most children never change the settings they start with. Services covered by the Code should be set to the highest available privacy setting by default, and both the collection of location data and the public visibility of profiles should be off by default. Location may only be enabled where it is directly necessary for the core service and this is obvious to the user, and the precision collected should be no greater than the function requires.
Data minimization applies at every stage of the child's interaction with the service. Organizations should collect only what is demonstrably necessary, set retention periods, and plan for what happens to a child's information when the child stops using the service or reaches adulthood, including the ability to request deletion of information collected during childhood.
A common gap is the general-audience service that never considered children at all. Under the Code, the first step is an honest, documented assessment of whether children are likely to access the service. If they are, default settings, consent flows and advertising practices all need to be revisited.
Profiling and behavioural advertising
The Code states that organizations should avoid profiling children for marketing purposes. They should not use children's personal information to deliver targeted or behavioural advertising to them, infer characteristics from children's digital activity to target them commercially, or share children's profile data with third parties for advertising or marketing. Where profiling informs automated decisions about children, the best interests of the child should be the primary consideration. The Code gives specific attention to recommender systems and other AI services, which can collect data pervasively and influence children's thoughts, feelings and behaviour.
Prohibited practices and deceptive design
The Code identifies practices that the OPC considers inappropriate under subsection 5(3) of PIPEDA, the provision that limits collection, use and disclosure to purposes a reasonable person would consider appropriate, whether or not consent was obtained. These include:
- manipulative interface design, such as pre-selected options that default to maximum data sharing and misleading labels;
- manipulative consent processes using artificial urgency, threat of loss or social pressure;
- engagement techniques such as points, streaks or rewards used to expand data collection and profiling;
- inferring sensitive characteristics a child has not disclosed, such as health, sexual orientation or family circumstances;
- using indicators of younger age or lower maturity to intensify data collection; and
- emotional analytics used to exploit a child's vulnerabilities.
Consent obtained through manipulative interfaces or consent processes is not considered valid under the Code. For design teams, this makes privacy for young users a product requirement, not only a legal review at launch.
Age assurance: risk-based and proportionate
Many of these obligations depend on knowing, with some confidence, whether a user is a child. The OPC's guidance on assessing whether and how to use age assurance, aimed at websites and online services, and a companion document for developers of age assurance systems, take a cautious approach. Age assurance should not be the default condition for accessing the Internet. It should be one of several tools, used in a risk-based way proportionate to the potential harm being addressed.
The guidance asks organizations first to determine whether their service is likely to be accessed by children and poses potential harm, then to consider alternatives that address the harm without age assurance. Turning off behavioural advertising for all users, for example, may be preferable to verifying every user's age. If age assurance is needed, the method should not require more, or more sensitive, personal information than necessary, and its application can often be limited to specific age-restricted content or features. The Children's Privacy Code adds that where sufficient certainty about age cannot be achieved, protections should apply to all users by default.
Quebec: consent under 14 and privacy by default
Quebec's private-sector privacy law, as amended by Law 25, contains statutory rules that go further than PIPEDA. According to the Commission d'accès à l'information, personal information concerning a minor under 14 may not be collected from that minor without the consent of the person having parental authority or the tutor, unless the collection is clearly for the minor's benefit. Organizations offering technological products or services to the public must also ensure that, by default, privacy settings provide the highest level of confidentiality without any action by the individual; this rule does not apply to cookie settings. The OPC's Code cites these provisions as evidence of the direction of provincial law.
For national services, the practical effect is a two-tier consent model: parental consent under 13 for PIPEDA purposes under the Code, and under 14 for Quebec users under statute. Many organizations choose to apply the stricter threshold across Canada to avoid maintaining separate flows.
Design obligations for apps and games
Games, educational technology, social and messaging apps and connected toys are where these obligations bite hardest. A practical design checklist includes:
- Assess and document whether the service is directed at or likely to be accessed by children.
- Map the personal information collected, including device identifiers, voice, images and location.
- Set high-privacy defaults, with location and public profiles off.
- Build age-appropriate consent and notice flows, with parental consent for younger users.
- Remove behavioural advertising and third-party advertising trackers from child experiences.
- Review engagement mechanics, such as streaks and rewards, for data-driven manipulation.
- Provide simple tools for children to correct and delete their information.
- Conduct a privacy impact assessment for higher-risk features such as chat, location sharing or AI companions.
Parental controls and guided autonomy
The Code does not treat parental control as a complete answer. Parental tools should be age-appropriate and respect the child's evolving capacity and best interests. Where a parent monitors a child's activity or adjusts settings, the child should be told in plain language they can understand. Services should not be designed so that full participation or privacy protection depends on adult oversight, because not every child has a parent or guardian available to help. For older teenagers, the Code expects greater autonomy, with organizations supporting their ability to make their own privacy choices.
Enforcement outlook
The OPC enforces PIPEDA through complaints, investigations and compliance agreements, and it has signalled that protecting young people's information is a strategic priority. Investigations involving platforms popular with young people, and joint work with provincial regulators, are likely to apply the Code's expectations. In Quebec, the Commission d'accès à l'information can impose administrative monetary penalties under Law 25. Federal privacy reform could also introduce express provisions on minors' information; see our insight on federal privacy reform. Related rules on harmful content are covered in our insight on online safety legislation.
A compliance roadmap for children's privacy
For most organizations, compliance starts with governance: assign responsibility for children's privacy, inventory services that children may use and record the assessment. Next, prioritize high-risk features and data flows, especially location, messaging, advertising technology and AI-driven recommendations. Then update consent flows, notices and defaults, and test them with real users of the relevant age where possible. Finally, review vendor contracts, including software development kits and advertising partners, to make sure third parties are not collecting children's data in ways the organization would not permit itself. See our privacy and data protection page.
How TRW & Co helps
We help app developers, game studios, edtech providers and consumer platforms meet Canadian children's privacy expectations. Our work includes child-access assessments under the OPC Code, privacy impact assessments, consent and age assurance design, Quebec under-14 compliance, advertising technology reviews and responses to regulator inquiries. See our technology, privacy and AI practice or contact us.
Frequently asked questions
Is the Children's Privacy Code binding?
The Code is OPC guidance rather than a regulation, but it sets out the OPC's interpretation of what PIPEDA already requires for children's personal information. The OPC is likely to apply it in complaints and investigations.
Does the Code apply to general-audience services?
Yes, if the service is likely to be accessed by children in practice. An organization that concludes children are unlikely to access its service should document that assessment and its reasons.
At what age is parental consent required?
Under the OPC Code, parental or guardian consent is expected for children under 13 in all but exceptional circumstances. In Quebec, the private-sector law requires the consent of the person with parental authority to collect information from a minor under 14, unless collection is clearly for the minor's benefit.
Do we have to verify every user's age?
No. OPC guidance says age assurance should be risk-based and proportionate and should not be the default condition for accessing online services. Alternatives, such as turning off risky features for everyone, should be considered first.
Can we show targeted ads to teenagers?
The Code states that organizations should not use children's personal information, including that of teenagers under 18, to deliver targeted or behavioural advertising to them or share their profile data with third parties for marketing.
Sources
General information only, not legal advice. References to statutes, courts and authorities describe published law and practice at the date shown.


