App Store RejectionGuideline 2.3.10 — Accurate Metadata — Login Requirements

You're Making Users Create an Account Before They Can Do Anything

If your app forces account creation before users can access features that don't actually require personalization or storage, Apple will reject it. Guest mode or browse-before-sign-up is now expected.

What Apple said

“Your app requires users to create an account before they can access any features or content. Apps may not require account creation for features that do not require user-specific data. Please provide a way for users to access the app's functionality without an account, or clearly indicate what functionality requires an account.”

What this actually means

Apple's position is that users shouldn't have to hand over their email address just to see what your app does. If the core functionality doesn't inherently require a persistent user identity — browsing content, reading articles, playing a game — then users should be able to try it first. Account creation should be prompted when it genuinely adds value, not as a gate to everything.

What Apple needs to see

  • A guest or browse mode that allows access to core app features without requiring sign-up
  • Account creation prompted only when features genuinely require a user identity (saving progress, syncing, social features)
  • A clear explanation on the login screen of what additional features become available with an account
  • Easy dismissal of any sign-up prompt so users can continue without creating an account
  1. 1Identify every feature in your app and categorize which ones genuinely require a user account and which don't
  2. 2Build a guest mode that allows unauthenticated access to all features that don't require personalization or server-side user data
  3. 3Move account creation prompts to moments where they add clear value — saving work, accessing premium features, setting preferences
  4. 4Add a 'Continue without account' or 'Browse as guest' option to any login or sign-up screen
  5. 5Update your support page at yourapp.baseterms.com/support to explain what features require an account and why

While you're at it — Apple also requires these pages for every app.

Fix this rejection, then make sure you're covered on the compliance side too. Apple requires every app to link to a hosted Privacy Policy, Terms of Service, Support page, and Data Deletion page. No link means another rejection — just for a different reason.

Privacy Policy
Terms of Service
Support Page
Data Deletion Page
Generate my compliance pages — $9

Common questions

My app is entirely social — every feature requires an account. Is that okay?
For genuinely social apps, Apple understands that an account is required. The key is making that obvious in your App Store description and, where possible, offering a read-only or preview mode so users can see what they're signing up for. A Twitter-like browse mode before sign-up is a good model.
I need users to agree to my terms before they can use the app — can I show that before a guest mode?
Yes, a terms of service or age verification gate is acceptable before accessing content, as long as it doesn't require account creation. Linking to your terms at yourapp.baseterms.com/terms before the main app experience is fine — it's the account creation requirement that's the issue.
What if guest mode data loss is confusing to users — like losing their cart?
That's expected behavior for a guest experience and Apple accepts it. What you can do is prompt account creation at the moment of potential data loss — 'Create an account to save your cart' — rather than requiring it upfront. That's the pattern Apple wants to see.