Starting November 16, 2026, Apple will introduce mandatory age-rating declarations for apps that facilitate real-world location sharing or offer romantic and sexual content via virtual AI companions. Developers must identify these features within App Store Connect during any update or questionnaire change, with a universal compliance deadline of January 12, 2027.
Crucially, these rules apply to specific functionality rather than app branding. A multipurpose chatbot containing an optional romantic companion must still receive an 18+ rating. Developers should audit their entire catalog immediately, as these requirements apply to all apps regardless of update schedules.
Apple will require a minimum 18+ App Store rating for apps that offer dating or relationship connections between people, or virtual companions that engage users in romantic or sexual content. The company announced the change on November 2, 2026, alongside a new declaration for real-world location sharing.
Developers will encounter the new content descriptors in App Store Connect starting November 16, 2026. They must complete the declarations when submitting an app update or changing their age-rating questionnaire, and all apps must have them completed by January 12, 2027, according to Apple’s developer announcement.
The practical consequence for AI developers is straightforward: an app’s branding is not the deciding factor. A product marketed as a general chatbot can still contain a romantic-companion feature covered by Apple’s wording. Developers need to examine what their apps actually offer, then plan both the declaration work and any resulting age-rating change.
What Developers Must Declare
Apple is adding two content descriptors to the age-rating questionnaire in App Store Connect:
Descriptor
What developers must assess
Rating consequence
Shared Location
Whether the app shares real-world location with another person or group
May leave the minimum rating unchanged in some regions; Brazil requires A16
Dating and Relationships
Whether the app enables dating or relationship connections between real people, or offers a virtual companion engaging users in sexual or romantic content
Minimum 18+ rating; Brazil uses A18
These are declarations about features, with consequences for the app’s rating. Apple is asking developers to identify whether the functionality exists, not simply to choose a label that matches the app’s main purpose. The definitions and rating outcomes come directly from Apple’s notice.
For location sharing, the important detail is the recipient: another person or group. A review should therefore examine what location information is shared and with whom, rather than stop at whether the app requests location permission. Reading a location to provide a local service and sharing that location with other people are different functions.
The 18+ requirement is a minimum. Developers should not interpret it as an instruction to lower an existing higher rating or disregard other content declarations.
November 16 Starts the Submission Requirement
The announcement contains two operational deadlines: a requirement tied to submissions and questionnaire changes, followed by a deadline for the entire app catalog.
Date
What happens
Developer action
November 2, 2026
Apple publishes the announcement
Identify affected features and assign responsibility for the questionnaire
November 16, 2026
The new descriptors begin appearing in App Store Connect
Provide the declarations when submitting an update or changing the age-rating questionnaire
January 12, 2027
All apps must have completed the declarations
Finish the work even for apps without a planned release
November 16 and January 12 are 57 days apart, calculated from Apple’s published dates. That interval is useful for catalog planning, but it should not be treated as permission to postpone declarations during an intervening submission. Apple explicitly connects the requirement to app updates and age-rating questionnaire changes. Apple’s announcement also makes the January deadline universal.
An app with no planned update still needs attention. Equally, a team preparing a November or December release should put the declarations on that release’s submission checklist instead of treating January as its only deadline.
I’d prioritize apps by their next submission date, then work through the remaining catalog. That follows Apple’s two requirements more closely than organizing the task solely around the final deadline. It also gives teams time to resolve uncertainty about a feature before release preparation is under way.
Why Romantic AI Falls Within the Rule
Apple’s definition explicitly includes:
“a virtual companion that engages a user in sexual or romantic content”
That wording makes two details consequential. First, a connection with another human is not required. Second, sexual content is not the only trigger: romantic content is included independently. A developer cannot assume that removing explicit sexual material alone puts a romantic-companion feature outside the descriptor. Both points follow from Apple’s published definition.
The distinction matters for apps combining several kinds of conversation. Consider a hypothetical chatbot with a study assistant, a productivity helper and an optional virtual romantic partner. If that partner engages the user in romantic content, Apple’s wording points to the Dating and Relationships descriptor even though other parts of the product serve unrelated purposes.
The reasoning is specific: Apple assigns the minimum rating to apps containing the qualifying functionality. Its notice offers no separate rating mechanism for an individual companion inside a multipurpose app. Developers should therefore assess the consequence at the app level when planning their declarations.
TechCrunch’s November 3 coverage highlighted Character.AI and Replika as examples of the broader companion-app market relevant to the change. That provides context, not an Apple determination about either product’s compliance.
Apple’s announcement leaves some implementation questions open, including the boundary of romantic content, how reviewers will assess individual features, and enforcement details. It announces an age-rating and disclosure requirement, not an outright ban on AI companions or a new identity-verification procedure.
My view is that the most useful first step is a feature inventory, not a rewrite of the store description. Calling a product an assistant, character platform or entertainment app does not resolve whether it contains the functionality Apple describes.
Brazil Has Specific Rating Requirements
Apple identifies Brazil separately because local regulations require:
A16 for apps with Shared Location.
A18 for apps with Dating and Relationships.
Developers who believe their app qualifies for a lower Brazilian rating can request an official rating directly from Brazil’s Ministry of Justice and Public Security, or MJSP. Apple gives location sharing designed specifically for parents and children as an example of a feature that could justify such a request. Once verified, the official rating will appear on the App Store in Brazil. These conditions are set out in Apple’s announcement.
That is a request process, not an automatic exemption for anything marketed as family safety. A parent-child location app should still assess the Shared Location declaration, while separately considering whether to seek an official lower Brazilian rating.
For developers distributing internationally, the distinction is worth recording in the release checklist: the same feature declaration can have different rating consequences across storefronts. Apple specifically says Shared Location may leave the minimum rating unchanged in some regions.
A Practical Checklist for App Teams
The compliance work belongs across product, content and release management. The following steps are practical recommendations based on the requirements Apple has published.
Review every app in the catalog. Include older products with no scheduled release. The January 12 deadline applies to all apps, not only products actively shipping updates.
Inventory the relevant features. Record person-to-person dating or relationship functions, virtual companions with romantic or sexual interactions, and real-world location sharing with other people or groups. For multipurpose AI apps, examine optional modes as well as the default experience.
Review paid and optional experiences. A feature behind a subscription or optional setting still deserves assessment. Apple’s definition concerns included functionality; the announcement provides no paid-feature exception. This is a review recommendation, not a claim about a separately published paywall rule.
Connect the task to the next submission. From November 16, completing the declarations is part of submitting an update or changing the age-rating questionnaire. Assign an owner before that work reaches the submission stage.
Check regional rating consequences. Record the expected 18+ consequence for qualifying dating and relationship features, and assess Brazil’s A16/A18 requirements separately. If seeking a lower official Brazilian rating, plan for the request and verification process.
Set an internal deadline before January 12. Leave room to resolve disagreements over feature scope and check that every app’s declarations are complete.
The useful distinction is between declaring a feature and deciding whether to change it. Apple requires the declaration. A team may then have a separate product decision about keeping, changing or removing a romantic-companion feature after considering the app-wide rating consequence.
Frequently Asked Questions
3 questions
1
Are AI Companion Apps Being Banned?
No. This announcement introduces declarations and a minimum 18+ rating for qualifying features. It does not announce a general ban on AI companion apps.
2
When Must Developers Complete the Declarations?
The descriptors arrive November 16, 2026. Developers must provide declarations when submitting an update or changing the age-rating questionnaire, and all apps must complete them by January 12, 2027.
3
What About Location Sharing for Parents and Children?
It falls within the location-sharing assessment. In Brazil, developers who believe their app qualifies for a lower rating can request an official rating from the MJSP; Apple specifically identifies parent-child location sharing as an example.
