In an effort to provide your organization with the best experience possible, Sourcepoint continually releases new features, updates, and bug fixes for our Consent Management Platform (CMP). Below are the most recent updates to CMP:
Sourcepoint is excited to introduce Privacy Check functionality to the Privacy Manager builder for GDPR TCF v2. As an additional checkpoint in the configuration of your GDPR TCF v2 consent experience, we hope this new functionality can further help your organization ensure compliancy. Click here to learn more.
The line items for the Privacy Check for GDPR TCF v2 Privacy Manager are as follows:
Vendors processing personal data on the basis of Legitimate Interest
Right to object to Legitimate Interest Processing
Manually completing the Privacy Check is a prerequisite to launching a new GDPR TCF v2 campaign
Restrict Privacy Manager Deletion (GDPR TCF v2)
In addition to recently implemented guardrails for Privacy Manager, we have implemented a new rule that protects Privacy Managers from deletion if it is linked to a First Layer Message. This new rule was implemented to ensure that Privacy Managers are not inadvertently deleted while they are being utilized by a First Layer Message.
Enforce Privacy Check for First Layer Message and Privacy Manager Before Campaign Launch (GDPR TCF v2)
In order to protect your organization from launching non-compliant GDPR TCF v2 experiences, Sourcepoint is enforcing Privacy Check for both First Layer Message and Privacy Manager as a prerequisite to launching a campaign.
We are currently aware of an issue where an incomplete Privacy Check for Privacy Managers is failing to block the launch of a Campaign. We are investigating.
Update to Privacy Check for First Layer Message
We have performed the following updates to Privacy Check for First Layer Messages:
Removed a duplicate line item for Example of personal data
Added Direct Link to Vendors as a new line item
We recently updated the GDPR TCF v2 Android SDK so that your mobile developers can serve a consent experience in a specific language to the end-user rather than relying on the default language setting of the webview. Add the following setter to the ConsentLibBuilder to configure this update:
.setMessageLanguage(MessageLanguage.messageLangauge)//replace parameter with desired language
If the selected parameter is not available than the message experience will automatically default to the configured default language for the message.
We recently fixed a reported issue where vendors who only supported Special Purposes and Features were appearing in Privacy Manager with opt-in/opt-out toggles. We have fixed the issue and apologize for any inconvenience this may have caused.
When adding cookies to a vendor with different categories but with the same name should now successfully save for the vendor.