> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/mobile-apps-native-sdk/mobile-sdk.md).

# Android & iOS SDK

Sirdata CMP is a Consent Management Platform SDK for **Android** and **iOS**, 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 ad and analytics SDKs already in your app read consent without a line of integration code.

|                 | Android              | iOS                              |
| --------------- | -------------------- | -------------------------------- |
| Minimum version | API 24 (Android 7.0) | iOS 14.0                         |
| Consent UI      | Jetpack Compose      | SwiftUI                          |
| Signal storage  | `SharedPreferences`  | `NSUserDefaults`                 |
| Distribution    | Maven Central        | Swift Package Manager, CocoaPods |

## What it covers

* **IAB TCF v2.2** — in-app CMP API (`ping`, `getInAppTCData`, `addEventListener`)
* **IAB GPP** — Global Privacy Platform, including the section command API
* **CCPA / USP** — US Privacy string and "Do Not Sell" opt-out
* **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 dashboard](https://dashboard.sirdata.com). 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**](/en/mobile-apps-native-sdk/mobile-sdk/setup.md) or [**iOS setup**](/en/mobile-apps-native-sdk/mobile-sdk/setup-1.md) — install and initialize
* [**Sharing consent with vendor SDKs**](/en/mobile-apps-native-sdk/mobile-sdk/sharing-consent.md) — how ad SDKs read the consent you collect
* [**Troubleshooting**](/en/mobile-apps-native-sdk/mobile-sdk/troubleshooting.md) — the errors integrators actually hit

## Sample apps

A full sample app per platform is available on request from your Sirdata contact. 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cmp.docs.sirdata.net/en/mobile-apps-native-sdk/mobile-sdk.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.