The most critical areas to get right during implementation are:
- The consent screen — it must display the correct mandatory transparency language, clearly describe what the user is agreeing to, and present the value offer accurately.
- The opt-out mechanism — users must be able to withdraw consent easily, typically via a setting in your app's main settings menu. This is a compliance requirement, not optional.
- Triggering SDK start correctly — Bright SDK must only activate after the user has confirmed consent. Activating it before consent is given is a violation of Bright SDK's guidelines.
- Accurate value representation — the benefit you promise the user on the consent screen must match what they actually receive when they opt in.
Getting these elements right the first time will result in a faster compliance review and fewer revision cycles.
Essentially, all the necessary information is outlined in our integration guides for each operating system (OS). However, we highly recommend watching our guided tour video. It highlights critical elements to pay attention to, ensuring a faster review process and transparent communication with your users.
Ready to start monetizing? Sign up here →