Prerequisites for privacy consent setups
Review key requirements before implementing your privacy consent solution, including SDK behavior for missing consent, regional frameworks, developer responsibility, and the impact on revenue if consent is not provided.
읽는 시간 1분최근 업데이트: 한 달 전
Prerequisite considerations for privacy consent setups
Review these requirements before setting up privacy consent:Missing consent
The SDK acts only on the consent values it receives. If no value is provided, the SDK interprets this according to the relevant privacy framework:- For opt-in frameworks, no value means the user is considered not to have consented.
- For opt-out frameworks, no value means the user is considered to have consented.
Regional privacy frameworks
The SDK doesn't automatically detect or interpret regional privacy laws. You're responsible for determining which privacy frameworks apply (for example, GDPR or CCPA) for all regions and for sending the corresponding consent signals. Refer to Supported privacy frameworks for the full list.Developer responsibility
When using Developer consent, you’re responsible to do the following:- Collect and store valid consent from users
- Manage and update consent when user preferences change
- Pass the correct consent and opt-out values to the SDK