IsEligibleForAgeFeatures behavior in Brazil

Question

Created 6d

Replies 5

Boosts 1

Participants 4

From the Feb 24 news, I understand that for all Apple users in Brazil with iOS26.2 and newer, isEligibleForAgeFeatures will eventually return true. Brazil is a "nonregulated region", and developers will need to handle all three situations of ask first/always share/never share.

Please correct me if I'm wrong above. A few questions follow on the eligibility check:

What's the return value of IsEligibleForAgeFeatures for a Brazilian user who has NOT touched the age range feature at all, thus hasn't picked one of the three options?
How can we test these cases? From the updated sandbox doc, there's more information on declined/approved, will those the same behaviors as a future Brazilian user? The doc used to say Texas, now it doesn't say any region.
On which date will Apple START to return true for IsEligibleForAgeFeatures for Brazilian users? I cannot find the exact date anywhere.
Will ALL of Brazil return true overnight, or is there some ramp up that developers need to be aware of?

Thanks a lot for sharing the guidance, and thanks in advance for more guidance to come!

Boost

Answer 1

DTS Engineer OP

Apple

5d

Thank you for your post and your patience. There are many other developers here with more extensive knowledge of this subject. Please review the two resources we have published regarding your questions, as well as the FAQ. If your questions are not addressed there, please let me know, and I will ensure that someone takes over to address them and add them to the FAQ.

https://developer.apple.com/kids/

https://developer.apple.com/support/age-assurance

Albert Pascual   Worldwide Developer Relations.

0

Answer 2

jarrodlombardo-eventbase OP

1d

@DTS Engineer None of the above linked documents answer any of these 4 questions.

Based on https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app we can answer questions 1 and 4 ourselves. We can expect that for all users with Brazilian App Store accounts:

Before the date, isEligibleForAgeFeatures will return false.
After the date, isEligibleForAgeFeatures will return true.

For Question 3, the Brazilian law says:

This Law shall enter into force six months after the date of its publication.

And I think it was published on September 17, 2025, so it should be effective March 17, 2026.

I don't know anything about Question 2's answer.

0

Answer 3

tomatomato OP

1d

Thanks a lot!

Re "we can answer questions 1 and 4 ourselves": eventually yes, but we don't have clarity from Apple today, and there's no way to find out from sandbox testing or otherwise today.

I agree IsEligibleForAgeFeatures will return true for Brazil. I didn't phrase it right, but my question for 1 is more on, after "true", what's the age range for someone who hasn't picked anything. I would assume the answer is "nil" as if they have declined, but a prompt may be reasonable too.

1

Answer 4

raphaelkohncr OP

23h

I was reading the documentation and it states that regulated regions will enforce the age sharing, so for those regions, there won't be a popup (at least that's what I understood), since the law enforces users to share that information.

I don't know if this is true for all regions that are regulated, but my understanding of the docs, is that if isEligibleForAgeFeature is true, then no prompt for the user is needed... I was just thinking about a way know if we need to ask, or if the information would come right away, because that will matter for me to measure impact here.

0

Answer 5

DTS Engineer OP

Apple

22h

Thank you for your inquiry. Unfortunately, I am unable to provide information on future dates. We have an API that is designed to cover the law as it becomes effective, not prior. However, I am not involved in that team. When the law becomes effective, please let us know if the API does not cover any of the requirements from the country and the correct team will take care of resolving any issue.

Albert Pascual   Worldwide Developer Relations.

0