GDPR & Engaging Networks

Have you seen our report? Form blocks - Only ask for the data you need to ask for Dependencies and Code blocks allow you to show/hide fields and messages depending on supporter interaction, or record extra pieces of info (e.g. opt-in text) Address lookup, google tag manager Validation ?

? Flexibility Templates Form fields, questions & opt-ins Code blocks Form blocks - Only ask for the data you need to ask for Dependencies and Code blocks allow you to show/hide fields and messages depending on supporter interaction, or record extra pieces of info (e.g. opt-in text) Address lookup, google tag manager Validation Why is this important for GDPR? Right to be informed Data protection by design and default ?

? Code examples: javascript / regex… Number only: ^(0[0-9]{9})?$ <p>Are you sure you don’t want to receive emails from us?<p> <div class="en__component en__component--codeblock"><script> checkOptIn(); $(".en__field—OPT IN-").click(function() { checkOptIn () }); function checkOptIn() { if ( $(".en__field—OPT IN- input[value='N']" ).is(':checked') ) { $(".checkOptIn").show(); } else { $(".checkOptIn").hide(); } } Form blocks - Only ask for the data you need to ask for Dependencies and Code blocks allow you to show/hide fields and messages depending on supporter interaction, or record extra pieces of info (e.g. opt-in text) Address lookup, google tag manager Validation Number only: ^(0[0-9]{9})?$ Address validator: ^[a-zA-Z0-9\/ ,.'’]*$ Added in pages > alerts & validators ?

? Opt-ins Why is this important for GDPR? Right to be informed Consent managed via opt-in questions Should be able to cope with multiple opt-ins Shared components to quickly allow for copy updates Opt-ins One key component of GDPR is the Lawful basis for processing: Consent. In particular, you must “Keep evidence of consent – who, when, how, and what you told people”. The design of our opt-in functionality means you are keeping an audit log of consent that you can export at any time. Multiple You are advises to “Be specific and ‘granular’ so that you get separate consent for separate supporter activities. Vague or blanket consent is not enough.” You can create your opt-ins to make each specific to channel or content, thereby collecting separate consent for separate activities. Shared components >> why important for GDPR? For Lawful basis for processing: Consent, you should “Check your consent practices and your existing consents. Refresh your consents if they don’t meet the GDPR standard.” Shared components ensure your changes are immediately applied to all your live pages and can be used to display information and cover the GDPR’s Right to be informed. Screen show Why is this important for GDPR? Right to be informed Evidence of consent - who, when, how & what Be specific and granular ?

? Settings Why is this important for GDPR? Question settings (radio, check box, double opt in etc) Account-wide settings to customise options whilst maintaining as many supporters as possible Opt-in settings per question Account settings for opt-ins Account settings for ETTs Opt-in question settings >>> Why is this important for GDPR? GDPR says that “Consent requires a positive opt-in. Don’t use pre-ticked boxes or any other method of default consent.” and “Avoid making consent to processing a precondition of a service.”. If you are using a checkbox for your opt-in, uncheck the “pre-tick”option so it will display unchecked on a page. If you use a radio HTML format for your opt-in, then you do not have to have any of the two options pre-selected. Making this question mandatory will mean the supporter is prompted to choose an option, but do not have to choose Yes to continue. Account settings >>> Why is this important for GDPR? Ensuring you do not lose supporters as a result of tightening your opt-in procedures in response to GDPR and Consent is vital. These tools, and ones in development in response to client discussions, will help ensure this. Email to target The settings you choose will help ensure your supporters’ right to be informed is adhered to and that you are following the concept of data protection by design and default. Why is this important for GDPR? Consent: Don’t use pre-ticked boxes Consent: Avoid making it a precondition Right to be informed on what you store Data protection by design and default ?

? What about email unsubscribes? Direct unsubscribe links, or Subscription management pages Why is this important for GDPR? Consent: make it easy for people to withdraw consent and tell them how ?

? Data management Why is this important for GDPR? Supporter & transactional data Amendment of data individually or in batches Data export Why is this important for GDPR? Management: Right to rectification Source data: Right to be informed Deletion of data: Right to erasure Exports: Right to portability & access ?

? Supporter self-management Supporters should be able to access & amend their own data at any time Why is this important for GDPR? Consent Right to rectification Right to access ?

? Marketing automation Why is this important for GDPR? Consent Automate reactivation processes You might want to automatically check in with supporters to ensure consent ? Why is this important for GDPR? Consent

? Security Why is this important for GDPR? Security policies and documentation Plans for entry and exit of data - and user access Permission groups and data views for users Secure certificate (https) ? Why is this important for GDPR? Data protection and security will be a key requirement

? What’s coming? Two-factor authentication: security ‘QCBs’ exposed under Transaction History gadget (both imports and general page): consent Opt in statement will also be exposed: consent WYSIWYG for opt-in questions: informed ?

You’ll need to resave your opt-ins What’s coming? ? Import file or page You’ll need to resave your opt-ins

More information  support@engagingnetworks.community  support.engagingnetworks.net  engagingnetworks.academy  020 7253 0753