Skip to content

Android SDK: Data and privacy

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.

Only the pixels of the ad view itself, when the ad is fully visible, unobscured and in a focused window. The SDK never captures a window marked FLAG_SECURE, 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 (Android, SDK 0.3.0), when the app’s full-screen capture switch is on. Then the SDK uploads one image of Google’s ad window for that show, and nothing else of your app: never your own activities, dialogs or the screen. A full-screen ad that your app did not track is never captured. By tracking, you assert that your app and its libraries draw nothing into Google’s ad activity; the SDK cannot check this, so anything drawn there could appear in the image. Ad80.register never uploads a full-screen image. See Full-screen ads (opt-in).

Uploads go over HTTPS to the endpoint in your app’s configuration (AndroidManifest.xml), authenticated with the app’s upload key. A batch contains:

FieldContent
appIdYour app’s package name (applicationId).
sdkVersion, protocolVersionSDK and protocol version.
batchId, observationIdGenerated identifiers of the batch and of each observation, used to avoid duplicates.
droppedSinceLastBatchHow many observations were dropped without being delivered (for example when the queue was full).
placementIdThe placement id, for example MainActivity/banner_top.
mediationPlatformFor example admob.
servingNetworkThe 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.responseIdThe AdMob response id, when available.
creativeThe content hash, width, height and screen density, and the PNG image (only the first time this image is sent).
triggerWhy it was sent: a new ad, changed pixels, or a new response id over the same pixels.
capturedAtEpochMsWhen the ad was captured.
captureThe capture method and the ad view’s size in pixels (for a full-screen ad, the size of Google’s ad window).
fullScreenOnly 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.

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).

  • 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.

The queue lives in the app’s no-backup storage (noBackupFilesDir, folder ad80), so it is not included in device backups. 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.

The SDK uses two background threads of its own: one for its engine, network and disk work, and one for copying pixels. The main thread only checks visibility and schedules captures.

  • It never replaces or wraps your ad listeners (setAdListener, setOnPaidEventListener) or the view hierarchy listener.
  • It never changes your ad request or your ad views.
  • It never uses reflection into Google Mobile Ads internals, bytecode instrumentation or accessibility services.

See also Security and privacy.