Website

A Parental Consent Checkbox Is No Longer Enough: Indonesia's Child Data Rules for Apps

November 13, 2026 · 5 min read · Etzal Group Team

From 16 January 2027, data controllers in Indonesia must take steps to identify child users and verify that consent to process their data truly comes from a parent or guardian. The duty sits in Article 38 of Government Regulation 33 of 2026 (PP 33/2026), according to a Katadata report of 3 September 2026, and it applies to anyone processing children's personal data: apps, education portals, clinics and loyalty programmes alike.

Katadata reports that PP 33/2026, which implements the Personal Data Protection Law, was signed by President Prabowo Subianto on 16 July 2026. The effective date falls before the next school year and enrolment season, so next year's forms need to be ready.

A note on sources: the article numbers here come from Katadata's reporting, not from an official copy of the regulation that we have read.

What the regulation asks for

According to Katadata, Article 38 sets three steps in sequence:

  1. The controller must take steps to identify children.
  2. Once a child is identified, processing their data requires the consent of a parent and/or guardian.
  3. The controller must verify that consent, taking available technology into account.

The same report spells out the practical consequence. A consent button, or a user's statement that parental permission has been obtained, is not enough. The controller is responsible for making sure the consent truly comes from a parent or guardian.

Three related duties apply:

  • The controller must provide a transition procedure for processing when a child reaches the age or criteria at which they are no longer classed as a child.
  • Article 34 requires a mechanism for obtaining consent, electronic or otherwise.
  • Article 36 requires the controller to hold proof of the consent given.

Two things the sources do not answer

The age limit. The sources we read do not state up to what age a person is a child under PP 33/2026. Do not fill the gap with a number from another rule. Katadata wrote on 13 November 2026 that Government Regulation 17 of 2025, known as PP TUNAS, governs the operation of electronic systems for child protection and is aimed at strengthening protection of children under 16. That is a different regulation with a different purpose. Its figure of 16 must not be read as the definition of a child in PP 33/2026. Check the official text.

The verification method. The sources name no mandatory method. The wording is "taking available technology into account". The choice therefore rests with the controller, and so does the burden of explaining why the choice is adequate.

Do you process children's data

Many companies answer "no" too quickly. The screening table below is our suggestion for thinking about children's data Indonesia now regulates more tightly.

BusinessWhere children's data appears
Apps and gamesAccounts created by children themselves
Education portals, tutoring, schoolsStudent data, grades, attendance, photos
Clinics and health servicesChild patient records, registration by a companion
Loyalty programmes and retailChild member cards, birthday data, kids' clubs
Events, attractions, coursesParticipant registration forms
Any employerDependants' data for employee benefits

If your service is aimed at the general public and never asks for age, you do not yet know the answer. The first duty in Article 38 is precisely that: take steps to identify.

Identifying without over-collecting

The first trade-off appears here. Identifying children needs age data, and asking every user for an identity document piles up new sensitive data. We suggest starting light:

  • ask for date of birth or an age range at sign-up, with an explanation of why
  • for services clearly aimed at children, treat every user as a child until shown otherwise
  • for adult services, decide what happens when there are signs that a user is a child

Record the approach chosen and the reasoning.

Verifying parental consent

No method is mandated according to the sources, so the list below is a set of options, not rules. Our principle: the more sensitive the data, the stronger the verification.

  • Confirmation through the parent's contact. A link or code is sent to the parent's email or number. Light and cheap, but a child can enter their own contact. Suited to low-risk data.
  • Consent from a verified parent account. The parent has their own account and links the child's. Stronger, and needs development.
  • A signature in person. Schools, clinics and course providers already meet parents at enrolment. A paper form signed on site and then scanned is often both the strongest and the simplest route.
  • Document check or video call. Strongest, most expensive, and adds sensitive data you must protect. Keep it for high-risk data.

Whatever you choose, Article 36 asks for proof. Keep who consented, for which child, when, by what method and for what purpose.

When the child grows up

The transition duty is easily forgotten because its effect is felt years later. Our design suggestion:

  1. Store the date of birth or an expected transition date on the child's record.
  2. Ahead of that date, notify the individual and the parent.
  3. Ask for fresh consent from the individual for any processing that relies on consent.
  4. Hand over control of the account, including removing parental access where needed.
  5. If there is no response, define what happens: frozen, restricted or deleted under the retention policy.

School portals and paediatric clinics will feel this need first.

What to do this week

  1. List every form and sign-up screen that may be completed by or for a child.
  2. Flag those that still rely on a checkbox or a user statement.
  3. Choose a verification method per risk level and write down why.
  4. Check whether your systems store proof of consent that can be produced later.
  5. Ask legal counsel to confirm the age limit from the official text.

These changes touch the sign-up flow, the data model and evidence storage. If your app or portal needs rework for this, our enterprise software team can help design it.

This article is not legal advice. Confirm the obligations for your service with legal counsel and the official text of PP 33/2026.

Sources

Frequently asked questions

Is a parental consent checkbox still enough in Indonesia?

According to Katadata's report on Article 38 of PP 33/2026, a consent button or a user's statement that parental permission was obtained is not enough. The controller must make sure the consent truly comes from a parent or guardian.

Which verification method is required?

The sources we read do not name a specific method. The controller must verify taking available technology into account, so choose a method proportionate to the risk and record why.

Up to what age is someone a child under PP 33/2026?

The age limit is not stated in the sources we read. Check the official text and ask legal counsel.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Website Development

Fast, SEO-ready websites that turn visitors into customers.