Implementation
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.
![Happy mother and daughter at tablet. Free range within your age range](https://cdn.prod.website-files.com/6599cfe48b0931a1a32c6e3d/6599dec0b26d4e6c1d56d465_access.webp)
User-Driven Use Cases
Site-Driven Use Cases
Implementing User-Driven Use Case
Trigger – User proactively provides their existing Bandio Age Band to your site by clicking on your logo on the Bandio.com site
Bandio provides an example code with the above functionality.
Implementing Site-Driven Use Cases
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