You can control whether tracking activity is allowed on a specific device:
Mobile Apps - The VA library respects the
AdobeMobile library’s privacy and opt-out settings. To opt-out of tracking, you need to use the
AdobeMobile library. For more information on the
AdobeMobile library’s opt-out and privacy settings, see Opt-Out and Privacy Settings.
VisitorAPI privacy and optout settings. To optout of tracking, you need to opt out from the Visitor API service. For further information on optout and privacy, see Adobe Experience Platform Identity Service..
OTT Apps (Chromecast, Roku) - The OTT SDKs provide General Data Protection Regulation (GDPR)-ready APIs that allow you to set
opt status flags for data collection and transmission, and to retrieve locally stored identities.
Media heartbeat tracking calls are also disabled if the privacy status is set to opt-out.
You can control whether or not Analytics data is sent on a specific device using the following settings:
privacyDefault setting in the
ADBMobile.json config file. This controls the initial setting and persists until it is changed in code.
When a user opts out of tracking, all of the persisted device data and IDs will be purged until the user opts back in.
Opt back in:
Return the current setting:
After the privacy setting is changed using
setPrivacyStatus, the change is permanent until it is changed again using this method, or the app is uninstalled and reinstalled.
This information helps you retrieve locally stored user identities from your Roku app.
The method for retrieving all identifiers gets all user identities known and persisted by the SDK. You must call this method before a user opts-out.
The locally stored identities are returned in a JSON string, which might contain:
vids = ADBMobile().getAllIdentifiers()