Social login and Sign in with Apple: the App Store rule teams miss
Apps using third-party social login for their main account must also offer a privacy-preserving login option under App Review Guideline 4.8. The criteria, exceptions and planning notes.
If your app's signup screen offers "Continue with Google" or "Continue with Facebook" and nothing else, you may have an App Store problem: unless one of its exceptions covers your app, App Review Guideline 4.8 (Login services) requires apps using third-party or social login for their main account to also offer a privacy-preserving alternative. Teams discover this at review time - the worst moment to learn it.
This guide explains the current requirement as published in Apple's guidelines, checked against the live text on 19 November 2026.
What guideline 4.8 actually requires
The current text: apps that use a third-party or social login service - the guideline names Facebook Login, Google Sign-In, Log in with X, Sign In with LinkedIn, Login with Amazon and WeChat Login as examples - to set up or authenticate the user's primary account must also offer, as an equivalent option, another login service with three features: it limits data collection to the user's name and email address; it allows users to keep their email address private while setting up the account; and it does not collect interactions with your app for advertising purposes without consent. A "primary account" is the account the user establishes with your app to identify themselves, sign in and access your features.
Sign in with Apple is Apple's own service built to exactly these three features, and Apple introduced the requirement alongside it in September 2019 - which is why the rule is often summarized as "you must offer Sign in with Apple". The guideline itself is written provider-neutrally: any login service meeting the three features satisfies it. In practice, Sign in with Apple is the option iOS apps overwhelmingly implement.
The exceptions, precisely
Another login service is not required when:
- Your app exclusively uses your company's own account setup and sign-in systems.
- Your app is an alternative app marketplace, or is distributed from one, using a marketplace-specific login for account, download and commerce features.
- Your app is an education, enterprise or business app that requires sign-in with an existing education or enterprise account.
- Your app uses a government or industry-backed citizen identification system or electronic ID to authenticate users.
- Your app is a client for a specific third-party service, and users must sign in to their mail, social media or other third-party account directly to access their content.
Planning login for a new app
- Decide your identity model first. Your own account system alone is exempt; add any third-party social login and the equivalent-option requirement applies.
- Budget for the native providers. Sign in with Apple on iOS; Google sign-in is the native expectation on Android. Each is a small but real integration and testing surface.
- Account linking is the hard part. The same person arriving via Google on Android and Apple on iOS should land in one account; design for email-matching and linking from the start.
- Apple's private relay. Users can hide their real email behind an Apple-generated relay address - one of the guideline's required features in action. Your systems must treat that address as a first-class email; it forwards to the user and can stop working if they withdraw it.
- Don't forget deletion. Offering account creation also means supporting in-app account deletion under App Store rules - plan the data side, which our GDPR basics guide covers from the privacy angle.
Sources
- Apple App Review Guidelines, 4.8 Login services (verified against the live text on 19 November 2026): https://developer.apple.com/app-store/review/guidelines/
- Apple Developer News, New Guidelines for Sign in with Apple (September 12, 2019, historical introduction): https://developer.apple.com/news/?id=09122019b
Drafted with AI assistance from these sources. Review guidelines change; verify the current 4.8 text before submitting an app that uses third-party sign-in.