Guide · 9 min read
App Store Social Media Disclosure 2026: What to Declare, What the 13+ Flag Costs, and 5 Edge Cases That Catch Indie Devs
Apple added a new mandatory question to the App Store Connect age rating questionnaire on July 9, 2026: does your app include social media capabilities? From September 2026, every new app, every update, and every notarization for alternative distribution must answer it. The question sounds simple. Apple's definition of "social media capability" is not — and apps across categories from fitness to productivity to education are qualifying when their developers assume they won't.
What "social media capability" means in Apple's own words
A social media capability is defined by Apple as the ability to redistribute, amplify, or interact with user-generated content through a social feed or similar discovery method. The definition is intentionally broad. The operative phrase is discovery method — Apple is not just describing apps that call themselves social networks. It is describing any surface where user-generated content becomes visible to users who did not directly seek it out.
A social feed, under this definition, is any interface that surfaces content from other users to a viewer who did not specifically request that content. A chronological list of posts from people you follow is a social feed. A trending tab that surfaces popular community posts is a social feed. A discovery section showing top user-generated recipes is a social feed. Apple's definition does not depend on whether users can follow each other, create profiles, or send direct messages — it depends on whether UGC flows outward through a discovery mechanism.
The definition also covers interaction: liking, reacting to, or commenting on content that causes it to spread further counts as amplification. An app where users can upvote content that then surfaces in a trending section qualifies — even if the app has no follower graph, no profiles, and no direct messaging. Understanding this breadth is the prerequisite for assessing your own app accurately before the September 2026 deadline.
The 5 edge cases that catch indie developers off-guard
1. Fitness and activity apps with shared feeds or public leaderboards. A fitness app that shows your workout next to other users' workouts in an activity feed qualifies. A leaderboard counts if users can browse each other's names, scores, and free-text entries — especially when content is surfaced by rank or algorithm rather than a direct search. Solo-tracking apps with any community tab or friend-activity feed now face the same declaration requirement as dedicated social fitness platforms.
2. Productivity apps where users comment on shared documents. If your productivity app lets users share a document and other users can leave comments, reactions, or annotations that are visible to third parties outside the original document creator, this is a social mechanism. The comment is user-generated content; the ability for a viewer to read it constitutes interaction with UGC. Collaborative annotation features and document-level comment threads fall squarely in scope.
3. Educational apps with discussion boards or peer feedback threads. A class discussion board, student Q&A forum, or peer review mechanism in an edtech app is a social feed by Apple's definition. The audience may be constrained to classmates, but the redistribution of UGC through a non-search discovery mechanism — a feed sorted by recency or votes — still triggers the requirement. The under-13 exemption path is particularly relevant here for schools serving minors.
4. Recipe, travel, and reading apps where public reviews form a discovery feed. If your app has a "what's popular" or "trending recipes" surface that aggregates user reviews into a browsable collection, that surface qualifies. A curated algorithm that surfaces content based on engagement is amplification even without user-facing social graphs. Apps where users rate and review, and where those ratings feed an algorithmically ranked discovery surface visible to others, should audit this carefully.
5. Games with guild chat, community hubs, or public player showcases. A game leaderboard with free-text usernames visible to all players, a guild or clan chat, a community hub with posted achievements, or a Hall of Fame screen that showcases top players' submitted content all qualify. Many games that have historically avoided the Social category classification will need to re-evaluate, because the threshold for the social media capability declaration is lower than the threshold for an app being categorized under Social.
What the "Social Media" content descriptor does to your App Store listing
Any app that declares a social media capability receives two automatic changes to its App Store listing. First, a "Social Media" content descriptor appears on the product page — similar to how "Contains In-App Purchases" displays under your app's age rating. This is visible to every user before downloading and to every parent evaluating the app for their child. Second, the app receives a minimum 13+ age rating. If your current rating is 4+, 9+, or 12+, it floors to 13+ upon submission. There is no override.
The age rating change affects more than parental controls. Apple's Screen Time and the new parental Time Allowances feature — announced alongside this requirement at WWDC 2026 — now have a dedicated Social Media category. Apps rated 13+ for social media capability automatically fall into this bucket. That means parents who configure a Time Allowance for social media will also control access to your app, alongside Instagram, TikTok, and YouTube. This is a meaningful placement change for apps that have never previously appeared in any social-adjacent parental control flow.
The practical conversion impact depends on your audience. Fitness, productivity, and professional tools targeting adults will see minimal install disruption — 13+ is not a meaningful filter for those users. Apps in the 4+, 9+, or 12+ brackets that serve families or schools will feel the change most directly. This is also a good time to review your App Store privacy labels — both disclosures appear on the same product page and are typically reviewed together by privacy-conscious parents evaluating an app for their household.
How to answer the social media questionnaire in App Store Connect
The questionnaire lives inside App Store Connect under your app's App Information → Age Rating section. The updated questionnaire includes a new "Social Media" section with two questions: whether your app includes a social media capability, and if yes, whether social features are disabled for users under 13. You can answer both questions today — they became available as of July 9, 2026, and become mandatory at your first submission after September 2026.
Answer the first question based on Apple's definition, not based on what category your app is listed in. The Social category in the App Store is separate from the social media capability declaration. An app categorized under Productivity can still have a social media capability if it meets the redistribution or amplification definition — and Apple's review team will verify the binary against the questionnaire answer. A mismatch between your declared answer and your app's actual features is treated as a metadata accuracy issue and can trigger rejection or a more thorough review on subsequent submissions.
If you are unsure whether a specific feature qualifies, Apple's WWDC 2026 App Store guide includes expanded definitions with examples. When in genuine doubt, the conservative choice is to declare the capability. The listing impact of a 13+ rating is modest for most adult-targeted apps, and a false negative is harder to fix after submission than a correct positive declaration made proactively. Developers going through their first compliance audit should also walk through the App Store Connect submission guide, which covers every age rating field in the full submission flow context.
Disabling social features for under-13 users: what it does and what it requires
Declaring that your social features are disabled for users under 13 does not lower the 13+ age rating — it stays. What changes is the Time Allowances classification: apps that disable social features for under-13 users are excluded from the parental Social Media Time Allowances category for those users. This is the path for edtech apps and family-focused apps that have community features but want Apple and parents to understand that children under 13 experience those features in a disabled state.
Apple requires at minimum the Declared Age Range API to check age ranges before enabling social surfaces. The API lets your app query whether a given user falls below an age threshold without receiving their actual birthdate — Apple handles identity, your app receives an age tier, and you gate social surfaces accordingly. An app that declares social features disabled for under-13 without implementing this check will fail review, because Apple verifies the implementation in the submitted build. This is a declaration of existing technical reality, not a statement of intention.
For apps serving schools through Apple School Manager or apps enrolled in Family Sharing flows, the under-13 declaration also interacts with Managed Apple IDs. If your app serves both adults and students, implement the age range check at the feature level rather than the account level so adult users see social surfaces normally while student users do not. Apps that serve only adults can safely skip this path entirely — the social media capability declaration alone is the field that matters for most indie apps. The App Store Connect analytics guide covers how age-segment data appears in your analytics dashboards after the declaration takes effect.
The September 2026 deadline: what it covers and what happens to existing apps
Existing published apps with no pending updates are not immediately affected. The social media capability declaration is required only at the point of submission — a new binary, a metadata-only update, or a build submitted for notarization for alternative marketplace distribution. An app already live on the App Store with no pending submission does not need to answer the questionnaire until the next change is filed. This grace period ends the moment you submit.
Once you do submit, the questionnaire is blocking. App Store Connect will present the social media questions as a required step for any app that has not yet answered them, and you cannot skip past it to upload your binary. Prepare your answers before you build — discovering you need to make an implementation decision about the Declared Age Range API after uploading a binary is an avoidable delay that costs a re-upload cycle. The same mandatory-on-update pattern applies to privacy label declarations; both are checked at submission, not pushed proactively before your listing goes live.
If your app triggers a social media capability flag and you have not implemented the under-13 feature gate, note that review teams have been briefed on this requirement since WWDC 2026. Apps that declare "no social media capability" but include features that clearly meet the definition are running a rejection risk on the feature review pass. The safest path — especially for apps with community or sharing features — is to audit your surfaces now, answer the questionnaire accurately, and submit once rather than cycle through rejections. Developers who have navigated the most common App Store rejection reasons will recognize this pattern: the biggest compliance risks are the ones declared inaccurately, not the features themselves.
Answer the questionnaire before your next submission, not during it
The social media capability questions are available in App Store Connect today — no update submission required to fill them in. The highest-value step right now is auditing your app against Apple's redistribution and amplification definition, deciding your answer, and if you answer yes, deciding whether the under-13 Declared Age Range API path is worth implementing before your next release. Do that audit now rather than at 2am before a planned release.
If your answer is no — no social feed, no amplification surface, no UGC redistribution mechanism — document the reasoning internally so you can articulate it during review. If your answer is yes, the 13+ floor is not a catastrophe for most apps; it changes nothing visible to your core adult users, and the content descriptor signals transparency rather than risk.
Update your App Store listing in the editor →
Frequently asked questions
what counts as a social media capability for the app store questionnaire
Apple defines a social media capability as the ability to redistribute, amplify, or interact with user-generated content through a social feed or similar discovery method. Any surface where user-generated content becomes visible to users who didn't specifically request it — a trending tab, an activity feed, a community leaderboard with free-text entries — qualifies. The app does not need follower graphs, profiles, or direct messaging to meet the definition.
does the app store social media declaration change my age rating
Yes. Declaring a social media capability sets a minimum 13+ age rating on your app at your next submission. If your current rating is 4+, 9+, or 12+, it floors to 13+ automatically. Declaring that social features are disabled for users under 13 does not lower the age rating — it only removes your app from the parental Time Allowances Social Media category for under-13 users.
when is the app store social media disclosure mandatory
From September 2026, the declaration is required for every new app submission, every update, and every build submitted for notarization for alternative distribution. Existing live apps with no pending update are unaffected until they next submit a change. You can answer the questionnaire today in App Store Connect under App Information → Age Rating without submitting a binary.
do game leaderboards count as social media capability on the app store
Leaderboards can qualify depending on their design. A leaderboard that shows players' usernames and scores in a browsable, algorithmically ranked list visible to all players is a social feed under Apple's definition. A private leaderboard showing only a user's own rank relative to mutually opted-in friends sits closer to a social graph feature. The key question is whether content is being surfaced to users who didn't specifically seek out that content.
how do i disable social features for users under 13 in my app
Implement the Declared Age Range API to check whether a given user falls below an age threshold before enabling social surfaces. The API returns an age tier without exposing the user's actual birthdate. Gate activity feeds, comment threads, and community boards behind this check so they do not load for users under 13. The declaration in the questionnaire is not sufficient on its own — Apple verifies the technical implementation in the submitted build during review.