> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/classic-push-provisioning/help/application-submission-guidelines/google-plays-data-safety-form.md).

# Google Play's data safety form

This section helps you understand how the Push Provisioning SDK affects your mobile application when you complete the Google Play Data safety form.

> <i class="fa-info-circle">:info-circle:</i>
>
> #### Note <a href="#note" id="note"></a>
>
> * This page only covers the scope of the Push Provisioning SDK.
> * You may see different responses in the Google Play Data safety form if your application performs additional processing, transfer, or storage.

### Data safety questions <a href="#data-safety-questions" id="data-safety-questions"></a>

These fields are required in the Google Play Data safety form:

| Question                                                                                                                        | Answer | Comments                                                                    |
| ------------------------------------------------------------------------------------------------------------------------------- | ------ | --------------------------------------------------------------------------- |
| Does your app collect or share any of the required user data types?                                                             | Yes    | Our service relies on several data types to be captured and sent to server. |
| Is all of the user data collected by your app encrypted in transit?                                                             | Yes    | Traffic to server is encrypted in transit.                                  |
| Do you provide a way for users to request that their data is deleted?                                                           | No     | Users have access to the APIs to remove the user data types stored.         |
| Is your app currently certified by an authorized lab, according to the Mobile Application Security Assessment (MASA) framework? | No     | This certification is managed at the application level.                     |

### Data types used <a href="#data-types-used" id="data-types-used"></a>

For details on these data types, see the [Google documentation](https://support.google.com/googleplay/android-developer/answer/10787469?hl=en#types\&zippy=%2Cdata-types).

| Category            | Data type           | Description                                                                                                                                                                          | Is Data Collected?      | Is Data processed ephemerally? | Is Data Optional? | Purpose of data collection | Is Data shared? | Purpose of data sharing |
| ------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------- | ------------------------------ | ----------------- | -------------------------- | --------------- | ----------------------- |
| Device or other IDs | Device or other IDs | Identifiers that relate to an individual device, browser, or app. For example, an IMEI number, MAC address, Widevine Device ID, Firebase installation ID, or advertising identifier. | Yes (WalletId from OEM) | Yes                            | No                | App fun                    |                 |                         |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/classic-push-provisioning/help/application-submission-guidelines/google-plays-data-safety-form.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.