Skip to content

OneTrust: what happens behind a privacy preference screen?

OneTrust provides a consent management platform, often shortened to CMP. Its mobile SDK supplies a banner, a preference centre and vendor lists. These help an app ask for and manage choices about data use. A privacy interface can have legitimate network requirements; its presence is not proof that every request is behavioural tracking. OneTrust SDK reference.

Consent is also a state consumed by other app code. A callback is code run when something changes, such as a consent choice. Whether a choice actually gates collection depends on the connected collectors, not just the appearance of the banner.

Can managing choices itself exchange data?

OneTrust's documented save/log API supports app and SDK information, a consent string and optional identity or cross-device fields. A consent string is an encoded representation of choices; it is not encryption that makes the information secret. These API capabilities are not proof that Buienradar invokes that exact route or enables identity synchronisation. Save and log consent API.

Hypothetical example: a privacy screen fetches the current vendor list, remembers a choice and notifies an analytics library. Those are three different operations. Hiding the screen alone need not stop the library, while blocking the whole consent service may prevent you changing a choice later.

What did we find in Buienradar?

In Buienradar 7.4.8, OneTrust configuration remains at startup, with mobile-data.onetrust.io and geolocation.1trust.app identified as retained service destinations. The audit also traces a consent callback that grants Firebase analytics storage. This is why the tracking patch covers analytics collection and re-enablement rather than relying on a hidden banner. A geolocation-named host alone does not establish transmission of GPS coordinates. Pinned Buienradar audit.

What does skipping the screen mean here?

Skip consent screens bypasses the automatic Pay-or-OK and OneTrust displays. It includes the tracking and ad controls, writes neither acceptance nor rejection, and keeps manual Privacy settings available. The audit says unanswered OneTrust groups are read as not granted by the app's cache.

That is a specific patch behaviour, not a substitute for examining every connected sender or a legal assessment of consent. Functional configuration and ordinary network metadata remain; no decrypted traffic capture was added for this documentation.

Evidence reviewed 28 October 2026. Continue with consent, Firebase and methodology.