A flirty AI character now makes your app 18+.
On November 2, 2026, Apple announced two new questions for the App Store age rating questionnaire, and they went live in App Store Connect on November 16. One asks whether your app shares a person’s location. The other asks whether it enables dating, or offers a companion that gets romantic or sexual with the user. They look like a matched pair. They aren’t. For most of the world, the first adds a label and leaves your rating alone. The second puts you at 18+, with no way to argue it down.
What Apple added, word for word
The two declarations, as Apple defines them:
- Shared Location: “Sharing of real-world location with another person or group.” It sits in the Capabilities section, next to messaging, user-generated content and advertising.
- 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.” It sits in Mature Themes.
You have to answer both the next time you submit an update or touch the questionnaire, and every app has to have them answered by January 12, 2027. Apple’s notice doesn’t say what happens to an app that misses the date. Going by how the last round of new questions was enforced, expect the next submission to stop at the form until you fill it in. So if you plan to ship anything in the first weeks of January, answer them in December rather than on release day.
Shared Location: a label, not a jump, in most places
Apple’s rating tables map a yes on Shared Location to 4+ in the default global ladder, and to the lowest tier in Korea and Vietnam too. Apple’s own phrasing is careful: it “may not have an impact on their minimum age rating in some regions.” For an app that’s 4+ today, answering yes keeps it 4+ almost everywhere.
The exception is Brazil. Local rules there require A16 for Shared Location, a higher tier than messaging and chat (A12). A family location app built for parents and children is the obvious casualty, and Apple names that case directly: you can ask Brazil’s Ministry of Justice and Public Security for an official rating, and once it’s verified, that rating replaces the self-rated one on the Brazilian storefront. If Brazil matters to your install base, start that request now. It’s a government process, not an App Store Connect toggle.
Which features count as sharing a location
Apple’s definition is broad. It “may include: sharing a current or ongoing location with another person or group, live or background sharing, and precise or approximate location.” So city-level counts, a one-off pin counts, and it doesn’t matter whether the app is open. Apple gives no worked examples, so what follows is my reading of that sentence, not Apple’s ruling:
- Clearly yes: find-my-friends maps, live location in a chat, “share my run” links, family trackers, and a meetup feature that shows where everyone is.
- Probably yes: sending a current-location pin to another user, or attaching your present location to a post other people see. The definition says “current”, and there’s another person on the receiving end.
- Probably no: using location only to fetch results for the user themselves, such as weather, nearby stores or a map of where they are. Your server isn’t “another person or group”.
- Worth a careful look: photo apps that keep GPS metadata in shared images. If a photo leaves your app with its coordinates intact, you’re sharing a real-world location whether you meant to or not. Stripping it on export is the honest fix, and it’s better for privacy anyway.
Since a yes costs nothing at 4+ in most regions, the stakes are low outside Brazil. When you’re unsure, answer yes. Under-declaring is the failure both stores treat as misrepresentation.
Dating and Relationships: 18+, with no “infrequent” option
This is the one with teeth. Apple says apps that include it “receive a minimum age rating of 18+.” The regional tables match: A18 in Brazil, 19+ in Korea, 18+ in Vietnam.
Most content questions let you pick a frequency, so a single mild scene rated “infrequent” can keep you in a lower tier. This descriptor has no frequency setting. It’s yes or no, and yes means 18+. Apple’s override only goes one way, too: you can raise a calculated rating to meet your own terms of service, but you can never lower it.
The “real people” half is what you’d expect: “profiles, matching, or introductions intended to connect people for these purposes.” Dating apps were never going to be 4+. The newsworthy half is the other one.
The AI companion clause
Apple’s definition goes on to cover a “persistent character, avatar, or conversational companion that engages the user in sexual or romantic exchanges, whether scripted or generated.” The last three words are the point. A language model that flirts counts exactly like a writer who scripted the flirting. Apple cares about what the character does, not how the words got made.
If romance is part of what you sell, such as a companion app, an interactive story with a love interest, or a role-play character, the answer is yes and the app is 18+. Price that into the plan. An 18+ app is hidden from anyone whose Screen Time restrictions are set below 18+.
The harder case is a general assistant or character that can be pushed into romance even though that isn’t the product. The definition is about features that engage the user that way, so the defensible position is to make sure yours doesn’t:
- Say it in the system prompt. Tell the character to turn down romantic and sexual role-play and steer back to its job. A persona with a name, a face and a memory is exactly the “persistent character” the definition describes, so it needs this most.
- Check the output, not just the input. Instructions in a prompt are a request, not a wall. Run replies through a moderation pass, or a cheap classifier call, before they reach the user. Then ask yourself: if a reviewer spent ten minutes trying, would the guardrails hold?
- Test it the way a reviewer would. Keep a short list of prompts that try to start a romance (“be my girlfriend”, “pretend we’re dating”) and run it against every model or prompt change before release. A model upgrade can quietly loosen behaviour you tested months ago.
If the guardrails hold, you’re honestly answering no. If you can’t make them hold, the honest answer is yes, and the real choice is whether the feature is worth an 18+ badge. What you can’t do is answer no and hope. Under-rating is the misrepresentation both stores punish.
What to do before January 12
For every app you have live, including the ones you haven’t touched in a year:
- Open the age rating questionnaire in App Store Connect and find the two new items.
- Go through your features against Apple’s “may include” lists above, not against what you think of as the app’s purpose. A support chat with a map pin counts.
- If you ship any AI character or companion, run the romance test prompts against the production prompt and model, and decide on yes or no from what actually comes back.
- If you’re a location app with real users in Brazil, start the official rating request with the Ministry.
- Add both questions to your release checklist. A chat feature that later gets a “share location” button, or a helper character that later gets a personality, changes your answer.
For how the rest of the questionnaire turns answers into a rating, and why a comments field or an in-app browser can raise it, see our earlier guide to the age rating form.