iOS SDK: Data and privacy
When the SDK sends anything
Section titled “When the SDK sends anything”The SDK makes no network request of any kind until your app has granted consent with Ad80.setConsent(true)
and enabled the SDK. Revoking consent or disabling the SDK stops requests at once and deletes the queue.
What is captured
Section titled “What is captured”Only the pixels of the ad view itself, when the ad is fully visible, unobscured and its scene is active. The SDK draws the ad view into an image and never captures your app’s own content outside the ad view. Images are encoded as PNG.
The one exception is a full-screen ad that your app has opted in with Ad80.trackFullScreenAd, when the app’s
full-screen capture switch is on. Then the SDK uploads one image of Google’s full-screen ad (the root view of its view
controller) for that show, and nothing else of your app. A full-screen ad that your app did not track is never
captured. By tracking, you assert that your app and its libraries add nothing to Google’s ad view; the SDK cannot
inspect what is inside it, so anything added there, or drawn over the ad, could appear in the image. Video areas can
come out black. See Full-screen ads (opt-in).
What is uploaded
Section titled “What is uploaded”Uploads go over HTTPS to the endpoint in your app’s configuration (Info.plist), authenticated with the app’s upload key. A batch contains:
| Field | Content |
|---|---|
appId | Your app’s bundle identifier. |
sdkVersion, protocolVersion | SDK and protocol version. |
batchId, observationId | Generated identifiers of the batch and of each observation, used to avoid duplicates. |
droppedSinceLastBatch | How many observations were dropped without being delivered (for example when the queue was full). |
placementId | The placement id, for example FeedViewController/banner_top. |
mediationPlatform | For example admob. |
servingNetwork | The network id and the raw attribution values from ResponseInfo: adapter class name, ad source name and id, ad source instance name and id, mediation adapter class name. |
admob.responseId | The AdMob response id, when available. |
creative | The content hash, width, height and screen density, and the PNG image (only the first time this image is sent). |
trigger | Why it was sent: a new ad, changed pixels, or a new response id over the same pixels. |
capturedAtEpochMs | When the ad was captured. |
capture | The capture method and the ad view’s size in pixels (for a full-screen ad, the size of Google’s ad window). |
fullScreen | Only for a tracked full-screen ad: its format (INTERSTITIAL, REWARDED, REWARDED_INTERSTITIAL or APP_OPEN), its ad unit id, how it was associated (PUBLISHER_TRACKED, meaning your app said so) and whether the picture had settled. |
On iOS the capture method is UIKIT_DRAW_HIERARCHY for banner and native ads. For a tracked full-screen ad the
protocol’s shared value PIXELCOPY_AD_WINDOW is sent; on iOS it means the tracked ad’s own content at full
resolution.
The upload contains no advertising id, no device identifier, no user identifier, no location and none of your app’s screen content outside the ad (for a full-screen ad, outside Google’s ad window).
How often
Section titled “How often”- Each distinct image is uploaded once per network per 24 hours. After that, the same ad in the same placement is sent at most once per 24 hours as metadata only.
- An ad whose AdMob response id changes over the same pixels is sent once more as metadata only.
- Uploads are batched (at most 10 observations and 1 MiB per request), with at most one request in flight.
- If a request fails it is retried with growing waits (from 2 seconds up to 5 minutes, honouring
Retry-After), at most 6 times per batch and at most 12 failed attempts per hour.
On the device
Section titled “On the device”The queue lives in Application Support/dev.ad80/ inside the app, which the SDK creates excluded from backups, with
file protection completeUntilFirstUserAuthentication. It holds at most 50 observations within about 5 MiB; when it
is full the oldest observations are dropped first and counted in droppedSinceLastBatch. The SDK also keeps the last
remote configuration and its de-duplication keys there.
Threads and performance
Section titled “Threads and performance”Drawing the ad view into an image happens on the main thread, once the ad has passed the visibility checks (for a full-screen ad on an iPhone 13, a full-resolution capture took 21 to 28 ms of main-thread time at the median in our measurements). Conversion, hashing, PNG encoding, network and disk work run off the main thread.
What the SDK never does
Section titled “What the SDK never does”- It never loads ads, never records impressions, and never replaces or wraps your ad delegates (it never sets
fullScreenContentDelegate). - It never changes your ad requests or your ad views, and it never presents or dismisses an ad.
- The Google Mobile Ads integration uses only Google’s typed public API: no swizzling, KVO, KVC, associated objects or private API. The one exception is the exact class-name comparison for Google’s full-screen view controller.
Privacy manifest (iOS)
Section titled “Privacy manifest (iOS)”The Ad80 library ships an Apple privacy manifest, PrivacyInfo.xcprivacy. It declares:
| Key | Value |
|---|---|
NSPrivacyTracking | false |
NSPrivacyTrackingDomains | None |
NSPrivacyCollectedDataTypes | One entry: NSPrivacyCollectedDataTypeAdvertisingData (the ad creative image), not linked to the user (NSPrivacyCollectedDataTypeLinked false), not used for tracking (NSPrivacyCollectedDataTypeTracking false), purpose NSPrivacyCollectedDataTypePurposeAnalytics. |
NSPrivacyAccessedAPITypes | None: the SDK uses no Required Reason APIs. |
The manifest describes the SDK only. Your app’s own privacy manifest and your App Store privacy answers must still cover what your app uploads; the SDK’s manifest does not replace them.
See also Security and privacy.