Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Apple rejected my app for offering Google or Facebook login only

Short answer

Apple's guideline 4.8 says an app that uses a third-party or social login for the main account must also offer an equivalent login that limits collection to name and email, lets users keep their email private, and does not collect app interactions for ads without consent.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The rejection cites guideline 4.8 Login Services.
  • My app only offers Google, Facebook or similar login.
  • I removed the social login and now users cannot sign in.
  • I am not sure whether email and password counts.
  • Existing users must keep their accounts after the change.

Why does this happen?

  1. A social login is the only way to sign in

    Guideline 4.8 applies to apps that use a third-party or social login to set up or authenticate the user's primary account.

  2. The equivalent option has three requirements

    It must limit data collection to name and email, let users keep the email private during setup, and not collect interactions for advertising without consent.

  3. Own accounts are not mentioned

    The guideline text I read talks about third-party or social login. Check your rejection message for exactly what applies to your app.

  4. The change touches users and data

    Adding a login method means linking accounts, avoiding duplicates and handling private relay emails.

What can I do about it today?

  1. Read which exact point is citedApple's message tells you what it looks at. Do not assume the whole login must change.
  2. Do not remove existing loginsKeep what works. You may need to add an option, not take one away.
  3. Ask for a plan before buildingWhat is added, how existing accounts are linked and what changes on the server.
  4. Tell users nothing yetA mistaken announcement can confuse customers.
  5. Plan the account deletion sideIf the app supports account creation, in-app deletion is also required. See the account deletion page.

When should I bring someone in?

  • Users already have accounts that must be merged.
  • The back end identifies users only by email.
  • The rejection repeats after a fix.

How do I handle it?

  1. Check what the app collects at sign-inI list the data taken from each login method.
  2. Add an equivalent login that meets all three pointsI choose the option that satisfies them for your app, for example Sign in with Apple if it fits.
  3. Link, not duplicateI match new sign-ins to existing accounts safely and handle hidden email addresses.
  4. Test the whole login on a clean installIncluding sign-out, return and deletion.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is email and password login enough?

Guideline 4.8 as I read it concerns third-party or social login. Confirm the exact reason in your message.

Will existing users lose their account?

They should not if accounts are linked carefully.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.