Latest in AI
Apple’s AI Companion Age Rating: What Changes and When
Romantic AI features will trigger an 18+ minimum, creating a product decision for apps that serve more than one audience.
Apple is adding an 18+ minimum age rating for apps with dating or relationship features, including virtual companions that engage users in sexual or romantic content. Announced November 2, the change gives AI app developers a concrete deadline to review what their products actually offer.
Which AI companions are covered?
The Apple Developer notice defines a new Dating and Relationships descriptor. It covers connections between people and relevant interactions with virtual companions. The wording does not make every chatbot or AI assistant an adult-only app merely because it uses AI.
That distinction matters for a general-purpose product. A team might think of romance as one optional mode among many. The rating question concerns whether the app includes the feature, so treating it as a small part of the interface does not make the classification irrelevant.
The product’s available experiences matter more than its marketing category. Developers should assess the actual feature against Apple’s definition rather than assume that calling an app an assistant settles the question.
November 16 rollout, January 12 deadline
The descriptors arrive in App Store Connect on November 16, 2026. Developers must answer the new questions when submitting an update or changing the age-rating questionnaire. Every app must complete the declarations by January 12, 2027.
The same notice adds a Shared Location descriptor. It concerns sharing a user’s real-world location with another person or group, a separate capability from romantic interactions. Regional rating requirements differ, so the two answers should not be treated as interchangeable.
A rating is different from an age check
Apple’s age-rating documentation explains that questionnaire answers generate the rating used by parental controls. It separately describes age assurance as a mechanism for checking whether someone meets an age requirement.
That separation is useful for planning. Updating a store declaration describes the app’s content. Designing age-appropriate access inside the app concerns how people encounter that content. A team should review both rather than assume a label alone resolves every access question.
The notice is a classification change, not a complete implementation recipe for mixed-audience apps.
What this changes for AI product teams
My reading is that the hard work begins before someone opens the questionnaire. A founder needs a clear inventory of the experiences the product supports, including optional modes and character interactions, and an explanation that engineering, product and distribution teams can all use.
For a product serving both everyday assistance and romantic companionship, that can turn into a decision about audience and product boundaries. It is worth resolving before committing to a launch aimed at younger users, rather than discovering during submission that the product and its intended distribution no longer line up.
The useful question is now very specific: which experience are you building, for whom, and can the product enforce the boundary you describe?
I’m Paras. I work at the intersection of AI, engineering and distribution.
I help technical founders explain product decisions and launches in language developers and customers can understand.