Apple Adds Dating, Location and Companion Questions to App Store Age Ratings
Apple will add new content descriptor questions to App Store Connect so that age ratings better reflect what an app contains. Apps that declare dating or relationship content will receive a minimum age rating of 18+. The new descriptors are scheduled to appear on November 16.
The questions go beyond general content categories. Developers will have to declare whether their app shares a user's real-world location with another person or group. They will also have to disclose whether the app enables dating between real people, and whether it includes a virtual companion that engages in sexual or romantic content. Both age-rating questions must be answered when a developer submits a new app or changes an existing one. Developers must have answered both questions for all of their apps by January 12, 2027, which is roughly eight weeks after the descriptors go live.
Apple described the change in a developer news item titled "New age rating content descriptors in App Store Connect," published on November 2, 2026. Coverage of the update, including the November 16 date and the January 12, 2027 deadline, was published on November 3, 2026, by Engadget.
The ratings are only one half of Apple's age-related tooling. The Declared Age Range API lets an app request a user's age-range information without requiring the exact birthdate. Apple's developer news from February 2026 says the API's new signals include whether age-related regulatory requirements apply to the user. Apple's kids documentation states that developers can use the API to deliver age-appropriate content and experiences based on a child's age range.
The broader context here is a split between two kinds of age data. The rating questions describe the app: what it does, who can be matched with whom, and whether an AI character behaves in sexual or romantic ways. The Declared Age Range API describes the user, and it does so without handing over a date of birth. An app built to comply with both would need to know its own risk profile and also how to ask the platform for the minimum information it needs about the person on the other end. For a dating product, those two answers together determine what the onboarding flow looks like.
In my view, the most consequential detail is the virtual companion category. Developers of AI companion apps will have to make a classification decision that the rating system did not previously ask for in this form. Whether a given product's conversational output falls within "sexual or romantic content" will be a judgment the developer makes when answering the question, and the 18+ floor attaches automatically once a dating or relationship declaration is made. Declarations of this kind depend on developers answering accurately, and the gap between a declaration requirement and a verification mechanism is where enforcement questions will land.
The location question is narrower but touches a different set of products. An app that shares a user's real-world location with another person or group, whether a family tracker, a meetup tool or a social feature, now has to say so in its metadata. Developers building location features should expect the question to shape how their rating is computed, not only how it is described.
For teams with large catalogs, the practical arithmetic is short. The descriptors appear on November 16, every new submission and every update to an existing app will require both answers, and every app in the account must carry them by January 12, 2027. Teams that maintain older apps without frequent releases will need to schedule metadata reviews deliberately rather than waiting for a routine update to prompt one.
There is also a constructive reading. Ratings that describe an app's actual behaviour give parents, schools and younger users a clearer basis for decisions than a generic label does, and the Declared Age Range API offers a way to tailor content without collecting birthdates the app does not need. Used accurately, the two systems can narrow the gap between what an app does and what the store tells people it does. Whether that happens will depend on how carefully developers answer the new questions in the next two months.
