Data Collection

Data collection can be disabled at the SDK level to prevent the collection of any data (with the exception of the data collection opt-in status). Disabling data collection disables all features of the SDK.

Data collected in the SDK

Any feature enabled

If any feature is enabled, the SDK will collect and send the following data:

• Channel ID
• Locale
• TimeZone
• Platform
• Opt in state (push and notifications)
• SDK version
• Accengage Device ID (Accengage module for migration)

In-app automation enabled

In addition to the default data collection when any feature is enabled, In-App Automation will also collect:

• App Version (App update triggers)

Message center enabled

In addition to the default data collection when any feature is enabled, Message Center will also collect:

• Message Center User
• Message Reads & Deletes

Push enabled

In addition to the default data collection when any feature is enabled, push will also collect:

• Push tokens

Chat enabled

In addition to the default data collection when any feature is enabled, Airship Chat will also collect:

• User messages

Analytics enabled

In addition to the default data collection when any feature is enabled, analytics will also collect:

• Events
• Associated Identifiers
• Registered Notification Types
• Time in app
• App Version
• Device model
• Device manufacturer
• OS version
• Carrier
• Connection type
• Framework usage

Tags and attributes enabled

In addition to the default data collection when any feature is enabled, tags and attributes will also collect:

• Channel and Contact Tags
• Channel and Contact Attributes

Contacts enabled

In addition to the default data collection when any feature is enabled, contacts will also collect:

• External ids (named user)

Location enabled

In addition to the default data collection when any feature is enabled, location will also collect:

• Location permissions
• Collect location for the app (Airship no longer supports uploading location as events)

All SDK featues are enabled by default, but individual features can be enabled or disabled by using the Privacy Manager. The privacy manager can also be used to completely opt out of SDK functionality, or to initially run the SDK in an opted-out state. If all features are disabled the SDK will not make any network requests or collect data, and will effectively no-op. Data collection can also be enabled or disabled on a per-module basis.

Configuring default enabled features

Default enabled features can be declared in UAConfig or AirshpConfig.plist by setting the enabledFeatures flag. For instance, to default to just push:

let config = Config.default()
config.enabledFeatures = [.push]

UAConfig *config = [UAConfig defaultConfig];
config.enabledFeatures = UAFeaturesPush;

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  ...
  <key>enabledFeatures</key>
  <array/>
    <string>push</string>
  </array>
  ...
</dict>
</plist>

To fully disable data collection by default, just set the enabled features in your config to [] in Swift, or UAFeaturesNone in Objective-C:

let config = Config.default()
config.enabledFeatures = []

UAConfig *config = [UAConfig defaultConfig];
config.enabledFeatures = UAFeaturesNone;

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  ...
  <key>enabledFeatures</key>
  <array/>
    <string>none</string>
  </array>
  ...
</dict>
</plist>

Enabling features at runtime

To enable full Airship functionality at runtime, make the following call:

Airship.shared.privacyManager.enableFeatures(.all)

[UAirship.shared.privacyManager enableFeatures:UAFeaturesAll];

To enable individual features, provide the associated option as shown below:

Airship.shared.privacyManager.enableFeatures(.push)

[UAirship.shared.privacyManager enableFeatures:UAFeaturesPush];

Airship.shared.privacyManager.enableFeatures(.messageCenter)

[UAirship.shared.privacyManager enableFeatures:UAFeaturesMessageCenter];

Airship.shared.privacyManager.enableFeatures(.analytics)

[UAirship.shared.privacyManager enableFeatures:UAFeaturesAnalytics];

Airship.shared.privacyManager.enableFeatures(.inAppAutomation)

[UAirship.shared.privacyManager enableFeatures:UAFeaturesInAppAutomation];

Airship.shared.privacyManager.enableFeatures(.chat)

[UAirship.shared.privacyManager enableFeatures:UAFeaturesChat];

Airship.shared.privacyManager.enableFeatures(.tagsAndAttributes)

[UAirship.shared.privacyManager enableFeatures:UAFeaturesTagsAndAttributes];

Airship.shared.privacyManager.enableFeatures(.contacts)

[UAirship.shared.privacyManager enableFeatures:UAFeaturesContacts];

Airship.shared.privacyManager.enableFeatures(.location)

[UAirship.shared.privacyManager enableFeatures:UAFeaturesLocation];

You can also enable combinations of features by combining or bitmasking options. For instance, to enable both push and message center:

Airship.shared.privacyManager.enableFeatures([.push, .messageCenter])

[UAirship.shared.privacyManager enableFeatures:UAFeaturesPush | UAFeaturesMessageCenter];