# Guideline 5.1.1: sign-up required to use the app > Rejected under Guideline 5.1.1 for making users register before using features that don’t need an account? How to add guest access, and the reply. **Guideline 5.1.1 — Data collection: don’t force sign-up for features that don’t need it.** 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. - App Store · Guideline 5.1.1. Data collection: don’t force sign-up for features that don’t need it. - Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-sign-up-required - Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer - Last updated: 2026-10-14 ## 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 1. Let people browse or try the core features as a guest. Ask for an account only when it is needed: saving, syncing, purchases. 2. Don’t ask for details the feature doesn’t need, such as a phone number or a birthday. 3. If the app is entirely account-based — a company tool, a social network — say so in the reply and the review notes. 4. 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](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded. ## Other App Store rejections - [App Store Guideline 4.3 Spam rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-3-spam) - [Guideline 4.2 Minimum Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-2-minimum-functionality) - [Guideline 2.1 App Completeness rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-app-completeness) - [Guideline 2.1 Information Needed: demo account](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-information-needed-demo-account) - [Guideline 4.0 Design rejection: sign-in in Safari](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-0-design) - [Guideline 2.3.3 Accurate Metadata: screenshots](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-3-screenshots) - [Guideline 2.3.10: Android mentioned in the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-10-other-platforms) - [Guideline 2.3.8: app icon or name doesn’t match](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-8-app-icon) - [Guideline 4.8 Login Services: Sign in with Apple](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-8-sign-in-with-apple) - [Guideline 5.1.1(v): account deletion required](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-v-account-deletion) - [Guideline 5.1.1: permission purpose string](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-purpose-string) - [Guideline 5.1.1(i): privacy policy link missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-i-privacy-policy) - [Guideline 5.1.2: App Tracking Transparency](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-2-app-tracking-transparency) - [Guideline 3.1.1: digital goods without In-App Purchase](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-1-in-app-purchase) - [Guideline 3.1.2: subscription information missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-2-subscriptions) - [Guideline 1.5: support URL doesn’t work](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-1-5-support-url) ## Fixed it? Send the build back to App Review CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode. [Get started free](https://capwr.app/login). ## About CapWrapp CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)