> 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/3d-secure/es/integrar-el-sdk-de-d1/despliegue/directrices-para-el-envio-de-la-aplicacion/politicas-de-privacidad-de-aplicaciones-de-apple.md).

# Políticas de privacidad de aplicaciones de Apple

The following section provides information to help you understand the impact of Apple's app privacy policies on D1 SDK to your issuer application.

{% hint style="info" %}
This page only covers the scope of D1 SDK.
{% endhint %}

### Data safety questions

These are the fields that are required in the Apple app privacy declaration:

| Question                                                            | Answer |
| ------------------------------------------------------------------- | ------ |
| Do you or your third-party partners collect data from this app/SDK? | Yes    |

### Data types used

<table><thead><tr><th>Category</th><th>Data type</th><th width="351">Is data collected?</th><th>Data use</th><th>Is data used for tracking?</th><th>Is data linked to the end user?</th></tr></thead><tbody><tr><td>Contact Info</td><td>Name</td><td>Yes (Data passes through the D1 SDK. This is for Mastercard Click to Pay.)</td><td>App functionality</td><td>No</td><td>Yes</td></tr><tr><td>Contact Info</td><td>Email Address</td><td>Yes (Data passes through the D1 SDK. This is for Mastercard Click to Pay.)</td><td>App functionality</td><td>No</td><td>Yes</td></tr><tr><td>Contact Info</td><td>Phone Number</td><td>Yes (Data passes through the D1 SDK. This is for Mastercard Click to Pay.)</td><td>App functionality</td><td>No</td><td>Yes</td></tr><tr><td>Contact Info</td><td>Physical Address</td><td>Yes (Data passes through the D1 SDK. This is for Mastercard Click to Pay.)</td><td>App functionality</td><td>No</td><td>Yes</td></tr><tr><td>Contact Info</td><td>Other User Contact Info</td><td>No</td><td>N/A</td><td>N/A</td><td>N/A</td></tr><tr><td>Identifiers</td><td>User ID</td><td>Yes (<code>consumerId</code> as part of D1 SDK APIs)</td><td>App functionality</td><td>No</td><td>Yes</td></tr></tbody></table>


---

# 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/3d-secure/es/integrar-el-sdk-de-d1/despliegue/directrices-para-el-envio-de-la-aplicacion/politicas-de-privacidad-de-aplicaciones-de-apple.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.