New App Store Age Rating Questions: What to Answer by 12 January Without Losing Your Audience
Since 16 November 2026, the age rating questionnaire in App Store Connect has two new questions: can people share their real-world location with others (Shared Location), and does the app include dating or romantic relationships (Dating and Relationships). Every app must answer them by 12 January 2027, and the answers are also required with every update or questionnaire change.
On paper it is a couple of checkboxes. In practice, one answer can raise an app to 18+, hide it from child and teen accounts with parental controls, and block a release right before the holidays. Here is what changed, how to audit your features, and how to avoid losing an audience over one careless answer.
What Apple announced
According to Apple's announcement of 2 November 2026, the age rating section gains two declarations:
- Shared Location: sharing real-world location with another person or group;
- Dating and Relationships: features that enable dating or relationship connections between real people, or a virtual companion that engages the user in sexual or romantic content.
Apps with dating features receive a minimum rating of 18+. Shared Location, Apple says, may not affect the minimum age in some regions. Brazil is the exception: local law requires A16 for location sharing and A18 for dating. If you believe your app deserves a lower rating (Apple's example is location sharing built for parents and children), you can request an official rating from Brazil's Ministry of Justice (MJSP). Once verified, that rating is shown on the Brazilian App Store.
Context: the third stage of a ratings overhaul
These questions are not a one-off. Apple has been rebuilding its age rating system for more than a year, and each stage added work for app teams:
| When | What changed | Deadline |
|---|---|---|
| July 2025 | New 13+, 16+ and 18+ ratings alongside 4+ and 9+. New mandatory questions: in-app controls, capabilities, medical and wellness topics, violent themes | 31 January 2026 |
| July 2026 | Social media questions: a feed or other mechanism that redistributes or amplifies user content. New Social Media descriptor and a Time Allowances category (iOS 27) | September 2026 |
| November 2026 | Shared Location and Dating and Relationships; dating means 18+ | 12 January 2027 |
The takeaway for product teams: the age rating is no longer a formality filled in once at first launch. It is part of the product spec and needs a review whenever a new social, location or AI feature ships.
Why this matters even for an "ordinary" app
The new questions most often catch products where the relevant feature appeared as a side effect, not obvious dating services:
- Delivery and ride-hailing. The courier or driver sees the customer's location, and customers share their trip with family.
- Family and education apps. Parents see where a child is; students check in to classes by location.
- Sports and events. Group runs, a meeting point on the map, "friends nearby".
- Communities and marketplaces. Direct messages between strangers that easily turn into dating.
- AI chatbots. A "virtual companion" with a romantic scenario is named explicitly in the Dating and Relationships definition, and since 2025 Apple has required teams to account for AI assistants and chatbots in their rating.
A wrong assessment hurts either way. Overstate it and the app disappears for some teens and family accounts, and marketing loses reach. Understate it and App Review may reject an update or demand a fix at the worst moment, such as before a holiday release.
Feature audit: how to answer correctly
We recommend not filling in the questionnaire from memory. Run a short audit with the product manager and a developer who knows the codebase. Typical cases and how we see them:
| Feature | Likely declaration | What to do |
|---|---|---|
| User sends their location to a chat or shares a route | Shared Location | Declare it; check whether it can be disabled for minors |
| Courier/driver sees the customer’s address during an order | Probably Shared Location | Compare with the definition in Apple’s help; document the decision |
| Store map or "nearest venue" | Usually no: location is not passed to another person | Explain in the App Review notes if the feature looks ambiguous |
| Direct messages between strangers | Possibly Dating and Relationships, depending on purpose | Check the description, screenshots and marketing: if the product is positioned as dating, the rating will be 18+ |
| AI companion with an emotional or romantic scenario | Dating and Relationships | Either restrict the scenarios or accept 18+ |
| Feed of user-generated content | Social Media (since September 2026) | Consider disabling the feed for users under 13 |
This table reflects our practice, not Apple's official position. For the final definitions see Age ratings values and definitions, and in borderline cases explain your decision briefly in the App Review notes.
Step-by-step plan before 12 January
- List the features that pass location to other people, let strangers communicate or use generative AI. Cross-check it against your specification; if you don't have one, start with our article on structuring an app specification.
- Open App Information in App Store Connect and review the current answers and the rating in each region: ratings can differ by country.
- Model the impact. If a "yes" raises the rating, estimate what share of your audience it affects. For family and education products this can be critical.
- Decide whether to change the product or the rating. Sometimes it is simpler to disable a feature for younger users than to raise the rating for the whole app.
- Update the questionnaire early, without waiting for a release. Answers can be changed separately from a build.
- Align Google Play. On Google Play the rating comes from the IARC questionnaire in Play Console. Keep the logic consistent across stores so you don't end up 18+ in one and 12+ in the other.
- Document the decision in the repository or wiki: who answered, when and why. It saves time on the next rules change.
Keeping a teen audience: age signals
If a feature can't be removed, it can be switched off depending on the user's age. Both platforms offer APIs that return an age category without an exact date of birth:
| Apple: Declared Age Range | Google: Play Age Signals | |
|---|---|---|
| Returns | An age range; the minimum age is in lowerBound | An age category: by default 0–12, 13–15, 16–17, 18+ |
| Setup | Declared Age Range capability in Xcode (entitlement com.apple.developer.declared-age-range) | The age-signals library; custom age thresholds are configured in Play Console |
| Limitations | Declared by the user or a parent, partly verified; responses are cached | Beta; data is returned only where the law requires it; may not be used for ads or analytics |
| Docs | Declared Age Range | Play Age Signals |
This is exactly the approach Apple describes for social features: if they are disabled for users under 13, the app is not placed in the Social Media category for that age group. It is reasonable to apply the same pattern to location sharing or direct messages, but check how the questionnaire treats your specific case.
From a UX point of view, an age check is one more step in the first run, and it should not destroy conversion. We covered this in our articles on onboarding without extra steps and on the first 60 seconds in an app. If your age gate needs a date entry, see our piece on mobile forms.
Common mistakes
- Leaving it until release. The new questions appear exactly when you submit an update. If the questionnaire is incomplete, the release stalls at the worst moment.
- Answering only for the main flow. Location in support chat, messaging in a beta feature, an AI helper in settings: it's all part of the app.
- Ignoring marketing. A description, screenshots and keywords that promise "meet new people" contradict a "no" in the questionnaire.
- Different logic in the App Store and Google Play. It confuses users and invites questions from reviewers.
- Relying on an age check without server-side logic. If a feature is only hidden in the UI but the API still serves the data, there is no protection.
Checklist
- List of location, user-to-user communication and AI features is complete.
- Current per-region ratings in App Store Connect are reviewed.
- Shared Location and Dating and Relationships answered before 12 January 2027.
- Social media questions (since September 2026) answered.
- For Brazil, an official rating request considered if A16/A18 doesn't fit the product.
- Google Play IARC questionnaire aligned with App Store answers.
- Declared Age Range / Play Age Signals with server-side checks implemented for age-dependent features.
- Store description and screenshots match the declared features.
- Decision documented and an owner for the questionnaire assigned.
The age rating is now part of the product, not just of publishing. Teams that review it when planning each new feature don't learn about the problem from an App Review email the day before release.
Sources: Apple: Upcoming new age rating content descriptors; Apple: Updated age ratings in App Store Connect; Apple: Age rating questionnaire now includes social media questions; Apple: Age ratings values and definitions; Apple: Declared Age Range; Google: Play Age Signals; Google Play: Content ratings; MJSP: Classificação Indicativa.



