The Mobile App Consent SDK now reads each region's consent model from the server and, in opt in regions, applies the configured default category consent at app start without showing a banner, while regions with GDPR in scope, opt out regions and accounts with no default category are skipped. Three new iOS APIs (setAttOptOutLevel, setShowAttOptOutWindow, setAttOptOutLockCategories) control which categories are rejected and locked when a user declines Apple's App Tracking Transparency prompt, and a new getWebCookie() function returns consent cookie values on Android, iOS, Flutter and React Native.
Buyer relevance. This changes what the SDK decides on a user's behalf without any user action, so legal teams should confirm their per region consent models and default categories match their own legal position before the new behavior takes effect in their apps.