Adobe details streaming media SDK opt-out mechanisms for data collection
Adobe details various opt-out mechanisms for its streaming media SDKs, including Web SDK, mobile SDKs for iOS, Android, and Roku, and its Media Edge API. The documentation provides implementation guidance for respecting user consent regarding data collection across different Adobe platforms and APIs. It also covers legacy implementation types for Analytics-only use cases.
Key Takeaways
- Adobe's documentation covers opt-out implementation for Web SDK, Adobe Experience Platform Mobile SDKs (iOS, Android, Roku), Media Edge API, and older Media SDK JS 3.x, Chromecast Media SDK 3.x, and Media Collection API.
- For Web SDK and AEP Mobile SDKs, a `setConsent` or `setPrivacyStatus` call with an 'out' value stops all data collection, persisting across sessions.
- Server-side implementations like Media Edge API and Media Collection API require the application to manage consent status and withhold API calls for opted-out users.
- Partial opt-out for CCPA is supported via the Media Collection API, allowing users to opt out of server-side data forwarding or federated data sharing.
Why It Matters
Ensuring proper data privacy controls is crucial for streaming platforms, especially with evolving global regulations. Adobe's detailed guidance for its varied SDKs and APIs will help implementers maintain compliance and build user trust. The distinction between client-side SDKs that handle persistence and server-side APIs requiring explicit application-level checks highlights implementation complexity for hybrid architectures. Streaming providers should audit their Adobe Analytics implementations against these guidelines to ensure user consent is consistently respected across all their streaming endpoints and applications.
Read full article at experienceleague.adobe.com
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source