Android, iOS & React Native SDK

Sirdata CMP is a Consent Management Platform SDK for Android, iOS and React Native, registered with the IAB as CMP ID 92. It collects consent in a fully native interface — no WebView — and exposes every signal through the standard IAB in-app storage keys, so the IAB-compliant ad and analytics SDKs in your app read consent on their own, and built-in adapters forward it to several that do not.

	Android	iOS	React Native
Minimum version	API 23 (Android 6.0)	iOS 15.0	The Android and iOS minimums; 2.0.1 verified with React Native 0.86.3 (Expo SDK 57)
Consent UI	Jetpack Compose	SwiftUI	The native UI of each platform
Signal storage	SharedPreferences	NSUserDefaults	The native storage of each platform
Distribution	Maven Central	Swift Package Manager, CocoaPods	npm (@sirdata/react-native-cmp)

What it covers

• IAB TCF v2.2 — in-app CMP API (ping, getInAppTCData, addEventListener)

• IAB GPP — Global Privacy Platform, including the section command API

• US regime — a US opt-out screen, the US Privacy string and the GPP US sections

• Google Additional Consent and Google Consent Mode, derived from TCF purposes

• The web CMP's display cascade — capping windows, partial consent and cookie wall are decided by the SDK, not by your app

Before you start

You need a partner ID and a config ID from the Sirdata Console. They select the publisher configuration the SDK downloads at initialization: theme, texts, purposes, vendors, scope and capping. Changing the configuration takes effect without an app release.

Where to go next

• Android setup, iOS setup or React Native setup — install and initialize

• Sharing consent with vendor SDKs — how ad SDKs read the consent you collect

• Troubleshooting — the errors integrators actually hit

Sample apps

A full sample app for Android and for iOS is available on request from your Sirdata contact; there is no React Native sample. Both initialize the SDK, present the banner, expose Accept All / Reject All / Open Preferences, and display the live consent state (TC String, purposes, vendors) along with an IAB TCF ping test. Both also let you change the partner / config pair at runtime without rebuilding.