Skip to content

Consent, ads and tracking are different controls

A privacy screen asks for choices. An advertising component requests or displays an ad. An analytics component records activity. These components can interact, but removing one does not establish that the others stopped.

Follow the separate steps

Imagine choosing “no” in a consent interface. The app needs to communicate that choice to the relevant components. Whether collection then stops depends on how those components are wired. Conversely, hiding the interface says nothing by itself about what choice was saved or what the collectors do.

OneTrust and Didomi are consent-management services. Their presence should be explained by role. A configuration request, a consent receipt and an advertising-event upload are different operations even when they happen near the same screen.

The supported Skip consent screens implementations include their required privacy controls and complete the supported automatic flow without recording an automatic acceptance or rejection. They retain manual privacy controls and saved choices. Individual apps also have login or notification onboarding; the app page describes those differences.

Why ads can disappear while collection remains

An ad container can be hidden while a separate screen tracker still runs. An ad can also load from a service whose request carries an identifier. This is why the project has distinct ads, tracking and promotion controls with app-specific dependencies. Choose patches.

What this does not establish

No consent screen is a privacy indicator by itself. These technical findings are not legal assessments, and skipping a screen does not establish deletion of data already held by a provider. Read our evidence method for what was checked.