EN - GDPR - Differences between Accengage and Airship

Ce contenu est également disponible en français.

 

This article highlights the major differences between Accengage and Airship with respect to data collection.

Accengage

Data collection

Data collection on Accengage is controlled by:

  • The option acc_optin_data (only for Android)

    • This configuration option enables data collection by the Accengage Android SDK for the whole application.

  • The function setOptinData (Android) and setDataOptInEnabled (iOS)

    • This method enables or disables data collection by the Aggengage SDK (true/false).

  • The function collect:setOptinData (Web)

    • This method enables or disables data collection by the Accengage SDK (true/false).

Here is the list of fields tracked by the Mobile Accengage SDK when the collection is active.

Device ID
Token
Number of visits
Install date
Last opened
Device Model
OS Version
Language
Bundle Version
Latitude
Longitude
Altitude

Geolocation
SDK Version
Feedback
Time Zone
System push opt-in
Enabled push
Enabled in-app
Random Id
Country code
Operator name
Connection type

click
react_inapp
react_alarm
react_inbox
target
send_inapp
send_alarm
send_inbox

 

Here is the list of fields tracked by the Web Accengage SDK when the collection is active.

Device ID
Token
Number of visits
Install date
Last opened
Browser name
Browser version
Device platform
Language
SDK version

First opt-in date
First opt-in domain
Feedback
sw_version
userPublicKey
userAuth
Enabled in-app
Random Id
Country code

click
target

 

Accengage use case

When the user opens the application for the first time, the SDK is not launched until the user has given their permission to collect their data through our SDK.

  • If the user accepts: all data is retrieved and sent to Accengage.

  • If the user doesn’t give their consent: no data is recovered by Accengage. The profile does not exist in the database.

Here is a diagram explaining what happens when a user turns optinData off or on:

2.png

Data purge

After allowing the data collection for the first time, if a user deactivates it, then their profile and their data will be deleted within 7 days. If you do not want to wait 7 days, there is an API endpoint that allows you to manually delete a user's data, with the method DELETE.

 

Airship

Data collection on Airship is controlled by:

  • The option dataCollectionOptInEnabled (Android / iOS).

    • This configuration option indicates if data collection by the Airship SDK must be opted-in to.

  • The methods setDataCollectionEnabled (Android) and isDataCollectionEnabled (iOS).

    • These methods enable or disable data collection by the Airship SDK (true/false).

  • The method sdk.dataCollectionEnabled (Web)

    • This method enables or disables data collection by the Airship SDK (true/false).

    • Note that a parameter is available for our Web SDK: dataCollectionOptInEnabled (to be setup in the snippet).
      This parameter can be true or false. If it’s true, the above method will be required before asking user to be opt-in to notifications.

Data collection process

The list of data collected will depend on the SDK features activated.

If data collection is disabled, all SDK features will also be disabled and no data can be collected (the profile will not be created since the SDK is not launched).

The details of the data collected according to the activated functionalities can be found on the following pages:

Push Token case

On Airship, it is possible to retrieve the token and continue to send notifications even if the user has refused data collection. Please note that this requires the user's consent from your application:

For the Web SDK, please refer to the following table:

3.png

Note that if a user was opt-in data and becomes opt-out data, tags and named_user will be removed. Other information remains but won’t be collected.

 

Airship use case

  • Data collection enabled by default: SDK is launched. All data is collected and transmitted to Airship.
  • Data collection enabled by default features: SDK launches and activates some features by default. Only the data, which are associated with these functionalities, are then collected. Others may later depending on user choice.
  • Data collection disabled: The SDK does not get launch until the user agrees. No data is collected.

What about the Accengage profile following the upgrade? If users deny data collection from the combined SDK, this also applies to their Accengage profile. Therefore, no push can be received by this profile whether it is sent from the Accengage or Airship platform.

 

Data purge

After accepting the data collection for the first time, if a user deactivates it, then only certain data will be tracked. These data will be tracked at each opening (see the table above).

Unlike Accengage, the complete profile purge is not automatic. If you want to remove all personal data from a profile, you can do so using the channel Uninstall API. This changes the channel status to Uninstall and Opted-out, and removes all the personal data. However, the channel ID, with the platform, creation date and last registration date, is never deleted from Airship’s database.

 

Please feel free to contact our support team if you have any questions regarding this topic.

Was this article helpful?
0 out of 0 found this helpful
Submit a request