Control Privacy - DARO DOCS

Overview

The DARO SDK provides an API that relays the privacy consent state a publisher collects in the app to each ad demand source. The publisher must implement consent collection and its UI; the DARO SDK only relays the resulting values to the ad demand sources.

Available from daro-a 1.6.0 / daro-m 1.3.14.

Apply privacy settings before loading ads so they take effect on ad requests.

GDPR (General Data Protection Regulation) is a consent-based privacy regulation that applies to users in the European Economic Area (EEA) and the UK. Personal data may only be processed after the user explicitly consents.

How the DARO SDK handles it

After you confirm the user’s consent with a consent tool such as UMP, pass the result to the DARO SDK with the API below. The DARO SDK propagates the state to each ad demand source.

Daro.setGdpr(context, GdprStatus.OPT_IN, consentString)

Values

`GdprStatus`	Meaning
`OPT_IN`	The user consented to personal data processing and personalized ads.
`OPT_OUT`	The user declined consent. Ads are served non-personalized.
`NOT_APPLICABLE`	The user is not subject to GDPR (e.g., outside the EEA). Personalized ads are allowed.
`UNKNOWN`	The initial state before the consent prompt has been shown. Use it temporarily until consent is determined.

Caution

Use UNKNOWN only as a temporary state. Leaving a GDPR-covered user at UNKNOWN without showing the consent prompt can be a regulatory violation. Update to OPT_IN or OPT_OUT as soon as consent is determined.

consentString

An optional argument (default ""). If you use a CMP such as UMP, pass the GDPR consent string it generates. If you don’t, leaving it empty ("") is fine. This is a separate value from the CCPA consentString.

Code example

// User consented
Daro.setGdpr(context, GdprStatus.OPT_IN, consentString)

// User declined
Daro.setGdpr(context, GdprStatus.OPT_OUT)

// User is not subject to GDPR
Daro.setGdpr(context, GdprStatus.NOT_APPLICABLE)

// Initial state before the consent prompt has been shown
Daro.setGdpr(context, GdprStatus.UNKNOWN)

CCPA

CCPA (California Consumer Privacy Act) and similar US state privacy laws give users the right to opt out of the sale of their personal information. Unless the user explicitly opts out, processing is allowed by default.

How the DARO SDK handles it

After you confirm whether the user has opted out, pass the result to the DARO SDK with the API below. The DARO SDK propagates the state to each ad demand source.

Daro.setCcpa(context, CcpaStatus.OPT_OUT, consentString)

Values

`CcpaStatus`	Meaning
`OPT_IN`	The user has not opted out. Sale/sharing of personal information is allowed.
`OPT_OUT`	The user opted out of the sale of their personal information.
`NOT_APPLICABLE`	The user is not subject to CCPA.

Default behavior

If you do not call setCcpa, it is treated as OPT_IN and personalized ads are allowed. If your app has CCPA-covered users, set it explicitly.

consentString

This is optional (defaults to ""). If you use UMP, pass the US Privacy String it produced. If you do not use UMP, leaving it empty ("") is fine. This is a separate value from the GDPR consentString.

Caution

CCPA’s OPT_IN / OPT_OUT differ in meaning from GDPR. Under CCPA, OPT_IN means “the user did not opt out,” and OPT_OUT means “the user opted out of the sale of personal information.” Because CCPA is opt-out based, there is no equivalent of UNKNOWN. If the user has not responded yet, treat it as OPT_IN.

Code example

// User did not opt out
Daro.setCcpa(context, CcpaStatus.OPT_IN)

// User opted out of the sale of personal information
Daro.setCcpa(context, CcpaStatus.OPT_OUT)

// User is not subject to CCPA
Daro.setCcpa(context, CcpaStatus.NOT_APPLICABLE)

COPPA

COPPA (Children’s Online Privacy Protection Act) protects children under 13 in the United States. Unlike GDPR and CCPA, this is not a user consent flow — it is the publisher’s declaration of whether the app is child-directed.

How the DARO SDK handles it

After you determine whether your app is child-directed, pass the result to the DARO SDK with the API below. The DARO SDK propagates the declaration to each ad demand source.

Daro.setCoppa(context, CoppaStatus.CHILD)

Values

`CoppaStatus`	Meaning
`CHILD`	The app is child-directed. Personalized ads are not allowed.
`NOT_CHILD`	The app is not child-directed.

Default behavior

If you do not call setCoppa, the child-directed status is not sent to ad demand sources. If your app is child-directed, set it explicitly.

Caution

COPPA declares whether the app as a whole is child-directed. Per-user configuration is not supported. Even if only some users are children, decide on an app-wide basis.

Code example

// App is child-directed
Daro.setCoppa(context, CoppaStatus.CHILD)

// App is not child-directed
Daro.setCoppa(context, CoppaStatus.NOT_CHILD)

Migrating from the previous APIs

The previous grant* / reject* methods are deprecated. Use the set* APIs going forward.

Deprecated	Use instead
`grantGdpr(context, consentString)`	`setGdpr(context, GdprStatus.OPT_IN, consentString)`
`rejectGdpr(context, consentString)`	`setGdpr(context, GdprStatus.OPT_OUT, consentString)`
`grantCcpa(context, consentString)`	`setCcpa(context, CcpaStatus.OPT_IN, consentString)`
`rejectCcpa(context, consentString)`	`setCcpa(context, CcpaStatus.OPT_OUT, consentString)`
`grantCoppa(context)`	`setCoppa(context, CoppaStatus.CHILD)`
`rejectCoppa(context)`	`setCoppa(context, CoppaStatus.NOT_CHILD)`

​Overview

​GDPR

​How the DARO SDK handles it

​Values

​Caution

​consentString

​Code example

​CCPA

​How the DARO SDK handles it

​Values

​Default behavior

​consentString

​Caution

​Code example

​COPPA

​How the DARO SDK handles it

​Values

​Default behavior

​Caution

​Code example

​Migrating from the previous APIs

Overview

GDPR

How the DARO SDK handles it

Values

Caution

consentString

Code example

CCPA

How the DARO SDK handles it

Values

Default behavior

consentString

Caution

Code example

COPPA

How the DARO SDK handles it

Values

Default behavior

Caution

Code example

Migrating from the previous APIs