> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/other/faq/what-kind-of-data-is-collected-via-batch-by-default.md).

# What kind of data is collected via Batch SDKs by default?

Here is the list of data collected via Batch by default. Data can be collected from the SDK or generated server-side.

## Device data <a href="#device-data" id="device-data"></a>

### Mobile (iOS / Android) <a href="#mobile-ios--android" id="mobile-ios--android"></a>

| <ul><li>Installation ID</li><li>API level of the SDK (on Android)</li><li>IP address (shared with Batch, but not stored on Batch side)</li><li>Bundle ID</li><li>OS version</li><li>App version</li><li>Batch SDK version</li></ul> | <ul><li>Push token</li><li>Push notifications opt-in status</li><li>MLVL (Mobile Landing Version)</li><li>Mobile carrier\*: Batch collects the MNC/MCC codes and deducts the carrier name based on these IDs.</li><li>Locale (language and region)</li><li>Device time zone</li></ul> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

{% hint style="warning" %}
This list details the data collected by default by SDK V.2. If you are using an older version, we recommend updating the SDK to the latest version (migration guide available here : [iOS](https://doc.batch.com/developer/sdk/ios/advanced/migration-guides) / [Android](https://doc.batch.com/developer/sdk/android/advanced/2x-migration)).

If you have any questions about the default data collected by SDK V.1, feel free to reach out to us via our Live Chat.
{% endhint %}

### Web <a href="#web" id="web"></a>

| <ul><li>Installation ID</li><li>IP address (shared with Batch, but not stored on Batch side)</li><li>Push token</li><li>Push notifications opt-in status</li><li>User-agent (web browser, OS, etc.)</li></ul> | <ul><li>Locale (language and region)</li><li>Country</li><li>Device time zone</li><li>City (see above for more details)</li><li>Batch SDK version</li></ul> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |

Batch does not set any cookies but relies on Local Storage.

## App usage and campaigns data (App + Web) <a href="#h_c9da39433e" id="h_c9da39433e"></a>

| <ul><li>First SDK start date</li><li>Last SDK start date</li><li>List of the campaigns that targeted the installation.</li><li>List of the campaigns that targeted the installation and clicked by the user.</li></ul> | <ul><li><a href="https://doc.batch.com/getting-started/features/mobile-engagement-platform/userbase#smart-segments">Smart Segment</a></li><li>Send date of the most recent campaign that targeted the installation.</li><li>Number of push sent to the install, used for frequency capping limit.</li></ul> |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |


---

# 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://doc.batch.com/getting-started/other/faq/what-kind-of-data-is-collected-via-batch-by-default.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.