Opt-out and privacy
Opt-out / Opt-in
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 .
- 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:
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.
- The privacyDefault setting in the ADBMobile.json config file. This controls the initial setting and persists until it is changed in code.
- The ADBMobile().setPrivacyStatus() method.
- Opt out:
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:
Retrieving Stored Identifiers (OTT Apps)
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:
- Company Context - IMS Org IDs
- User IDs
- Experience Cloud ID (MCID)
- Data Source IDs (DPID, DPUUID)
- Analytics IDs (AVID, AID, VID, and associated RSIDs)
- Audience Manager ID (UUID)
vids = ADBMobile().getAllIdentifiers()