Guideline 5.1.1 Forced Sign-up Rejection: How to Fix It

What this rejection means

The app requires an account, or personal details, before people can use parts of it that don’t depend on an account. Apple wants those parts usable without signing up.

Why reviewers send it

Apple limits personal data collection to what a feature really needs. Locking content or tools that work without an account behind a sign-up wall counts as collecting data that isn’t necessary.

The message App Review sends

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

We noticed that your app requires users to register before accessing non-account-based features. Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app.

The exact wording changes from one review to the next; the guideline number is what to look for.

How to fix it

Let people browse or try the core features as a guest. Ask for an account only when it is needed: saving, syncing, purchases.
Don’t ask for details the feature doesn’t need, such as a phone number or a birthday.
If the app is entirely account-based — a company tool, a social network — say so in the reply and the review notes.
Upload a new build.

Fix it with Lovable, Bolt or Cursor

If the app was built with an AI builder, paste this into it, then check the result on a phone:

Let users open the app and use [features] without signing in. Show the sign-in screen only when they try to save, sync or purchase.

What to reply in App Store Connect

Replace the [brackets] with what you actually changed:

Guideline 5.1.1 — People can now [browse / try X] without an account. We only ask them to sign up to [save / sync / purchase].

Got a different message?

Paste the whole rejection into the rejection explainer. It recognises this one and 26 others, in your browser — nothing is uploaded.

Guideline 5.1.1: sign-up required to use the app