Data Collection
Types of data collected by the SDK.
Privacy Manager
Data collected by the Airship SDK can be controlled using Privacy Manager flags. Each flag enables additional Airship features within the SDK and controls what data is collected. The flags are for individual or groups of functional features within the SDK. Some Airship features, such as contact tags, require multiple feature flags to be enabled.
| Privacy Manager Flag | Features |
|---|---|
| Push | Push notifications |
| In-App Automation | In-App Automation, In-App Messages, Scenes, Surveys, and Landing Pages |
| Message Center | Message Center |
| Tags and Attributes | Tags, Attributes, Subscription Lists, and Preference Center |
| Contacts | Contact Tags, Attributes, and Subscription Lists; Named User; and Associated Channels |
| Analytics | Associated identifiers, Custom events, Screen tracking, Surveys |
| Chat | In-App Chat |
| Location | Location Lat/Long gathering for App (Not reported to Airship), Location status reporting |
SDK Data Collection
All SDK features are enabled by default, but the SDK can be configured to disable all or a subset of features on start. If the SDK is initialized without any features enabled, it will not store any data or make any network requests. If the SDK features are disabled after being previously enabled, it may make a few network requests to opt the channel out to prevent notifications.
The data collected automatically by the SDK is not used to track users across apps.
| Data | Description | Privacy Manager Features |
|---|---|---|
| Channel ID | Airship app install identifier. | Any |
| Locale | The app’s locale, comprised of language and language country. | Any |
| Time zone | The device time zone. | Any |
| Platform | The platform the device is running on, e.g., Amazon, Android, iOS. | Any |
| Accengage device ID | The device ID on Accengage. Only collected if using the Accengage module for Accengage to Airship migration. | Any |
| SDK version | The Airship SDK version. | Any |
| Notification opt-In status | Notifications and background opt-in status. | Any |
| Contact ID | Internal Airship ID that maps to contact. | Contacts |
| App version | The app’s version. | Analytics, In-App Automation |
| Message Center credentials | The message center credentials for message list access. | Message Center |
| Message Center message status | Message reads and deletes. | Message Center |
| Push token | The push address for push notifications. | Push |
| Push provider | The push delivery platform, e.g., FCM, HMS. | Push |
| Device model | The device model, e.g., Samsung GT-S5830L, iPad Air. | Analytics |
| Device manufacturer | The device manufacturer name. | Analytics |
| OS version | The device OS version. | Analytics |
| Carrier | The device mobile carrier. | Analytics |
| Connection Type | The connection type, e.g., Cell, Wifi. | Analytics |
| Framework | Airship framework usage: React Native, Unity, Cordova, Flutter, Titanium, and Xamarin. | Analytics |
| Lifecycle events | Init, foreground, background, and time in app. | Analytics |
| Scheduled summary1 | Scheduled summary notification status. Only collected if it is being used. | Analytics |
| Time sensitive1 | Time sensitive notification status. Only collected if it is being used. | Analytics |
| Notification events | Push notification interaction events. | Analytics, Push |
| Notification permissions | Authorized notification types and permissions. | Analytics, Push |
| In-App Automation events | Events within an In-App display: displays, resolutions, page views, button taps, and survey results. | Analytics, In-App Automation |
| Location permission | The location permission status. | Analytics, Location |
1. iOS 15+ only
App Data Collection
In addition to the data automatically collected by the SDK, the app can provide data to the SDK for collection:
| Data | Description | Privacy Manager Features |
|---|---|---|
| Channel Tags | Tags and tag groups set on the channel. | Tags and Attributes |
| Channel Subscription Lists | Subscription Lists set on the channel. | Tags and Attributes |
| Channel Attributes | Attributes set on the channel. | Tags and Attributes |
| Contact Tags | Tags and tag groups set on the contact. | Tags and Attributes, Contacts |
| Contact Subscription Lists | Subscription Lists set on the contact. | Tags and Attributes, Contacts |
| Contact Attributes | Attributes set on the contact. | Tags and Attributes, Contacts |
| Named User | Contact’s external ID. | Contacts |
| Associated Channels | Email and email opt-in data, SMS and SMS opt-in data, etc. | Contacts |
| Associated Identifiers | Additional analytics identifiers. | Analytics |
| Custom Events | App’s custom events. | Analytics |
| Screen Tracking | App’s screen tracking. | Analytics |
Data Privacy
Airship makes HTTPS encryption (also referred to as TLS connection) available for data in transit to or from the Service, for more information see Airship Security Measures. Data collected by the SDK is not transferred to any third parties unless a partner integration is enabled and configured by the application. For information on individual data requests, see Individual Data Privacy Rights.
Remaining functionality (when data collection is disabled) includes broadcast Message center messages and broadcast In-App Automation messages. When data collection is disabled, Airship will still collect language, language country, timezone, app version, SDK version, and device OS.
Disabling data collection on the Flutter platform requires setting configurations files for both the iOS and Android native SDKs
Config Instructions
Data collection can be disabled at the native SDK level by following the platform-specific data collection guides:
Opting In: Data Collection
Restoring full Airship functionality by opting back into data collection can be accomplished with the following call:
Airship.setDataCollectionEnabled(true);Excluding Push from Opt-out
By default, push functionality will also be disabled when data collection is disabled. However, you can override this behavior with the following call:
Airship.setPushTokenRegistrationEnabled(true);Categories