In case you don't need the full date of birth of the user for any feature to work, the data minimisation principle states that we shouldn't collect a piece of data we don't need.

We display a privacy notice with the privacy informations as per GDPR Right to be informed which covers the transparency requirement. The privacy notice must mention the purpose of collection and processing, the retention period, if the piece of data will be shared with third parties and mention the right to withdraw (if it's a permission - asking for consent). Users have to be informed of this  at the time of collection if they're providing the data for themselves, or within a month if the data has been provided by someone/something else.

Children don't always know their date of birth.  If you do need to collect the child date of birth, make sure you're asking for information in a way that a child could answer, or alternatively, ask their parent directly.

We display a privacy notice with the privacy informations as per GDPR Right to be informed which covers the transparency requirement. The privacy notice must mention the purpose of collection and processing, the retention period, if the piece of data will be shared with third parties and mention the right to withdraw (if it's a permission - asking for consent). Users have to be informed of this  at the time of collection if they're providing the data for themselves, or within a month if the data has been provided by someone/something else.

We keep in mind who our users are an make sure our instructions are clear and our validation requirements are adapted to our users level of understanding.

We clearly state what's expected and from who.

Asking for personal data is a transaction. Therefore we should always  give our users  a compelling reason for them to share their personal data.

We display a privacy notice with the privacy informations as per GDPR Right to be informed which covers the transparency requirement. The privacy notice must mention the purpose of collection and processing, the retention period, if the piece of data will be shared with third parties and mention the right to withdraw (if it's a permission - asking for consent). Users have to be informed of this  at the time of collection if they're providing the data for themselves, or within a month if the data has been provided by someone/something else.

Most children don't know their parent's email address. We've observed that inviting them to ask their parent for help tends to unblock them in the flow. Also, in this example where permissions are required at sign up, parents have to be involved in order to grant said permissions. Involving parents here allow them to be fully aware of what expected from them and why.

Once submitted, the parent email address is being used to create an access to our Parent Portal, so that parents can access and manage their child's permissions at a later date. Parents need to be made aware of how the service works and therefore, must agree with its terms of use.

We clearly state what's expected and from who. Given the next action happens in the parent's mail client, we avoid confusion by not displaying any prominent CTA they could click without reading.

We display a privacy notice with the privacy informations as per GDPR Right to be informed which covers the transparency requirement. The privacy notice must mention the purpose of collection and processing, the retention period, if the piece of data will be shared with third parties and mention the right to withdraw (if it's a permission - asking for consent). Users have to be informed of this  at the time of collection if they're providing the data for themselves, or within a month if the data has been provided by someone/something else.

We clearly display whose permissions are being set and for which app. Consent only makes sense if the context in which it's given is clearly stated.

Children under the age of digital consent aren't likely to understand Terms and Conditions. They can be displayed to parents on that page.

Transparency is a GDPR requirement that also helps with building trust. The more reliable the verification is, the more personal data we have to ask parents, therefore it's important to provide them with contextual information covering why we're doing it, how it's going to work and what we're going to do with their data.

Parents are informed that they can manage the permission they just gave (or didn't give) and they're told how to proceed to do so.