App Store Review Guidelines 2026: Every Change, and What Guideline 5.1.1(v) Actually Means

Apple revises the App Review Guidelines multiple times a year, usually in small clarifications rather than one big annual update, and 2026 has already brought several changes that actually affect how apps get approved. This is a running reference to what changed, what the most misunderstood guideline numbers actually mean, and where most 2026 rejections are actually coming from.

What Actually Changed in 2026

February 6, 2026 — Apple clarified that apps with random or anonymous chat features fall under Guideline 1.2 (User-Generated Content), not just the general safety rules. If your app connects strangers for chat, video, or messaging, you now need the same moderation, reporting, and blocking tools required of any UGC app, even if chat wasn't the app's original core feature.

June 4, 2026 — Following a Texas court ruling lifting an injunction on SB 2420, Apple Accounts registered in Texas became subject to state age-assurance requirements. Apps need to support the Declared Age Range API and honor parental consent revocation for users under 18 in that state.

June 8, 2026 — A broader Developer Program License Agreement and Guidelines revision touched several areas: export compliance identity verification (Sections 3.1, 14.8), the Sensitive Content Analysis framework (3.3.3(N)), the Suggested Actions API (3.3.3(Q)), and the Trust Insights framework (3.3.3(R)). Most of this affects apps using specific Apple frameworks rather than every developer.

June 9, 2026 — Guideline 4.3(b) (Spam) got noticeably stricter language around low-effort and "copycat" apps. Apple now explicitly calls out saturated categories like flashlights, simple timers, wallpaper apps, and fortune-telling apps, and states that apps which don't meaningfully improve on what already exists may not be accepted, and that existing low-quality apps that aren't maintained or don't attract users may be removed from the Store entirely.

Mid-2026 — A U.S. court decision forced Apple to update Guidelines 3.1.1, 3.1.1(a), 3.1.3, and 3.1.3(a), which govern buttons, external links, and other calls to action inside apps distributed on the U.S. storefront. This is the most consequential change for any app with external payment options, since it changes what you're allowed to say and link to inside your app regarding purchases made outside Apple's payment system.

None of this replaces the core guidelines. It layers on top of them, which is exactly why so many rejections in 2026 cite guideline numbers that developers assume haven't changed in years.

Guideline 5.1.1: The One Everyone Misreads

"Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage" is one of the most common rejection messages in App Store Connect, and it's also one of the most misunderstood, because it isn't one rule. It's a bundle of at least nine lettered sub-guidelines, and the fix depends entirely on which one got cited.

The three that show up most often in 2026 rejections:

• 5.1.1(i) — Missing or thin privacy policy. The policy URL field is empty, broken, or points to a policy that doesn't actually describe what your app collects.
• 5.1.1(v) — Account Sign-In. This is specifically about forcing registration for features that don't require an account. If your app makes users create a login before they can browse, preview, or use non-account features, this is the guideline that gets cited. The fix is almost always to add a guest or browse-first mode and only gate account-specific actions (checkout, saved items, personalization) behind sign-in.
• 5.1.1(ix) — Highly regulated services. Apps handling sensitive categories (health, finance, legal services) must be submitted under an organization Apple Developer account, not an individual one.

If your rejection just says "Guideline 5.1.1" with no letter attached, open the full message in App Store Connect's Resolution Center. Apple almost always references the specific sub-guideline by name in the body text, even when the subject line doesn't show it.

Guideline 2.1: App Completeness

"App completeness" rejections fall under Guideline 2.1, and by a wide margin it's the guideline developers hit most often, not because their apps are broken, but because the submission itself is incomplete. Common triggers:

• Crashes or bugs that appear during the reviewer's actual testing session
• Placeholder text, lorem ipsum, or "coming soon" content left in a shipped build
• Broken links anywhere in the app, including the privacy policy URL
• Missing demo account credentials for apps that require login, submitted in the App Review Information section
• Incomplete metadata, like a description that references features not present in the build being reviewed

The pattern across most 2.1 rejections is the same: reviewers can only evaluate what they can actually access and test. Anything that blocks that (a broken login, a missing test account, a feature description that doesn't match reality) reads as an incomplete submission even if the underlying app works fine for real users.

What "App Store Submission Requirements" Actually Means in 2026

There isn't one master checklist Apple publishes as "2026 requirements." What developers searching for this usually need is three separate things kept in sync:

1. The App Review Guidelines themselves — the content and behavior rules covered above
2. App Review Information — the demo account, contact info, and reviewer notes you fill in at submission time in App Store Connect, which Apple explicitly says can delay or block review if missing
3. Submission gates outside the guidelines — required reasons for certain APIs, Xcode and SDK version minimums, age rating questionnaire answers, and export compliance declarations

Missing an item in category 2 or 3 doesn't necessarily mean your app violates a guideline. It means the review can't start or complete, which produces the same result (a rejected or delayed submission) for a different reason.

Building This Into Your Pre-Submission Process

The guidelines shift often enough that a one-time reading isn't enough. A workable process:

1. Check the App Review Guidelines change log (developer.apple.com/news) before every major release, not just once a year
2. Keep a standing demo account active in App Review Information so reviewers can always test account-gated features
3. Audit your app for anything that reads as a near-duplicate of an existing popular app, given the tightened 4.3(b) language
4. If your app touches chat, messaging, or any user-to-user interaction, confirm you meet Guideline 1.2's moderation and reporting requirements even if that wasn't a core feature originally
5. Match your privacy policy, App Store Connect nutrition label, and actual data collection exactly, since 5.1.1(i) mismatches are still one of the most common rejection triggers

FAQ

What is Guideline 5.1.1(v)? It's the Account Sign-In sub-guideline. It requires that apps let users access non-account features without registering first, and reserves login requirements for features that are genuinely account-specific, like checkout, saved data, or personalization.

What does "app completeness" mean in an App Store rejection? It refers to Guideline 2.1, which covers crashes, placeholder content, broken links, missing demo credentials, and metadata that doesn't match the actual submitted build. It's consistently one of the most cited rejection guidelines because it covers anything that stops a reviewer from fully testing the app.

Did Apple update the App Store guidelines in 2026? Yes, several times. Notable changes include a February 2026 clarification bringing anonymous chat apps under Guideline 1.2, a June 2026 tightening of the anti-spam Guideline 4.3(b) against low-effort and copycat apps, and a court-mandated update to Guidelines 3.1.1 and 3.1.3 covering external payment links on the U.S. storefront.

How do I know which App Store submission requirements apply to my app? Start with the App Review Guidelines for content and behavior rules, then check App Review Information requirements (demo accounts, reviewer notes) in App Store Connect, and finally confirm any API-specific "required reasons" declarations or age rating updates apply to your app's specific features.

Where can I check the latest guideline changes myself? Apple posts every guideline revision to its developer news page as it happens, with the specific section numbers that changed. That's the most reliable source, since third-party summaries (including this one) can lag behind the official change log.