I'm happy to take that question.
We do have a neutral age-gating function for users. We don't clue them in about what the eligibility age is. We don't indicate to them that providing an age that's either under 13 or over 13 is what they need to do, but I think you're raising a valid point. Age assurance strategies are something that the industry is talking about.
We're talking about things like age detection technology and age verification. Those can be helpful in providing more accuracy about users' ages, but they also have privacy implications. Therefore, there's a broader conversation about the types of age assurance strategies that we can deploy as an industry to increase the likelihood and confidence that we know what age users are when they disclose that to us when they create an account.