Creating and Updating Privacy Protocols

  • Updated

A Privacy Protocol is set of rules that determine how consent and preference choices are collected. It contains the consent or preference that an end-user would see on their Preference Hub and related settings on how that choice is gathered.

Osano Curated Privacy Protocols

Osano provides 5 standard Privacy Protocols that are common consent and preference types. These Osano managed Privacy Protocols cannot be edited, updated, or changed. 

UC_default_protocols.png

The 5 standard Privacy Protocols are as follows:

  1. Do Not Sell/Share - meets Do Not Sell/Share personal data requirements for California (CCPA/CPRA), Colorado, Connecticut, Utah, Virginia, and The United State. It provides organizations with the ability for their subjects to opt-out of the sale of their personal information to third parties.
  2. Use of Sensitive Data – provides organizations with the ability for their subjects to opt-out of processing and use of their sensitive personal information in California, Colorado, Connecticut, Virginia, and The United States.
  3. Email Communication Sales – provides organizations the ability for their subjects to opt-out of all sales communications sent via email
  4. Email Communications Newsletter - provides organizations the ability for their subjects to opt-out of all newsletter communications sent via email
  5. Email Communications Other - provides organizations the ability for their subjects to opt-out of all communications sent via email

Note: Osano will be adding new managed privacy protocols in future releases.

Creating custom privacy protocols

If your consent or preference type is not covered by the Osano curated privacy protocols, you may create your own custom privacy protocol.

UC_add_protocol.png

Creating a Privacy Protocol is simple and can be set up in a matter of minutes. Follow the steps below to create one from scratch:

  1. Navigate to ‘Privacy Protocols’ from the left-hand navigation panel.
  2. Click the ‘Create’ icon on the bottom right of the page.
  3. Give the Privacy Protocol a Name and Description.
    • Note: The Name and Description are all internal facing fields and will not be displayed to an end-user.
  4. Select a Protocol Type.
    • There are only two options: Consent or Communication Preference.
  5. Enable or disable respecting the Global Privacy Control Signal.
  6. Click the ‘Add Jurisdiction’ button to set up an individual consent or preference toggle.
    UC_add_jurisdiction.png
  7. In the title, enter the specific consent or preference text that is to be gathered.
    • Note: This is the privacy choice an end-user would see displayed on their Portal. All custom Privacy Protocols will have the button choice for ‘an Opt-In’ or ‘Opt-Out’ response.
  8. Enter a description of the consent or preference.
    • Note: This description will be displayed as help text to the end-user if they hover over the information icon.
  9. Select a jurisdiction from the dropdown that the consent of preference is tied to.
    • If the jurisdiction field is left blank, the consent or preference will be defaulted to be visible to any end-user regardless of their jurisdiction. 
    • Any given jurisdiction may only be tied to a consent/preference once in each protocol.
  10. Select a default action that is the default state of the privacy choice.
  11. Click ‘Save’.

Repeat steps 6- 11 until all jurisdictions and consent/preferences are complete. 

Update a Privacy Protocol

If there are updates or changes that need to be made within a Privacy Protocol, it is easy to make edits. Follow the steps below:

  1. Click into the specific Privacy Protocol that needs to be updated.
  2. Update the necessary field(s).
  3. Click the Save button.

Warning: Note changes affect the configurations using it and requires the configuration to be re-saved.