Managing privacy for multiple legislation zones

BlueConic helps you comply with customer data privacy regulations worldwide. With multiple privacy legislation zones (i.e. GDPR covering Europe, CCPA in California, PIPEDA in Canada, SB220 for the state of Nevada, and NYPA potential legislation for New York State), compliance gets complicated quickly.

Managing multiple data privacy zones including GDPR, CCPA, PIPEDA, SB220, and NYPA

You can use BlueConic Objectives to manage customer and visitor privacy and marketing consent across multiple privacy legislation zones. Objectives determine how and whether an individual profile has given consent for the action or content that Objective governs. Use Objectives to ensure that content is shown only to profiles that have consented to the objective or are not covered by the relevant privacy legislation.

Using Privacy Settings for multiple legislation zones

Use the Privacy settings page in BlueConic to select the privacy legislation zones you want to support.

How do I use the BlueConic CDP to manage GDPR and CCPA compliance for customer privacy and marketing consent and for different privacy legislation zones worldwide?

Using Objectives to manage privacy and marketing consent

You can attach Objectives to content or actions in BlueConic, to ensure that the pool of profiles exposed to these objects includes only those profiles that have given the proper consent. For example, if you use a BlueConic Dialogue to display marketing content, you may need to obtain people's consent. You could add a privacy Objective to a BlueConic Dialogue to ensure that your marketing content is presented only to profiles that have given prior consent for marketing materials.

Consent status for BlueConic Objectives

Depending on a profile's consent status, BlueConic will include or not include profiles when matching user profiles to your consent objectives. For example, you can specify that a content dialogue should be shown only to profiles with a certain privacy legislation setting.

How do I let customers ask for privacy and marketing consent before customer profiling in the BlueConic CDP? 

When setting conditions for Objectives, you can specify the following consent categories for including profiles in an objective:

Consented: Include all profiles that consented to the objectives. In the case of a content Dialogue, this means show content to profiles that have explicitly consented to the selected Objective. 

Not needed or consented: Include all profiles that don't need to consent (i.e. the legislation is set to "None"), and also profiles that consented to the objectives. In the case of a content Dialogue, BlueConic would show content to all profiles that have explicitly consented to the selected objectives and to profiles from a legislation zone that isn't covered by the selected objective.

Refused: Include all customer profiles that refused the privacy objectives.

Unknown: Include all customer profiles that need to consent to marketing objectives (i.e. legislation is not set to "None"), but have not yet consented or refused the objectives.

Refused or unknown: Include all customer profiles that did not consent to the objectives. These profiles fall into either the Refused or Unknown category.

See Objectives for more information on using BlueConic Objectives for privacy and consent management. See Privacy settings for more information on supported privacy legislation zones.