Data that the Blueshift iOS SDK collects

We provide full control over the types of data that the SDK can collect. The Blueshift SDK never asks users for permission to collect any type of data. The host app should provide the functionality to get the necessary permissions from the user.

Types of data that the SDK collects or does not collect

Data	Does the SDK collect it?
Contact information	No
Health and fitness	No
Financial information	No
Location	No. The SDK itself does not collect the location data. The host app should capture and pass the location data to the SDK if the host app wants Blueshift to track it.
Sensitive information	No
User content	No
Browsing history	No
Search history	No
Identifiers	Yes. By default, the SDK collects IDFV as the device identifier. SDK also provides an option to use other identifiers such as UUID. SDK never collects the IDFA automatically, If you want Blueshift to track the IDFA, then the host app need to capture it and pass the IDFA value to SDK.
Purchases	No
Usage data	No
Diagnostics	No
Other data	No

Data use

Blueshift uses the data that it collects to enable product personalization, analytics, and optional advertising services.
The following table provides the possible uses of the collected data and whether Blueshift uses the collected data for those use-cases.

Use	Do we use the collected data for this use-case?
Third party advertising	No
Developer's advertising or marketing	Yes, if the developer configures multi-channel campaigns that send marketing material over emails, SMSes, in-app messages, or push notifications using Blueshift. In addition, developers can use syndications functionality on Blueshift to export data to advertising platforms. For more information, see Syndications.
Analytics	Yes
Product personalization	Yes
App functionality	No
Other purposes	No

Developer's advertising or marketing

You have to share information on the first-party ads that you display in the app, send marketing communications directly to your users, or share data with entities that display your ads.

With Blueshift, you can:

Send in-app messages, push notifications, emails, SMSes
Use syndication functionality to integrate our platform with advertising services like Google Ads/Facebook Ads and share user identification data with their platform. If you use the syndication functionality to integrate third party advertising services, then user identification data will be shared with the third party advertising services for personalization of ads.

Data linked to a user

You need to identify whether each data type is linked to the user’s identity (via their account, device, or other details). Either you can identify the data yourself, or a third-party service can do it for you. Data collected from an app is mostly linked to the user’s identity, unless there are specific privacy protections before collection to de-identify or anonymize it.

Blueshift provides a way to collect the user data using device ID, cookie, email ID, and customer ID in order to associate the data to the corresponding user profile.

Tracking

Tracking refers to linking customer data to third-party data for targeted ads or advertising measurement purposes, or sharing data collected from your app about a particular end-user or device with a data broker.

Blueshift tracks the device ID and profile information in order to associate it to the corresponding user profile on the Blueshift platform. Blueshift provides optional advertising integration services (syndication) to use this data for advertising.