App Store Rejection Under Guideline 5.1.1: Data Collection and How to Fix It
Short answer: Guideline 5.1.1 covers how an app collects and stores user data, and a rejection under it almost always points to one of four issues: the app forces people to register before they can use features that do not need an account, it asks for personal details its core function never uses, a permission prompt's purpose text is vague, or sign-up is possible while removing a profile is not. Read the exact sub-point in the rejection message, fix that specific behavior in the build, describe the change briefly when replying to the reviewer, and resubmit. Answering with arguments instead of changes usually leads to the same rejection again.
Reading the rejection message
Apple's message quotes the guideline and usually adds a sentence or screenshot showing where the reviewer saw the problem. Look for the roman numeral in brackets after the guideline number, and the screen or step mentioned. That tells you which of the cases below applies. The full text of the App Review Guidelines is worth reading for the section named, because Apple updates the wording from time to time.
Case 1: Login required before use
A dog grooming business launches an app where the first screen is "Create an account". Behind it sit a price list, opening hours, a gallery and a booking form. The reviewer rejects it: people should be able to see non-account content without registering.
The rule in practice: if a feature does not depend on an account, let people use it without one. Booking and order history may genuinely need an account; browsing prices does not.
Fixes
- Make the first screen show public content, with a "Sign in" or "Book" action where an account becomes necessary.
- Ask for registration at the moment it adds value: when someone books, saves a favorite or views past orders.
- If the whole app is a members-only service, say so clearly in the App Store description and the review notes, and explain why every feature needs an account.
Case 2: Unnecessary personal data
Reviewers object when a sign-up form asks for things the app does not use: date of birth for a coffee loyalty app, gender for a parking app, a home address before anything has been ordered.
Fixes
- Remove fields the app does not need for its core function.
- Mark genuinely optional fields as optional and let people skip them.
- If you need a field for a legal or operational reason, such as age confirmation for a restricted product, explain that in the review notes and on the sign-up screen itself.
- Compare your App Privacy answers with the data the build really gathers. A mismatch invites questions.
Case 3: Permission purpose strings
When an app asks for camera, location, photos, contacts or similar access, iOS shows a system prompt with text the developer supplies in the project's property list file, for example the camera usage description. Rejections happen when the text is generic ("This app needs your camera"), missing, or does not explain the real use.
Fixes
Write purpose strings that say what the data is used for, in plain language:
| Permission | Weak text | Better text |
|---|---|---|
| Camera | "Needs camera access" | "Snap your dog's coat so the groomer can plan the appointment." |
| Location | "Uses your location" | "Show the nearest branch and estimated travel time on the booking screen." |
| Photos | "Access photos" | "Pick earlier pictures of your dog to add to its grooming profile." |
Also check timing: show each prompt at the moment a person opens the related function, never on the first launch screen. Do not use custom screens that pressure people to accept, and do not block the app if a non-essential permission is declined.
Case 4: No account deletion
Whenever registration is offered, Apple requires that they can start deleting that account from within the app. A link to an email address or a "contact support" note is generally not enough. Apple's page on offering account deletion sets out what is expected.
Fixes
- Add a clearly labeled "Delete account" option in account settings, reachable in a few taps.
- Explain what happens: which data is erased, which records legal duties oblige you to retain, and how long the process runs.
- Confirm the action before completing it, and confirm afterwards.
- Make sure the backend actually deletes or anonymizes the data; reviewers may test it.
- For people who registered through Apple's own login button, follow Apple's guidance on revoking tokens as part of deletion.
Replying to the reviewer
Replies go through the App Review messages for that submission. Keep them short and concrete:
Thank you for the review. We have made the following changes in build 1.0.3: the app now opens on the services and prices screen without requiring an account. Registration is only requested when a user starts a booking. Profile, Settings now also contains a button that removes the user's profile and personal data. Demo credentials are included in the review notes.
Then upload the new build, attach it to the version and resubmit. When the reviewer seems to have misread how the app works, a calm written explanation is the first move; a formal appeal to Apple's review board is the last. Use that route sparingly, and only when the app genuinely complies.
Avoiding a resubmission loop
Teams often fix the one screen in the rejection, resubmit, and get rejected for another 5.1.1 point the reviewer did not mention the first time. Before resubmitting, check all four cases together:
- Can a new user see something useful without registering?
- Is every sign-up field necessary or clearly optional?
- Does each permission prompt explain the specific use, at the right moment?
- Can a user delete their account inside the app?
- Do the App Privacy answers in App Store Connect match the build?
- Are demo credentials in the review notes working and not expired?
Test on a fresh install, logged out, with all permissions reset. That is how the reviewer sees the app.
FAQ
Can we require login if our app is only for existing customers?
Yes, if the app's purpose genuinely depends on an existing account, such as a client portal. Explain it in the review notes and provide demo credentials.
Does adding Apple's login button fix this rejection?
No. It may be required under a different guideline when you offer third-party logins, but forced login and data minimization issues remain separate.
How long does re-review take?
It varies. Many resubmissions are reviewed within a day or two, but plan launches with some buffer.
Will our app be removed if it is already live?
A rejection of an update does not remove the live version. The current version stays available while you fix the update.
If your app keeps bouncing back from review and you want someone to go through it the way a reviewer will, reach out to us and we will help you get it approved.