It’s worth mentioning that the examples shown below are best case scenarios should you be able to achieve them. GDPR is not an aggressive law that is looking to fine and penalise everyone, causing businesses and marketing agencies (such as this one) to be constantly on edge over data. As long as you have your own versions of the below in place with the key learnings taken from the examples, you will be well on your way to being compliant with the change in data protection laws.<\/p>\n
Location Services Request – Choice Modal<\/h3>\n
Typically occurring during mobile sign up due to apps wanting to use location for a number of reasons (availability of services in local area, international restrictions, GPS\/positioning for maps etc), this option to share your location should now also come with information about what will happen to this data when it has been stored.<\/p>\n
![\"\"](\"http:\/\/projectsimply.com\/assets\/dos-donts-gdpr-blog-2.jpg\")
<\/p>\n
In the choices above, the “Existing” iteration shows that currently, it is designed in such a way to influence you to quickly click the “yes” option and move on without fully reading the information regarding what you are consenting to. In the “Improved” version, you can see that the colours have been equalled across both boxes to ensure no bias in selection. There has also been a link added to an external page that explains to the user what the location based feature is. This page will typically be the privacy policy that explains the feature, what the data is collected for, how it is used and the rights the user has if they want to be forgotten about.<\/p>\n
Data Requests, Right to rectification and Right to erasure<\/h3>\n
The next part concerns subscription centres and the ability to give the control of your users’ data to the user directly. This section doesn’t necessarily compare an existing vs an improved scope for design but rather shows a “minimum” standard compared to an “ideal” design for a subscription centre-style account setting.<\/p>\n
![\"\"](\"http:\/\/projectsimply.com\/assets\/dos-donts-gdpr-blog-4.jpg\")
<\/p>\n
For the minimum requirement, within the privacy policy page you should give clear and accurate information about who in your organisation the user needs to contact in order to request information about what data you hold about them, ask for amendments to be made or to ask for all data to be erased completely (unless it is legally impossible to do so).<\/p>\n
In the “Ideal” scenario, there is a special section reserved in the user’s account where they can view their data and consent information. As you can see in the images above, it is clear who the user needs to contact for information about what data is held about them and the user can also see on-screen what information has been stored about them. There are also clear instructions on how to edit and delete information in the online system.<\/p>\n
Finally you can see that there is a subscription settings section that allows the user to change what they have previously consented to receive. This can all then be saved to be reviewed again at any time the user wishes.<\/p>\n
The main benefit to having the “Ideal” set up is that it greatly reduces admin and processing time on behalf of the organisation. If the user can do all of this themselves then this saves a huge amount of time auditing, searching and amending data as well as documenting the process for GDPR reasons.<\/p>\n
Gaining Consent<\/h3>\n
The differences between the existing and the improved forms here are quite drastic on first glance but don’t let that put you off.<\/p>\n
![\"\"](\"http:\/\/projectsimply.com\/assets\/dos-donts-gdpr-blog-3.jpg\")
<\/p>\n
The first thing to notice about the “Existing” form is that there is a “negative” checkbox. What this means is that the user has to check the box if they don’t want to be notified about new offers. Under GDPR this is a very clear breach in that the new law states you must make it clear and obvious what the user is doing when they are signing up to something or offering their consent to be send information in the future.<\/p>\n
In the “Improved” section, you can see that it is explained early on to the user what their email address will be used for and a link to the privacy policy. It is then clearly explained under “Contact Permission” what the data will be used for as well as giving the visitor clear and obvious options as to which types of information (if any) they would like to receive. There is also then a notice that the user must agree to the terms and conditions if they wish to use the website.<\/p>\n
Opt-out vs Explicit Opt-in<\/h3>\n
In this example, we see an extension of the types of consent offered in the previous “Gaining Consent” section. As you can see by the previous form, there is a simple “Do not notify me about new offers” checkbox which as aforementioned, is a negative way for someone to opt-out.<\/p>\n
We also see that it has been attempted to include opt-in\/opt-out consent information for GDPR purposes but the non-compliant element is the checkbox that is stating that for someone to opt-out, they must check the box.<\/p>\n
<\/p>\n
![\"\"](\"http:\/\/projectsimply.com\/assets\/dos-donts-gdpr-blog-5-new.jpg\")
<\/p>\n
Another element to take note of in this particular example is that the consent it is seeking is to allow the company to share information with 3rd parties. The “Improved” example here explains in greater detail that data will not be sold to 3rd parties if you do not consent for this to happen and there is a very clear Yes\/No option to the checkboxes. There is also a link back to a privacy policy that will explain this in more detail.<\/p>\n
Another detail here is that the box to continue or submit this information is “greyed out” and will only be available to click once you have entered a response to the consent question.<\/p>\n","protected":false},"excerpt":{"rendered":"
The Do’s and Don’t of GDPR compliance including examples of forms There is a lot of information floating around the internet about what GDPR is, why it is being implemented and the astronomical fines that you could potentially incur for the most serious cases of negligence involving personal data. However what is lacking is the…<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,4],"_links":{"self":[{"href":"https:\/\/projectsimply.com\/wp-json\/wp\/v2\/posts\/1989"}],"collection":[{"href":"https:\/\/projectsimply.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/projectsimply.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/projectsimply.com\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/projectsimply.com\/wp-json\/wp\/v2\/comments?post=1989"}],"version-history":[{"count":0,"href":"https:\/\/projectsimply.com\/wp-json\/wp\/v2\/posts\/1989\/revisions"}],"wp:attachment":[{"href":"https:\/\/projectsimply.com\/wp-json\/wp\/v2\/media?parent=1989"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/projectsimply.com\/wp-json\/wp\/v2\/categories?post=1989"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}