Bandio is Common Sense Media's privacy-preserving age check process. Simple to implement, it is a low friction way to get a proxy “date of birth” for a user.

It can be used in place of your existing user-reported date of birth. While the Bandio proxy “date of birth” is not the user’s actual date of birth, it is a privacy-preserving alternative that meets compliance requirements. 
Let's talk about how Bandio would work for you!
Happy mother and daughter at tablet. Free range within your age range

Common Use Cases

User-Driven Use Cases

  1. Parents want to proactively make sure that the site has their child’s actual age, not whatever age their child provided on sign up.
  2. User wants to make sure that the site knows their age so the user can take advantage of age-specific experiences and/or benefit from age-appropriate safety features

Site-Driven Use Cases

  1. When a user creates an account on the Site
  2. When a user tries to do something that is age-gated
  3. When a user tries to do something that is age-specific (e.g., “for 13-14 year olds only”)
  4. When a user requests to change their age (e.g, “I mistyped my age…”)
  5. When Site suspects that the user is underage and shouldn’t even have an account
  6. When Site suspects that the user’s reported age is meaningfully higher than their actual age (e.g., reported = 28, suspected = 13)

Steps to Implement

Implementing User-Driven Use Case

Trigger – User proactively provides their existing Bandio Age Band to your site by clicking on your logo on the site

  1. Site creates a page for Bandio users
  2. Site interprets the incoming information from Bandio, which has the user's proxy date of birth (see below) in it
  3. Site calls a Bandio API to verify the age band is genuine and the age band information has not been altered after it was created
  4. Site adds the proxy date of birth as additional information about the user in their profile (If your site doesn’t require logins, then you skip this step)
  5. Site adjusts settings so they are legally and otherwise appropriate for the given age 
  6. Site provides feedback to the user that the age information has been recorded and age-appropriate settings have been set.

Bandio provides an example code with the above functionality.

Implementing Site-Driven Use Cases

  1. On the selected parts of Site, add the Bandio button using a code snippet that we supply.
  2. If the user already has a Bandio age band, the user clicks a button to "Share my age band”. See steps 2-6 above.
  3. If the user does not have a Bandio age band already, then the user clicks “Get child band” or “Get own band” and goes through the flow (<1 minute) to create an age band and share it with the Site. See steps 2-6 above.

Proxy Date of Birth

What is "proxy date of birth"?

This is the most conservative birthdate (DOB) for the given age range provided by the parent or user. So a 13 year old whose mom created a 13 year old age band for her on 5/20/2024 would have a proxy DOB as 5/19/2011.

Why not the user’s actual date of birth? 

Parents and users alike don't want to provide actual dates of birth, so this is a way that preserves user privacy and still gets Sites the information they need for compliance, age appropriate design, and aging up.

Will it always lag the user’s actual age? 

Given it is a proxy DOB and will always be conservative, a user who turns 18 and is especially eager to access 18+ content/features can always pro-actively provide a new Bandio age band. Sites can also choose to prompt a user to get an updated Age Band as appropriate (e.g., when there’s a 50% chance the user has turned 18).

"The best idea I’ve seen so far for obtaining parent-confirmed age and then sharing the age signal is Bandio’s tokenised approach."
—Max Bleyleben, Former Managing Director and Chief Privacy Officer, SuperAwesome

"Implementing Bandio is really straightforward,  super easy… Quite well done.”
— Engineer, Bandio pilot customer

Let's band together
for a Nicer Net.