Skip to Content
Platform.Ontology

In-app consent platforms (TCF/CMP)

A consent screen the developer shows (in addition to the OS prompt) for EEA, UK and some US laws.

Works without askingAds and install trackingSDKs and measurementAndroid and iPhoneWhen the app opens

In one line

Can show an extra consent screen on top of the phone prompt

A consent screen the developer shows (in addition to the OS prompt) for EEA, UK and some US laws.

Recorded consent decides what ad SDKs may do. Since 2024 Google requires a certified CMP for ads in the EEA. On iOS it adds a second prompt beside ATT, which Italy called double consent.

What it can and can't do

What the user does: You see a Consent screen the first time you open the app, often in the EU or UK

It can

  • Ask you to say yes or no to ads, analytics and sharing
  • Store your answer on the phone
  • Tell its ad tools what you agreed to
  • Show again later if you change your mind

It cannot

  • Skip the screen when Google needs a certified one for EEA ads
  • Count as your consent if the answer is not recorded
  • Replace the phone's own prompt; on iPhone you may see two

On Android and iPhone

AndroidiPhone
StatusSupportedSupported
First versionNot availableNot available
Permission or entitlementNot listedNot listed
Protection levelnonenone
How access is grantedpromptprompt
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyGoogle EU user consent policy; Play FamiliesATT remains separate; privacy manifest tracking flag
APIGoogle UMP SDK, TCF 2.2 strings in app storageUMP SDK, CMP SDKs
NotesConsent string stored in SharedPreferences (IABTCF_).Italy's regulator treats ATT plus a CMP as double consent.

Data you get

What comes back: TCF consent string
Shape: string
How often: stored locally, refreshed yearly

FieldTypeUnitRangePrecision
IABTCF_TCStringstringNoneNot listedNot listed

Technical limits

  • Two prompts on iOS
  • Consent must precede SDK init in EEA

The story

What it is

The extra consent screen an app shows, for privacy laws, on top of the phone's own prompt.

For you

You see a screen asking you to accept or manage cookies and ad choices in an app, often before the app opens. Your answer is saved and sent to ad partners.

For makers

Laws like GDPR require consent before personal ad data is used. Makers use a CMP so ad SDKs only do what the saved choice allows, and Google requires it for ads in the EEA.

Where you see it

TypeExampleApps
newsA news app asks you to consent to personalized ads before showing articles.BBC, The Guardian
gamesA free game shows a consent form at first launch, then loads ads based on your answer.Candy Crush, Subway Surfers
adsAn ad SDK reads the saved consent string and serves non personalized ads when you say no.Google AdMob, AppLovin
socialA social app offers separate toggles for ads, analytics and personalization.Pinterest
shoppingA retailer stores your consent so it can prove it asked, for audits.Zalando
analyticsA product team measures how many users accept and tunes the wording.None named

Risks

  • Dark pattern buttons
  • Second prompt next to ATT

Android and iPhone in short

  • Android: Android has no system consent screen. Apps use a CMP.
  • iPhone: On iOS the CMP appears beside the ATT prompt, which Apple allows if it is not misleading.

Good uses and abuse

Legitimate uses

  • Legal basis for ads data

Known abuse

  • Dark patterns

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2024-01, Android Google policy: Certified CMP required for ads in EEA and UK (Jan 2024)
  • 2025-12, iPhone iOS 26: Italy fines Apple over double consent

Same idea on the web

Sources

How well checked: Based on official documentation.

On this page