What Google Analytics means for your app's privacy disclosures

Google Analytics is a product analytics tool. 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 Analytics actually does

The web property, still reached for in web apps and in the web views inside mobile apps.

What its job necessarily involves

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

• A client identifier stored on the device, which is what European regulators have spent years arguing about.
• IP derived location, and whatever you pass in as custom dimensions.

What to open and check in Google Analytics

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

• Whether the tag fires on page load or after the consent answer.
• The data retention setting on the property, which defaults to something longer than most policies claim.

Google Analytics does not need the tracking prompt

It measures your own app rather than following people into other companies' apps, so long as you have not turned on the advertising features. So Google Analytics 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 Analytics in Europe: nothing may run before consent

This is the part that gets missed, because the natural place to initialise an SDK is the moment the app launches, and the natural place to ask for consent is a screen that appears after it. Reading or writing anything on the device for product analytics needs agreement first, and that comes from the ePrivacy rules rather than the GDPR, so picking a different legal basis does not get you past it.

Google Analytics in California: probably not a sale

Google Analytics 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 Analytics on the App Store privacy labels

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

Google Analytics 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 Analytics

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 Analytics, it comes from Google, and it changes when they ship.

The rejection Google Analytics is usually behind

It runs on page load, before the consent banner has been answered, which several European authorities have ruled against directly.

What to put in the privacy policy about Google Analytics

• 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.