App Store Reject

Guideline 5.1.1

Guideline 5.1.1(v) - Privacy: Requiring Login Without Account-Based Features

Medium RiskMedium DifficultyTypical Fix: 2-8 hours0 Reports
Also known as:App requires login to access features that are not account-basedApp forces registration before allowing access to contentUsers must create an account to access core functionality that does not require personalizationApp gates content behind login without clear justificationNon-account-based features are inaccessible without registration

Our Take

Apple is rejecting your app because it requires users to create an account or log in to access features that do not require an account. Under guideline 5.1.1(v), apps should not force registration unless the app's core functionality genuinely depends on account-based features like storing user-specific data, accessing personalized content, or social features. This rejection commonly hits utility apps, content consumption apps, and tools that gate all functionality behind a login wall without a clear reason. Apple's position is that users should be able to evaluate and use an app's basic features without surrendering personal information first. If your app is a flashlight, calculator, or static content viewer, forcing login violates this principle. The fastest compliant path is to allow users to access core functionality without an account, and offer login as optional for enhanced features (e.g., syncing, personalization, social). If your app genuinely requires an account (e.g., messaging app, banking app, enterprise app), explain this clearly in the review notes with specific reasons why offline or anonymous access is not feasible.

Resolution Guide

01

**Identify account-dependent features** — List every feature and determine which ones genuinely require a user account (syncing, saving preferences, social interaction) vs. which can work without one (content browsing, tools, calculators).


02

**Implement guest access** — Allow users to access non-account features without logging in. Add a 'Continue as Guest' or 'Skip' button on the login screen.


03

**Gate only what's necessary** — Keep login required only for features that truly need it. Show a login prompt when a guest user tries to access an account-dependent feature.


04

**Explain account necessity in review notes** — If your app's core functionality genuinely requires an account, provide a detailed explanation in the App Review Notes field. Explain what server-side data is needed and why the experience cannot function anonymously.


05

**Provide a demo account** — If login is justified, provide demo credentials in the review notes so Apple can test the app.

Prevention

  • Default to guest access, with login as an enhancement
  • Never gate static content behind login
  • Always provide demo credentials in review notes if login is required

    • Example Rejection Email

    From:Apple App Review Team
    Subject:Guideline 5.1.1 - Guideline 5.1.1(v) - Privacy: Requiring
    Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage Your app requires users to register or log in to access features that are not account-based. Specifically, the app requires users to create an account before they can access the app's content, but the app's core features do not appear to require user accounts. Apps may not require user registration to access content and features that are not associated specifically with the user. Next Steps: Please revise your app to allow users to access the app's non-account-based content and features without requiring them to register or log in.

    Consider Appealing

    Appeal if your app's core functionality genuinely depends on user accounts (e.g., social networking, banking, enterprise). Provide a clear, specific explanation of why anonymous access is not feasible. For content apps, an appeal is unlikely to succeed — implement guest access instead.

    Generate Appeal

    Before & After

    Before — Rejected

    App launches to a login screen with no way to proceed without creating an account; all content is behind the login wall

    After — Approved

    App launches with a 'Continue as Guest' option; content browsing and core tools are accessible without login; account creation is prompted only when user tries to save favorites or sync data

    What changed: Apple wants users to evaluate the app before committing to account creation. Gate only features that genuinely require server-side user data.

    Community Solutions · 0

    Sign in to share your solution.

    More Guideline 5 (Legal) rejections

    View all Guideline 5 rejections