From 16 November 2026, the age rating questionnaire in App Store Connect asks two new questions: does your app include Shared Location, and does it include Dating and Relationships? You'll have to answer them the next time you submit an update, and every app must have them answered by 12 January 2027. A "yes" to dating pushes your app to 18+ everywhere. A "yes" to shared location may not change your rating in most regions, but it means A16 in Brazil. Here's how to decide what applies, how to update the questionnaire, and what to do if a truthful answer raises your rating.
What Apple added, word for word
Apple's developer news post of 2 November defines the two descriptors:
Shared Location: "Sharing of real-world location with another person or group."
Dating and Relationships: "Features that enable dating or relationship connections between real people and/or a virtual companion that engages a user in sexual or romantic content."
The consequences, per the same post:
Apps with Dating and Relationships get a minimum rating of 18+.
Shared Location "may not have an impact on their minimum age rating in some regions."
In Brazil, local rules require A16 for Shared Location and A18 for Dating and Relationships.
The dates that matter
16 November 2026: the new questions appear. You must answer them when you submit an update or edit your age rating questionnaire.
12 January 2027: all apps must have the declarations completed.
The November post doesn't spell out what happens to apps that miss the January date. The last time Apple changed the questionnaire, adding the 13+, 16+ and 18+ tiers in July 2025, it asked for answers by a deadline "to avoid an interruption when submitting your app updates." I'd plan on the same: if you need to ship a hotfix in mid-January, you don't want a questionnaire standing in the way.
Does your app have "Shared Location"?
Read the definition literally: your user's real-world location is shared with another person or a group. Some honest yeses:
A "share live location" option in chat, including one that comes from a third-party chat SDK you dropped in.
Family or friend safety apps that show members on a map.
"Share my trip" in a ride or travel app.
Meetup or event apps that show who's nearby on a map.
And some likely nos: an app that uses location only to show the user nearby stores, weather or delivery slots, without showing that location to any other person.
The grey areas are features where location travels to another human as a side effect, like a delivery partner seeing a customer's pin. Apple's post doesn't address these cases. My suggestion: if a real person can see where your user is, treat it as sharing, and describe the feature in your Notes for Review so the reviewer sees your reasoning.
A quick audit to find every place your code touches location, on iOS and Android:
grep -rnE "CLLocationManager|startUpdatingLocation|requestLocation\(|FusedLocationProviderClient|requestLocationUpdates" \
--include=*.swift --include=*.kt --include=*.java --include=*.ts --include=*.tsx .
Each hit isn't a "yes". It's a list of places to ask: where does this coordinate end up, and who can see it?
Dating and Relationships: watch the AI companion clause
Dating apps are obvious. The second half of the definition is the one that will catch people: "a virtual companion that engages a user in sexual or romantic content." If your app has an AI character that can roleplay romance, that's 18+ now, even if dating isn't what your app is about.
That leaves three honest options:
Accept 18+ if romance is core to the product.
Remove or redesign the feature so the companion can't engage in romantic or sexual content, if your audience includes teenagers and the feature is peripheral.
Don't answer "no" and hope. With rule 2.5.19 now banning hidden or undocumented features, as covered in our breakdown of Apple's October guideline update, a feature that appears after review is a much bigger problem than an 18+ badge.
Brazil: A16, A18 and the official-rating route
Brazil is where Shared Location bites. If you believe your app deserves a lower rating there, for example a location-sharing app built for parents and children, Apple's post says you can request an official rating from Brazil's Ministry of Justice and Public Security. Apple's age rating reference notes that an official ministry rating takes precedence, and Apple updates the regional rating once it's issued.
How to update the questionnaire
Per Apple's App Store Connect help:
In Apps, select the app, then click App Information in the sidebar.
Click Edit at the top of the App Information page (for an app without a rating yet, use Set Up Age Ratings under Age Ratings).
Work through each section, answer the new descriptors, and save.
If your terms require users to be older than the calculated rating, use Override to Higher Age Rating; the help page says you must do this when your EULA sets a higher minimum age.
A pre-release checklist for the next six weeks
Run the location audit above, including third-party SDKs for chat, maps and social features.
List any AI character or companion features and decide which side of the romance line they sit on.
Update the questionnaire now, not on the day of an urgent release.
Check your Brazil rating if you answer yes to Shared Location.
Add a line to your release template: "Age rating questionnaire reviewed for new features."
If you're working through a stack of platform deadlines this quarter, our list of iOS 27 and Android 17 developer deadlines has the rest in one place. Two questions in a form is a small task; the trick is answering them before they block a release, not after.



