Preserve user privacy

For a general introduction to privacy-preserving methods in the AppsFlyer SDK, see Preserving user privacy (under Getting started).

Use start to share only the install event

If you prefer to send only the install event and no additional information, you can invoke start with a request callback. Upon receiving a success message confirming that the install event has been logged, you should then call stop or anonymizeUser from within the callback function.

• anonymizeUser sends data to AppsFlyer; however, upon its arrival to AppsFlyer servers, all identifiers (including IP address) are either deleted or hashed.
• The stop method reverts the start call, which means that the SDK stops sending any data to AppsFlyer.

appsflyer.start(getApplicationContext(), null, new AppsFlyerRequestListener() {
    @Override
    public void onSuccess() {
        Log.d(LOG_TAG, "Launch sent successfully, got 200 response code from server");
        appsflyer.stop(true, getApplicationContext());
    }

    @Override
    public void onError(int i, @NonNull String s) {
        Log.d(LOG_TAG, "Launch failed to be sent:\n" +
                "Error code: " + i + "\n"
                + "Error description: " + s);
    }
});

Prevent sharing data with third parties

If you want to prevent sharing install and in-app event information with third parties such as SRNs and ad networks, use the setSharingFilterForPartners method before calling start. Partners that are excluded with this method will not receive data through postbacks, APIs, raw data reports, or any other means.

Note: You can call setSharingFilterForPartners again if the user changes the app sharing settings (adding or removing partners) later in the session.
For a code example please refer to setSharingFilterForPartners.

Anonymize user information

You can configure the SDK to instruct AppsFlyer to remove all user-identifying information by using the anonymizeUser method. In this case, the SDK sends install and in-app events to AppsFlyer, where all identifying information is then deleted or hashed:

• Deleted: personal identifiers (GAID, IDFA, IDFV, and CUID)
• Hashed: AppsFlyer ID and IP address.

To learn how to implement the method without anonymizing install events, see: Share only the install event.

Disable IDs

The SDK is capable of sending several specific identifiers to AppsFlyer. You can choose to exclude them in accordance to your needs.

Note: Disabling the advertiser ID before calling start will prevent SRN attribution.

Send data only after the user opts-in

In cases where you would like to not send any data to AppsFlyer until the user gives consent, defer calling start until after the consent is given.