How to Resolve App Store Guideline 5.1.1 – Legal – Privacy – Data Collection and Storage

Introduction

Apple’s App Store Guideline 5.1.1 – Legal – Privacy – Data Collection and Storage prohibits requiring personal information that isn’t directly relevant to an app’s core functionality. If your registration form mandates City, State, or Birthdate—and these aren’t essential—you’ll see a rejection like:

Required fields not relevant to core functionality: City, State, and Birthdate

This guide explains how to remove or optionalize those fields so Apple can approve your app without submitting a new build.

How to Resolve it?

Remove or Make Fields Optional

Locate the Registration Form

1. In your codebase or plugin settings, find the form definition that includes City, State, and Birthdate.
   

Remove Non-Essential Fields

1. If these fields aren’t needed for any feature (e.g., shipping, age verification), delete them from the form and backend validation.
   

Or Mark Fields as Optional

1. If you still need this data (for personalization), change each field’s validation to optional.
2. Update UI labels to read “City (optional),” “State (optional),” and “Birthdate (optional).”
   

Deploy and Test

1. Push changes to staging, register a new account without filling those fields, and confirm successful signup.
   

Respond in App Store Connect

1. Open the Resolution Center for your rejected submission.
2. Reply with a brief note, for example:
   
   “We have removed/made optional the non-essential registration fields (City, State, Birthdate) as requested.”
   
3. Submit the response—no new binary upload is required for this metadata change.
   

Do I need to generate a new build?

No, there’s no need to generate a new build.”

Troubleshooting and FAQs

Q: Do I need to update my privacy policy?
A: Only if it mentions collecting City, State, or Birthdate. Otherwise, no update is necessary.

Q: My registration form comes from a third-party plugin—how do I adjust it?
A: Look for plugin settings to make fields optional or use available filters/hooks to remove or alter the field requirements.

Q: Will this affect existing users?
A: No. These changes only apply to new registrations; existing accounts retain their data and login flows.