> 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/merchant-tokenization/sdk-integration/guidelines/google-play-data-safety-form.md).

# Google Play data safety form

Use this information to complete the Google Play data safety form for your merchant native application when you integrate the Thales SDK.

## Data collection and security <a href="#data-collection-and-security" id="data-collection-and-security"></a>

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

| Does your app collect or share any of the required user data types?                                                             | Yes |
| ------------------------------------------------------------------------------------------------------------------------------- | --- |
| Is all of the user data collected by your app encrypted in transit?                                                             | Yes |
| Do you provide a way for users to request that their data is deleted?                                                           | No  |
| Is your app currently certified by an authorized lab, according to the Mobile Application Security Assessment (MASA) framework? | No  |

## Data types, usage, and handling <a href="#data-types-usage-and-handling" id="data-types-usage-and-handling"></a>

For more information about the data types used, refer to the [Google documentation](https://support.google.com/googleplay/android-developer/answer/10787469?hl=en#types\&zippy=%2Cdata-types).

| Category                           | Device or other IDs                                                                                                                                                                               |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Data type                          | Device or other IDs                                                                                                                                                                               |
| Description                        | <p>Identifiers that relate to an individual device, browser, or app.<br>For example, an IMEI number, MAC address, Widevine Device ID, Firebase installation ID, or an advertising identifier.</p> |
| Is data collected?                 | Yes (device ID passed through the SDK API)                                                                                                                                                        |
| Is data processed ephemerally?     | No                                                                                                                                                                                                |
| Is this data optional for the SDK? | No                                                                                                                                                                                                |
| Purpose of data collection?        | App functionality, fraud prevention                                                                                                                                                               |
| Is data shared?                    | No                                                                                                                                                                                                |
| Purpose of data sharing?           | N/A                                                                                                                                                                                               |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/merchant-tokenization/sdk-integration/guidelines/google-play-data-safety-form.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.