16 November 2026 · 9 min

New App Store age ratings: classify shared location and romantic AI companions correctly

From November 16, App Store Connect asks about real world location sharing and dating features. Teams running location products or romantic AI companions now need more than another checkbox.

New App Store age ratings: classify shared location and romantic AI companions correctly

A feature becomes an age rating question today

Apple is expanding the age rating questionnaire in App Store Connect on November 16, 2026. It adds two content descriptors. Shared Location means sharing a real world location with another person or group. Dating and Relationships covers features that enable relationships between real people or a virtual companion that engages a user in sexual or romantic content.

The change looks small because it first appears as another choice in the App Store backend. It is bigger for product teams. Location sharing, matching, private messaging and AI companions do not exist only in a store description. They live in onboarding, permissions, moderation, support and marketing. A wrong declaration cannot be repaired with a quickly edited screenshot.

Anyone developing or operating an iOS app should now review the real product experience. The pitch deck does not decide the answer. The experience available after download does.

What Apple requires from November 16

The new declarations become required when a team submits an app update or changes the age rating questionnaire. Apple has also set a common deadline. Every app must complete both declarations by January 12, 2027.

According to Apple, apps that include Dating and Relationships receive a minimum age rating of 18+. Shared Location may have no effect on the minimum rating in some regions. Brazil has specific rules. Shared Location results in A16 and Dating and Relationships results in A18. A product designed specifically for parents and children may request an official lower Brazilian rating for location sharing from the responsible ministry.

This is not a recommendation to choose a particular answer. It is a reason to derive the answer from the product, document it and consider regional availability.

Shared Location is narrower than any map screen

Not every map and every request for location access is automatically Shared Location. A weather app may use location locally to deliver a forecast. A delivery app may send an address to a driver. A family app may keep a member's current position visible to other members. The implementation can look similar while the relationship between data, people and expectations is very different.

The central question for Apple's new descriptor is whether a real world location is shared with another person or group. Looking at the list of iOS permissions is therefore not enough. The team needs to understand the entire data journey. Who can see the location, how long is it visible, does it update in the background and can the user stop sharing immediately?

A proper product inventory connects the interface, backend, push notifications and support processes. Only then does the team know which capability it needs to describe in the store.

Romantic AI companions are explicitly in scope

Apple does not classify every chatbot as Dating and Relationships. The new descriptor includes a virtual companion that engages a user in sexual or romantic content. A support bot, tutor or workout coach is not automatically covered. What matters is what the product enables and how it behaves in real use.

With generative AI, the marketing description alone is not reliable evidence. A model may accept romantic role play even when the landing page talks about motivation or entertainment. System instructions, moderation rules, user profiles, memory features and paid characters need to be reviewed together.

This is product work, not a wording exercise. A company selling a romantic experience should classify it honestly. A company that does not offer one needs technical controls that can identify and limit unwanted conversation paths.

An inventory beats a debate based on instinct

For every affected app, we would create a simple feature matrix. For each capability it records the people involved, the data exchanged, the content produced, the intended age group and the safeguards in place. The matrix is not a legal opinion. It creates one shared view for product, engineering, marketing and release management.

For Shared Location, the review includes live mode, last known position, location history, geofences, invitations and sharing links. For dating or virtual companions, it covers matching, private chats, profile images, generated content, memory and monetisation.

An abstract App Store question becomes a series of concrete product decisions. The same documentation helps with support cases, privacy requests and later releases.

Age suitability starts in onboarding

An age label on the product page does not protect anyone when the app itself tells a different story. Onboarding and permission screens should explain what is being shared and with whom. Before the first location share, a user should understand whether their position is visible once, during an activity or continuously.

AI companion and dating products need to set clear expectations for content, boundaries and reporting. A hidden paragraph in lengthy terms is not a substitute for an understandable decision at the right moment.

Good UX design makes safety logic both correct and visible. That helps users while reducing support tickets, negative reviews and friction during App Review.

Feature flags do not repair a wrong declaration

Many teams roll out new capabilities gradually. A romantic mode may be active in one country, live location may be limited to selected accounts or an AI character may be available only to subscribers. That can be sound engineering. The store review still needs to consider the experience reachable in the submitted version.

A feature flag must not become camouflage. If a capability can be activated remotely after review, release management needs to check its effect on the age rating, metadata and regional availability before activation.

A robust process connects product approval and store compliance. The check does not belong only to the iOS developer at the end. It belongs in the definition of done for the feature.

Marketing must describe the same app

The age rating, screenshots, description, website and advertising form one promise. If an app looks like a family product in the store while a campaign quietly sells romantic AI characters, it creates more than review risk. It damages trust and conversion.

An honest 18+ product can still speak clearly to its audience. Strong positioning does not come from hiding a relevant capability. It comes from saying precisely who the product is for, which problem it solves and where its boundaries sit.

For App Store Optimization, keywords and creative assets should match the real feature set. A higher age rating changes potential reach, but it can improve the quality of the audience. Relevant users are more valuable than a large number of unsuitable installs.

January 12 is a poor sprint boundary

Waiting for the deadline compresses product review, copy work, regional decisions and release risk into one narrow window. A dedicated compliance sprint before the next major update is a better plan.

First, the team lists every app and bundle ID. Then it completes the feature matrix. It reviews App Store Connect, onboarding, permissions, moderation, support copy and store metadata. Open questions receive an owner and a date. Only then should the questionnaire be updated.

This matters even more for agencies and companies with several apps. One central answer for the whole portfolio feels efficient, but it is rarely accurate. Each app needs its own assessment.

New apps need the rating discussion during product discovery

For a new location product, sharing rules shape the data model, permissions, invitations and deletion design. For an AI companion, the intended relationship with the user shapes moderation, minimum age, tone of voice and monetisation. Asking these questions just before the store upload is expensive.

We bring age suitability into product discovery and technical architecture early. The team defines allowed and disallowed scenarios, builds clear states for consent and revocation and plans signals for misuse or misclassification.

The result is more than a smoother store submission. It is a clearer product. Good compliance forces a team to describe a capability precisely. That precision improves UX, engineering and sales.

What we would review in an existing app now

We start with a real test account and walk through every role, country and paid area. We compare the result with the App Store description, screenshots, privacy copy and current questionnaire. For location capabilities, we trace the data all the way to its recipient. For AI features, we test typical romantic, sexual and borderline conversation paths.

Next, we close obvious gaps. Permissions become easier to understand, sharing receives a visible off switch, reporting stays within reach and store metadata becomes more precise. We update the age rating only when the product and its description tell the same story.

The review should be documented. Not as paperwork, but as the starting point for the next feature and the next app version.

Our conclusion

The new App Store age ratings are not a form problem. They make visible that Shared Location, dating features and romantic AI companions are sensitive product decisions.

Apple requires two new declarations from November 16, 2026 and sets January 12, 2027 as the deadline for all apps. Teams should use the time to review real capabilities, regional availability, onboarding, moderation and marketing together.

A checkbox alone only moves the risk. An honest product inventory creates a better submission, clearer communication and more trust with the people who actually use the app.

Primary sources

Apple Developer News: Upcoming New age rating content descriptors in App Store Connect provides the start date, definitions, minimum ratings, the January 12, 2027 deadline and the specific requirements for Brazil.

App Store Connect Help: Set an app age rating explains the questionnaire, global and regional ratings, required roles and the process for setting or changing an age rating.

App Store Connect Help: Age ratings values and definitions documents Apple's rating levels and how content descriptors apply across regions.

Cloud
Cloud
Contact us

We can say a lot. It is better to make something great together.

Tell us briefly what you have in mind — we will reply with a few concrete first thoughts.

Personal reply · usually within 1 working day · first call is free