Français
Español
DeutschMost ad SDKs want an advertising ID. This one asks for one permission.
Appaloo doesn't read the advertising ID, any device identifier, or details about the device it runs on. You won't need a tracking prompt because of it, and it adds one row to your Data Safety form.
What the SDK needs from your app
A typical ad SDK brings an advertising ID, device fingerprinting and a consent flow you have to maintain. Here's the permissions block of your manifest with each.
- Reads the advertising ID on both stores
- Ships a device and environment fingerprint
- Personalised ads, so an ATT prompt to show
- A consent platform to wire up for the EU
- A Data Safety form with identifiers on it
- No IDFA, no AAID, no vendor identifier
- No model, OS, locale, screen or custom user agent
- Non-personalised ads, so no ATT prompt
- No consent SDK to integrate on our behalf
- One row on the Data Safety form
Targeting is based on the app the ad appears in.
A reasonable question: if the network collects nothing about users, how do the ads reach the right people? Appaloo matches each ad to the app it appears in. A puzzle game gets shown inside other puzzle games, on the same store and in the same language.
None of that requires following anyone between apps. Appaloo knows what the host app is because its developer told us when they added it.
What you declare to each store
Both stores ask you to declare what every SDK in your app collects. This is everything Appaloo adds to each.
What you can skip
A tracking prompt
Appaloo doesn't need an ATT dialog, so there's nothing to design, translate or time.
A second consent flow
There's no consent SDK to embed for personalised ads and no vendor list to maintain. If you already run a consent manager, Appaloo fits into it.
Disclosure guesswork
It's one row on Play and one entry on Apple, and both are accurate. You don't have to work out what a mediation stack collects further down the line.
Data deletion requests
There's no per-user record to delete, because the SDK doesn't store an identifier that could tie data to a user.
Common questions
Does the SDK use the IDFA or the Google Advertising ID?
Neither. The Android SDK doesn't depend on play-services-ads-identifier and doesn't declare the AD_ID permission. The iOS SDK doesn't read the advertising identifier or identifierForVendor, and doesn't create a persistent device ID of its own.
Will my app have to show an App Tracking Transparency prompt?
Not because of Appaloo. The SDK has no cross-app identifier and the ads aren't personalised, so it doesn't count as tracking under Apple's definition. Its bundled privacy manifest sets NSPrivacyTracking to false, and Xcode adds that to your app's privacy report when you build.
What do I put on the Google Play Data Safety form?
One row: under App activity, choose App interactions, and mark it as collected and encrypted in transit. Don't declare an advertising ID or add the AD_ID permission for the SDK. It only asks for INTERNET.
The SDK docs have the full disclosure reference, including the exact Data Safety selections.
Advertise your app without tracking anyone.
Add your app and you can serve your first ad today.