What Google Sign-In means for your app's privacy disclosures

Google Sign-In is an accounts and backend service. What it involves, whether it needs the tracking prompt, what goes on the App Store labels and the Play Data safety form, and the rejection it is usually behind.

Updated 2026-09-18 · Written from the same rules terms.gg uses to generate documents

What Google Sign-In actually does

The Google identity button, often added because Android users expect it.

What its job necessarily involves

These follow from what the thing is for, so they are true whichever version you installed:

• The profile scopes you request, which is a decision you make and should be able to justify.
• A stable identifier linking the person to their Google account.

What to open and check in Google Sign-In

The settings below decide what the honest answer on the forms is, and they are specific to this SDK rather than to its category:

• The exact scopes requested, which tend to widen during development and never narrow again.

Google Sign-In does not need the tracking prompt

Signing someone in is the service they asked for. So Google Sign-In does not on its own require App Tracking Transparency. That is a statement about this SDK, not about your app: add one ad network or one attribution tool and the prompt applies to everything.

Google Sign-In in Europe: runs on necessity

You cannot deliver the service without it, so Google Sign-In generally rests on the contract with your user rather than on consent. Say plainly in the policy that it is a processor, what it does, and where it runs.

Google Sign-In in California: probably not a sale

Google Sign-In does its job for you rather than for its own commercial purposes, which normally keeps it a service provider rather than a sale. That depends on your contract saying so, and the standard terms usually do.

Google Sign-In on the App Store privacy labels

Apple asks what your app collects, and your app collects whatever its SDKs collect. Google Sign-In is generally declared under App Functionality, alongside whatever the rest of your app does for its own reasons.

Google Sign-In on the Google Play Data safety form

The form asks two things the labels do not: whether data is shared with anyone else, and whether it is encrypted in transit. For this SDK the honest answer is usually collected but not shared, because it processes on your behalf.

Check Google's own privacy manifest for Google Sign-In

Since 2024 Apple has required third-party SDKs on its list to ship a signed privacy manifest declaring what they collect and which sensitive APIs they use, and your app's combined manifest is built from them. That file is the authoritative answer for Google Sign-In, it comes from Google, and it changes when they ship.

The rejection Google Sign-In is usually behind

Scopes were widened during development for convenience and never narrowed before release.

What to put in the privacy policy about Google Sign-In

• Google named as a processor or a recipient, not hidden behind "our partners".
• What it is for, in a sentence someone would understand without knowing what an SDK is.
• Where it runs, and what makes a transfer outside your region lawful.
• How long the data is kept, which is a question the vendor documents and most policies skip.
• That it processes on your instructions rather than for its own purposes.

Keeping it true after launch

A legal page stops being true the moment the product moves past it, usually by adding a payment provider, an analytics SDK or a sign-in. No store re-checks your pages against your build, so the drift is yours to notice.

• Re-read it whenever you add a dependency that sees user data.
• Re-check what loads on the page after any change: the cookie notice and the policy have to agree.
• Keep the URL stable. Changing where a policy lives breaks every listing that points at it.