Since 16 November 2026, the App Store age rating questionnaire has two new questions: does your app include Dating and Relationships, and does it include Shared Location? You have to answer them the next time you submit an update, and every app must have them answered by 12 January 2027. Answer yes to Dating and Relationships and your app becomes 18+, and that includes AI companion apps with romantic chat, not just dating apps.
For most apps this takes five minutes in App Store Connect. For AI chat apps, social apps and anything with a map of friends, it’s a product decision. This guide covers what each question means, which features trigger it, how to answer, and what to change if 18+ would cost you your audience.
What changed in the App Store age rating questionnaire?
Short answer: Apple added two content descriptors to the age rating questionnaire in App Store Connect on 16 November 2026. Shared Location covers sharing someone’s real-world location with another person or group. Dating and Relationships covers dating between real people and virtual companions that engage in romantic or sexual content. Dating and Relationships means a minimum rating of 18+.
The details from Apple’s announcement of 2 November:
- You must answer both questions when you submit an app update or change your age rating answers.
- Every app must have them answered by 12 January 2027, even if you don’t plan to ship an update before then.
- Dating and Relationships gives your app a minimum rating of 18+.
- Shared Location may not change your minimum rating in some regions. In Brazil it means at least A16, and Dating and Relationships means A18.
This is the third round of age rating changes in about 18 months. In July 2025 Apple added the 13+, 16+ and 18+ ratings and new required questions. In July 2026 it added questions about social media features, required from September. If you haven’t opened the questionnaire since your first launch, you may have more than two questions waiting.
What counts as “Dating and Relationships”?
Apple’s definition has two halves:
- Features that let real people make dating or relationship connections. Dating apps, obviously. But also “meet people nearby”, match or swipe features, and community apps that are marketed as a way to find a partner.
- A virtual companion that engages a user in sexual or romantic content. This is the half that catches AI-built apps.
The second half matters because AI companion and character chat apps are among the most common things founders build with Rork, Lovable, Bolt.new and similar tools. If your app has an AI girlfriend, boyfriend or “partner” mode, a flirty character, or role-play that drifts into romance, it falls under this question. That’s true even if romance isn’t the main feature.
Apple already warned about this in its July 2025 update: you have to consider how AI assistants and chatbots affect the sensitive content in your app when you answer the questionnaire. The new descriptor makes romantic companions a yes/no question with a fixed result.
What is probably not Dating and Relationships: a general AI assistant that refuses romantic role-play, a relationship advice or coaching app that doesn’t connect people or play a partner, and a messaging app for people who already know each other. “Probably” is the honest word here. Apple’s age ratings reference page hadn’t been updated with the new descriptors when I checked on 17 November, so the announcement is the only official definition so far.
What counts as “Shared Location”?
Apple defines it as sharing real-world location with another person or group. The key word is another person. Your app using the user’s location is not enough. Someone else has to see it.
Likely yes:
- Live location sharing with friends or family, “find my friends” and family trackers
- Sending your location or a pin into a chat
- Group runs, rides or meetups that show members on a map
- Delivery and ride apps where a driver and a customer see each other’s position
Likely no:
- A store finder, weather by location or “restaurants near me”
- Location used only on the server, for example to pick a currency or a region
- Showing a fixed business address on a map
Outside Brazil, Apple says Shared Location may not change your rating at all. In Brazil it means A16. If your app is built for parents and children, Apple suggests you can request an official rating from Brazil’s Ministry of Justice and Public Security. Once it’s verified, that rating is shown on the Brazilian App Store instead.
Which features in an AI-built app trigger the new questions?
This is how I’d read the most common features in the apps founders send me. It’s my reading of Apple’s definitions, not Apple’s official position, so check borderline cases against the announcement and explain your choice in the review notes.
| Feature | Dating and Relationships? | Shared Location? |
|---|---|---|
| AI companion with a romantic or “partner” mode | Yes | No |
| AI character chat where users can steer into romance | Probably yes, unless you block it | No |
| General AI assistant that declines romantic role-play | No | No |
| Match, swipe or “meet people nearby” | Yes | Only if others see your location |
| Direct messages between strangers in a community app | Depends on how it’s marketed | No |
| Send your location into a chat | No | Yes |
| Friends or family on a live map | No | Yes |
| Store locator or “near me” search | No | No |
Two traps to watch for:
- Your App Store listing. If your description, screenshots or keywords say “meet new people”, “your AI girlfriend” or “find love”, a “no” in the questionnaire will look wrong to the reviewer. Your marketing and your answers have to tell the same story.
- Features you forgot about. A location share in support chat, a beta “date mode” behind a flag, an AI character a user can rename and flirt with. All of it is part of the app you’re rating.
How to answer the new questions in App Store Connect
You need the Account Holder, Admin, App Manager or Marketing role. Then:
- In Apps, select your app.
- In the sidebar, under General, click App Information.
- Click Edit at the top of the page to change your age rating answers. (On a brand-new app, click Set Up Age Ratings under Age Ratings.)
- Go through each section, including Dating and Relationships and Shared Location, and answer for every feature in the app, not just the main one.
- Check the calculated rating and the per-region ratings, then click Save.
You can change the answers without uploading a new build, so do it now rather than on the day you need to ship a fix. Apple’s step-by-step guide is in Set an app age rating.
While you’re there, write down why you answered the way you did, and who answered. The next time Apple adds a question, you’ll know what you decided and why.
Is an 18+ rating bad for your app?
It depends on who your users are. The age rating is what Apple’s parental controls use. If a parent limits a teenager’s account to apps rated 13+ or 16+, an 18+ app won’t be available to them.
- If your users are adults anyway (most dating apps, many companion apps, B2B tools), 18+ costs you very little. Answer honestly and move on.
- If teens are a real part of your audience (study apps, social apps, games with an AI character), 18+ can cut a big slice of your installs. Then it’s worth changing the product before you change the answer.
Never answer “no” to keep a lower rating when the feature is there. App Review can reject an update or ask you to fix the rating, and that usually happens at the worst moment, like the week you need to ship a fix.
How to keep a lower rating if your app doesn’t need romance
If the romance in your app is a side effect of a general-purpose AI character, you can often remove it rather than rate the whole app 18+. The goal is that your honest answer becomes “no”.
1. Make the companion decline romantic and sexual role-play
Put the rule in the system prompt on your server, not in the app. A prompt that ships inside the app bundle can be read and changed, and many AI-built apps call the model straight from the client. If yours does, that’s worth fixing for cost and security reasons anyway.
// Server-side only (an Edge Function, API route or Cloud Function).
type ChatMessage = { role: "user" | "assistant"; content: string };
const SAFETY_RULES = `
You are a friendly study and wellbeing companion.
Never take on a romantic or sexual role, including girlfriend, boyfriend or partner.
If the user asks for romance, flirting or sexual content, decline kindly
and steer back to how you can help.
`;
export function buildMessages(characterPrompt: string, history: ChatMessage[]) {
return [
// Safety rules go first and are not editable by the user or the character.
{ role: "system", content: SAFETY_RULES },
{ role: "system", content: characterPrompt },
...history,
];
}
2. Check the output, not just the prompt
Users are good at talking models out of their instructions. Run replies through a moderation check before you show them, and log what gets blocked so you can see what people try. If testers can still get romantic replies after a few minutes of trying, your honest answer is still “yes”.
3. Remove the romance from everything around the chat
Character names and avatars, onboarding copy, push notifications (“Your girlfriend misses you”) and the store listing all count. Change them together, then update the questionnaire.
Can you gate dating or location features by age instead?
You can, and for a social or location feature it’s often good product design. But be clear about what it does and doesn’t do.
For social media features, Apple’s questionnaire has a specific option: if they’re disabled for users under 13 (checked with at least the Declared Age Range API), your app isn’t treated as social media for that age group. Apple’s announcement for the new descriptors doesn’t mention an equivalent option. So, as far as Apple has said, hiding a dating feature from under-18s doesn’t lower your rating. If the feature is in the app, it’s in the rating.
Age gating is still useful to protect younger users from location sharing or messaging with strangers, and to meet age-assurance laws in some US states. Apple’s Declared Age Range API returns an age range without a birth date. In an Expo or React Native app, expo-age-range wraps it on iOS and Google’s Play Age Signals on Android:
import * as AgeRange from "expo-age-range";
// Returns true only when the OS reports the user as 18 or over.
export async function isConfirmedAdult(): Promise<boolean> {
try {
// Android: the user must agree to share age signals first. Returns null on iOS.
const status = await AgeRange.requestAgeSignalsAccessAsync();
if (status !== null && status !== "SHARED") return false;
const { lowerBound } = await AgeRange.requestAgeRangeAsync({ threshold1: 18 });
return lowerBound !== null && lowerBound >= 18;
} catch {
// Declined, not signed in or not available: treat as "not confirmed".
return false;
}
}
Three things to know before you rely on it:
- It needs an entitlement. Add
com.apple.developer.declared-age-rangetoios.entitlementsin your app config and build with Xcode 26 or later. - Older iOS versions report an adult. On iOS versions before 26, Expo’s module returns
lowerBound: 18, so it isn’t age verification for every user. - Hiding a button isn’t a gate. If the API still serves location data or opens a chat to an under-18 user, the feature isn’t really off. Enforce it on the server too.
What happens if you miss the 12 January 2027 deadline?
The first effect is certain: you won’t be able to submit an update until the new questions are answered, because Apple requires them with every update. Apple hasn’t said publicly what else happens to apps that miss the date. With earlier questionnaire deadlines, Apple’s warning was about interrupted app updates. Either way, the fix takes minutes now and can block an urgent release later, so don’t wait.
Don’t forget Google Play
Google Play rates apps through the IARC content rating questionnaire in Play Console, not Apple’s system. Look at it while the decisions are fresh. If your app is 18+ on the App Store and rated for teens on Google Play, users and reviewers will ask why. Google also offers Play Age Signals for age-dependent features, and the same expo-age-range code above covers it.
When to bring in a developer
Most founders can answer the new questions themselves in one sitting. It’s worth getting help when:
- Your app is an AI companion or character chat and you need to decide between 18+ and removing romance, then make that change hold up against users who try to break it
- The AI is called straight from the app, with the prompt and API key inside the bundle
- You need age gating that’s enforced on the server, not just hidden in the UI
- An update is already blocked or rejected over the age rating, and you also have a Guideline 4.3 spam rejection or another issue stacked on top
That’s the kind of work I do: getting AI-built apps through review and making them safe to run. If your app was made with Rork, see how I fix Rork apps. If you’re still preparing your first launch, the Lovable App Store guide covers the other steps. For anything else, send me your app and the features you’re unsure about and I’ll tell you how I’d answer and what, if anything, needs to change.
FAQ
Do I have to answer the new age rating questions if I’m not updating my app?
Yes. Apple says all apps must have the Shared Location and Dating and Relationships declarations completed by 12 January 2027. You can answer them in App Information without uploading a new build.
Does an AI chatbot app have to be rated 18+?
Not automatically. Only a virtual companion that engages users in sexual or romantic content falls under Dating and Relationships. A general assistant that reliably declines romantic role-play doesn’t. Apple does expect you to consider what your chatbot can produce, not only what you intended it to do.
Does using the user’s location count as Shared Location?
No. Shared Location is about showing someone’s real-world location to another person or group. Using location only inside the app or on your server, such as a store finder or local weather, isn’t sharing it with anyone.
Can I change my age rating later?
Yes. Click App Information, then Edit, and update your answers at any time. You can also override to a higher rating than Apple calculated, for example if your terms require users to be 18. You can’t choose a lower rating than your answers produce.
Does Shared Location make my app 16+?
In Brazil, yes: A16 is the minimum. In other regions, Apple says Shared Location may not change your minimum rating. Check the per-region ratings in App Store Connect after you save.
Further reading
- Upcoming: New age rating content descriptors in App Store Connect (Apple, 2 November 2026)
- Set an app age rating (App Store Connect Help)
- Age ratings values and definitions (App Store Connect Help)
- Age rating questionnaire now includes social media questions (Apple, July 2026)
- Requesting people’s age range information in your app (Apple)
- Expo AgeRange (Expo docs)