Summary
Guideline 5.1.2 commonly points to how the app uses collected data, shares it, or gives users control after collection.
App Store App Review issue
App Store Guideline 5.1.2 rejection
Guideline 5.1.2 commonly points to how the app uses collected data, shares it, or gives users control after collection.
app store guideline 5.1.2guideline 5.1.2 rejectionapple data use rejection
Fix App Store review issues before the next submission
Use LogicSpring to run a free precheck, regenerate the right policy or disclosure pack, and shorten the loop from rejection notice to resubmission.
What this means
Apple sees a problem in how your app uses data after it is collected, including sharing, retention, or secondary use.
This may overlap with account deletion, data access, data export, or third-party sharing explanations.
The rejection usually means reviewers do not believe the app gives users enough transparency or control.
Common causes
- The policy is vague about how data is shared with vendors, affiliates, or analytics tools.
- User controls for deletion, consent withdrawal, or communication preferences are missing or hard to find.
- The data use described in the app and policy seems broader than what the feature actually needs.
Step-by-step fix
- Step 1
Rewrite the policy sections covering sharing, retention, deletion, and user rights in concrete language.
- Step 2
Add or clarify in-app controls for account deletion or privacy choices where required.
- Step 3
Document in review notes where Apple can test these controls and how the updated policy maps to them.
What to update
- Privacy Policy sharing and retention sections
- Account settings or deletion flows
- Reviewer notes
- Vendor disclosure copy
How LogicSpring helps
- LogicSpring helps teams regenerate the policy sections reviewers actually compare for data-use and user-rights issues.
- Use precheck to spot missing deletion or disclosure surfaces before the next build goes out.
- Store vendor and sharing details once, then reuse them across policy and export materials.
FAQ
Can I resubmit to App Store without changing the binary?
Only if the issue is purely metadata or disclosure copy. If the current build behavior still conflicts with the policy, permissions, or SDK inventory, you usually need a new build.
What evidence should I prepare before resubmitting?
Prepare the updated public policy URL, the exact store fields you changed, screenshots for permission or disclosure flows where relevant, and a short reviewer note explaining what changed and why it now matches the app.
Should the privacy policy, store form, and in-app disclosure all match?
Yes. Review teams compare these surfaces together. If one says you collect or disclose something and another says you do not, the mismatch itself often becomes the next rejection.