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

# Store Privacy Disclosures

> The App Store privacy answers and Google Play Data safety answers to update when your app moves to the Encore SDK release that reads moments and device signals.

The 2.7.0 SDK release sends new data with each offer request: the moment your app passes, a few device facts, and the privacy signals already on the device. Update your store privacy answers when you ship that release. Nothing on iOS reads the advertising identifier (IDFA), and by default the Android SDK does not read the advertising ID either.

> [!WARNING]
>
> When you upgrade to SDK 2.7.0, or to the Flutter or React Native release that requires native SDK 2.7.0, update your App Store privacy answers and your Google Play Data safety form with the rows on this page.

> [!NOTE]
>
> 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, and `osVersion` 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.

| Data | Sent as | iOS | Android | Web | Sent when |
| - | - | - | - | - | - |
| Moment type, name, and value | `moment.event`, `moment.label`, `moment.value` on the request, `sdk_offer_presentation_success.moment_event` and `sdk_offer_presentation_success.moment_label` on the show | Yes | Yes | Yes | Your app passes a moment ([Tell Encore the Moment](https://docs.encorekit.com/publishers/guides/moments.md)) |
| Purchase amount and currency | `moment.value`, `moment.currency` | Yes | Yes | Yes | Your app passes a purchase moment |
| Device model | `device.model` | Yes | Yes | No | Every request |
| Operating system version | `osVersion` | Yes | Yes | iOS and Android browsers only, when the browser reports it | Every request |
| Device type (phone, tablet, or desktop) | `device.type` | Yes | Yes | Yes | Every request |
| Connection type (Wi-Fi, cellular) | `device.connectionType` | Yes | Yes | Chrome on Android only | Every request |
| Low power mode or battery saver | `device.lowPowerMode` | Yes | Yes | No | Only while it is on |
| Time zone | `timeZone` | Yes | Yes | Yes | Every request |
| Your app's version | `appVersion` | Yes | Yes | When you pass it | Every request |
| Time the last offers took to draw | `offersRenderMs` | Yes | Yes | Yes | After the first presentation |
| Round-trip time of the last offer request | `device.networkRttMs` | Yes | Yes | Yes | After the first request |
| Which Encore copy the headline uses | `headlineCopySource` on the request, `sdk_offer_presentation_success.headline_copy_source` on the show | Yes | Yes | Yes | Every request and every show |
| The request a show's offer list came from | `sdk_offer_presentation_success.prefetch_request_id` | Yes | Yes | Yes | A show that uses a list fetched earlier. Never sent on a request |
| TCF and GPP consent strings from your consent tool | `gdprApplies`, `consentString`, `gpp`, `gppSid` | Yes | Yes | Yes | Your consent tool has stored them |
| US Privacy string from your consent tool | `usPrivacy` | Yes | Yes | When a US Privacy (`__uspapi`) consent tool answers | Your consent tool has stored it |
| Global Privacy Control | `gpc` | No | No | Yes | The browser sends it |
| Your app's personalization switch | `personalization` | Yes | Yes | Yes | Your app passes it |
| Advertising ID, its limit flag, and the ads personalization opt-out | `advertisingId`, `limitAdTracking`, `adPersonalizationOptOut` | Never | Not by default | No | See [Advertising ID on Android](#advertising-id-on-android). Once the SDK has read the advertising ID, it sends `limitAdTracking` and `adPersonalizationOptOut` as true or false. The read runs in the background, so the first request after launch, and a request after a failed read, sends neither |

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:

| App Store data type | Covers | Linked to the user | Purposes |
| - | - | - | - |
| Product Interaction | The moment | Yes | App Functionality, Analytics, Third-Party Advertising |
| Purchase History | The purchase moment's amount and currency | Yes | App Functionality, Analytics, Third-Party Advertising |
| Other Diagnostic Data | Device model, OS version, device type, connection type, low power mode, app version, draw time, request round-trip time | Yes | App Functionality, Analytics, Third-Party Advertising |

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:

| Data safety category | Data type | Covers | Purposes |
| - | - | - | - |
| App activity | App interactions | The moment | App functionality, Analytics, Advertising or marketing |
| Financial info | Purchase history | The purchase moment's amount and currency | App functionality, Analytics, Advertising or marketing |
| App info and performance | Diagnostics | Device model, OS version, device type, connection type, battery saver, app version | App functionality, Analytics, Advertising or marketing |
| App info and performance | Other app performance data | Draw time, request round-trip time | App functionality, Analytics, Advertising or marketing |
| Device or other IDs | Device or other IDs | The advertising ID, only when the SDK reads it (see below) | App functionality, Analytics, Advertising or marketing |

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:

1. 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.
2. Your app includes the Google Play services ads identifier library.
3. 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.
4. Your app's store listing is not for children.
5. Personalization is not off for this user.

The SDK adds neither the permission nor the library to your app. To stop the SDK from reading the advertising ID while your app ships the library, remove the permission from the merged manifest:

```xml AndroidManifest.xml theme={null}
<uses-permission
    android:name="com.google.android.gms.permission.AD_ID"
    tools:node="remove" />
```

The `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](#what-the-sdk-sends).


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