Help Center

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/CPRA in California, PIPEDA in Canada, SB220 for the state of Nevada, and NYPA potential legislation for New York State, and other privacy legislation zones supported in BlueConic), compliance gets complicated quickly.

Managing multiple data privacy zones 

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 (BlueConic Settings > Privacy) in BlueConic to select the privacy legislation zones you want to support.

privacy_page_consent.jpg

To require consent for all profiles, regardless of visitors’ legislation zone, select the option for “Rest of the World (including disabled legislation zones).” This ensures that your organization is compliant with any legislation.

Note: This option is labeled “Whole world” if no other legislation zone is selected on the Privacy settings page.

Important Notes:

  • As of the June 2022 release, when the United Kingdom (UK GDPR) legislation zone is enabled on the Privacy settings page, all new UK visitors will be assigned to that zone and no longer to Europe (GDPR).
  • If United Kingdom (UK GDPR) is NOT enabled on the Privacy settings page, then any new UK visitor will continue to be assigned to the Europe (GDPR) zone until the UK zone is enabled.
  • Existing UK profiles before June 2022 will still be part of the Europe (GDPR) zone. No changes have been made for those visitors.

Privacy status for legislation zones

For each privacy legislation zone, the status describes whether objectives will be executed for profiles in that zone:

  • Opt-in: Objectives will only be executed for profiles in this legislation zone that have given explicit consent
  • Opt-out: Objectives will be executed, except for profiles in this legislation zone that explicitly refused the objective
  • Disabled: Objectives will always be executed for profiles in this legislation zone

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.

Setting consent to opt-in or opt-out

BlueConic enables you to set a legislation zone to be opt-in or opt-out by default through the Privacy settings page. This allows you to specify whether consent for profiles governed by a particular legislation zone should by default be opted-into a consent setting or should be considered opted-out until they explicitly provide consent. Consult your legal team for regulations governing the localities and legislation zones of your profiles.

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 to 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.

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

Was this article helpful?
0 out of 0 found this helpful