> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kontext.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance

> Viewability, IAB Tech Lab standards, privacy regulations and platform policies for the Video SDK.

Kontext is built to meet the standards publishers, advertisers and platform owners expect from a modern ad SDK. This page summarizes where the Video SDK stands.

## Viewability

The SDK measures every ad against the **MRC viewability standard**: at least 50 percent of the creative on screen for one continuous second, two seconds for video, counting only time in an active app. The verdict is reported for every impression and is part of what advertisers pay for.

[Open Measurement (OMID)](https://iabtechlab.com/standards/open-measurement-sdk/) certification for third-party verification is planned; ask [support@kontext.so](mailto:support@kontext.so) for the current status.

## IAB Tech Lab

* **VAST**: the SDK renders standard VAST video ads from every demand partner; your app never sees or parses VAST.
* **TCF v2.2**: the SDK reads the consent string automatically from the standard IAB storage every TCF-compatible CMP writes to (`UserDefaults` on iOS, `SharedPreferences` on Android). See [TCF & CMP](https://docs.kontext.so/video/guides/tcf-cmp.md).
* **app-ads.txt**: see [app-ads.txt](https://docs.kontext.so/video/guides/ads-txt.md).

## Privacy regulations

`KontextVideo.shared.regulatory` lets you forward consent and privacy signals to the ad server. All fields are optional; supply whichever applies to your viewer's jurisdiction.

* **GDPR (EU and UK)**: the TCF v2.2 consent string is collected automatically. You can also set `gdpr` and `gdprConsent` explicitly.
* **CCPA / CPRA (US)**: pass the [IAB US Privacy](https://iabtechlab.com/standards/ccpa/) string in `usPrivacy`.
* **GPP (Global Privacy Platform)**: pass the GPP string in `gpp` and the applicable section ids in `gppSid`.
* **COPPA (US)**: set `coppa` to `true` when the viewer is known to be under 13. The SDK and the ad server then treat the request as child-directed.

## Data handling

The SDK collects only what is needed to serve a relevant ad and report on it:

* The content metadata you pass in `Content` (the episode's title, genre, categories, series) and what you set in `User`: used for contextual targeting and frequency capping.
* A platform advertising identifier when the viewer granted permission (IDFA on iOS, GAID on Android), and on iOS the vendor identifier.
* A first-party install id generated by the SDK and kept in app storage.
* Your `publisherToken`.
* Standard device, app and network attributes (model, OS version, screen size, app bundle, connection type), and the content playhead at the time of a request.

Nothing else is collected. The full data processing terms are covered in our publisher agreement. For the third parties that process data on our behalf, see the [subprocessor list](https://docs.kontext.so/video/resources/subprocessors.md).

## Platform policies

* **Apple ATT (iOS 14+)**: the SDK reads the IDFA only after App Tracking Transparency authorization, which your app requests at the moment of its choice, or the SDK on request. Your app must declare `NSUserTrackingUsageDescription` in `Info.plist`. See [IFA & ATT](https://docs.kontext.so/video/guides/ifa.md).
* **SKAdNetwork (iOS)**: your app must list the `SKAdNetworkItems` we provide for install attribution to work. See [SKAdNetwork](https://docs.kontext.so/video/guides/skadnetwork.md).
* **Google AD\_ID permission (Android 13+)**: declared by the Android SDK through manifest merger.
* **Creative isolation**: advertisers' creatives render in a WebView the SDK owns, isolated from your app, and can open a URL only after a real tap.

For anything not covered here, contact [support@kontext.so](mailto:support@kontext.so).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.