0151 355 4555

Understanding the provenance of your data

GDPR is a complex and wide-ranging topic, but some key elements that will directly impact your CRM are the requirement for recording consent and implementing the right to erasure. data8 provenance targets these areas of GDPR in Microsoft Dynamics 365. It offers the ability to quickly record consent as it is given or withdrawn, and enforce those consents in your use of CRM for marketing. It also allows you to erase personal information without the problems that come from deleting records outright.
 

Recording Consent

Store consent as it is given or withdrawn and build up an audit trail that can be referred to in case of any future disputes. 

Hierarchical Consent

Arrange your consentable elements into hierarchies to make it simple to gather and withdraw consent at the appropriate level, e.g. get consent for all emails and withdraw it later, just for your monthly newsletter. 

Traceable Consent

Link your consent records to where the consent was gathered from, making it simpler to justify if challenged in the future. 

Timestamped Consent

Each consent record is timestamped and builds on earlier records, so you can quickly see what consent you had at any point in time. 

Merging Data Subjects

If you merge leads or contacts, the consent you have gathered travels with them so it’s still clear whether or not you have consent on the new record.

Recording Processing Grounds 

Record the grounds under GDPR that you are processing a marketing list (consent, legitimate interest etc.) so all bulk data processing can be justified with appropriate Privacy Impact Assessments. 

Failsafe List Filtering 

Ensure your marketing automation users can only see a filtered view of marketing lists, excluding any records that do not have the appropriate consent. 

Right to Erasure 

Implement the right to be forgotten without retaining personal information, or deleting your records. 

Configurable

Select which fields hold personal data and they can be either erased or securely hashed when the right to be forgotten is invoked. 

Prevent Re-Importing

Use a hashed key field such as email address to prevent data being accidentally re-imported in the future after the data subject has asked for it to be erased.

data8 duplicare™ & data8 provenance™

When used together data8 provenance and data8 duplicare will provide a data governance protocol for data integrity and consent management by reducing the amount duplicate records with conflicting consent statements. Together they also allow users to manage the health of your data against GDPR by auditing the data and producing GDPR Red Flags based upon any conflicting consent statements. 

Reactivate Erased Records 

Using data8 duplicare™ with data8 provenance™, when a previously erased individual re-engages with you, you can quickly find and reactivate the previously erased record and re-populate the personal data fields.


Ring me back!

Need information or help? Let us know..