These are Encore’s recommended answers for the data the Encore SDK collects. Your final answers also cover your own app’s data. React Native and Flutter apps use the iOS and Android answers below for each store.
What the SDK sends
In the Sent as column, consent keys, advertising ID keys, andosVersion are request attributes. Keys that start with sdk_offer_presentation_success are properties of the show event. Every other key is in the request context.
Device model, OS version, device type, connection type, and low power mode describe the device, not the user. The SDK sends them with every request, also when personalization is off or the user refuses consent. On Web, the SDK skips the detailed browser hints after any refusal.
The SDK reads consent strings only where your consent tool already stores them: the standard IAB (Interactive Advertising Bureau) keys in
UserDefaults on iOS and in the default SharedPreferences on Android, and the __tcfapi, __gpp, and __uspapi APIs on Web. Encore uses them to honor the user’s choice. After a refusal, such as a Global Privacy Control signal or personalization turned off, Encore uses nothing it knows about that user: it chooses offers from the request alone and stores no user profile data from those requests.
App Store privacy answers
The SDK’s privacy manifest (PrivacyInfo.xcprivacy) already declares each data type below, so Xcode’s privacy report lists them. Check that your App Store Connect answers include these rows:
These rows are linked to the user because Encore stores each value with the app user ID that the same request sends. The SDK’s manifest already declares that user ID as linked.
Keep Used for tracking set to No. The SDK reads no IDFA and shows no App Tracking Transparency prompt, and its manifest declares no tracking domains. Time zone and consent strings are device settings, not a separate App Store data type, so they add no row.
Google Play Data safety answers
Check that your Data safety form includes these rows:
For each row except Device or other IDs, answer No to Is this data processed ephemerally?: Encore stores these values with the app user ID that the same request sends.
The Device or other IDs row has its own answer. Encore does not store the advertising ID: the serve record keeps only whether one was present. The raw ID goes only into the bid request that Encore sends to an ad exchange, as
device.ifa. For this row, answer Yes to Is this data processed ephemerally?, and declare the advertising ID as shared, because the bid request passes it to a third party.
Time zone and consent signals are device settings, not a separate Data safety data type, so they add no row.
The SDK’s manifest adds the ACCESS_NETWORK_STATE permission to read the connection type. It is a normal permission: Android grants it at install, with no prompt, and it needs no Data safety answer. If your app removes it from the merged manifest, the SDK sends no connection type.
Advertising ID on Android
By default, the SDK does not read the advertising ID. With the default, do not declare the advertising ID as collected by Encore in your Data safety form: the Device or other IDs row in the Data safety table does not apply. When the SDK does read the advertising ID, all of these are true:- Your app’s merged manifest declares
com.google.android.gms.permission.AD_ID. Your own manifest does not have to declare it: the Google Play services ads identifier library adds it to the merged manifest, and apps that use Firebase or AdMob often include that library. - Your app includes the Google Play services ads identifier library.
- Device identifiers are enabled for your app. They are off by default, and Encore turns them on only after you agree to it. If you have not agreed to it with Encore, this condition is false.
- Your app’s store listing is not for children.
- Personalization is not off for this user.
AndroidManifest.xml
tools prefix needs xmlns:tools="http://schemas.android.com/tools" on the <manifest> element. Removing the permission also stops other libraries in your app from reading the advertising ID.
When these conditions hold and the user limits ad tracking, the SDK sends the limit flag and no ID. For apps whose store listing is for children, the SDK reads no device identifiers and serves contextual offers only.
Web
Browsers have no store privacy form. The SDK honors the Global Privacy Control signal and the consent APIs of the Transparency and Consent Framework (TCF), the Global Privacy Platform (GPP), and the US Privacy API (__uspapi) on your page. If your privacy policy lists the data you send to vendors, add the Web rows from What the SDK sends.