For the RW contact form page type, change your form label to something like this:
I agree that my message will be sent and handled in accordance to the website <a href="https://example.com/terms" target="_blank">privacy policy <i class="fas fa-external-link-alt"></i></a><br>
Then you can make part of the label a link that will open in a new tab or window, like this:
The Font Awesome 5 icon shows to the user that the link opens in a new tab or window. So what they have entered in the form already wonât be lost if they click the link.
The actual rules (links branch out from here: http://ec.europa.eu/justice/smedataprotect/index_en.htm) My own (IANAL) reading is this: you do need a privacy policy page (because of rules in both the US and EU) but for a simple âsign me up for your newsletterâ where the only user input is an email address, you do -not- need a checkbox because the self-obvious case is that providing their email, is necessary to send it*. US law requires an âunsubscribeâ method at the bottom of each email however.
*if you were to also ask for their street address, or zip code, or phone, then you -would- need the checkbox because that other information is not necessary to send an email. I believe this is correct, but donât sue me if itâs wrong. Check for yourself.
Hereâs a direct quote from the GDPR rules:
" Individuals must know that you process their personal data and for which purpose.
But there is no need to inform individuals when they already have
information on how you will use the data, for instance, when a
customer asks you to do a home delivery."
As promised, CompactForm has been updated to include these new GDPR enhancements. This is a free update for all existing users of the stack.
A checkbox is now displayed at the bottom of the form, which a user must check, before the form is sent. If the user fails to click / accept this disclaimer, the form is not sent and an error message is displayed:
I have made the new setup as flexible as possible. The message text displayed is fully customisable. An optional link can be displayed after the text, which can open your website privacy policy in a new tab / browser window or display your privacy policy inside a lightbox - using a stack like FancyViewer or TopBox. The small icon appended after the link is a Font Awesome 5 icon, which will display in any themes that have Font Awesome 5 support. Alternatively you can use your own icon markup or an image.
This is a brilliant contact form and just what I have been looking for in a couple of Foundation sites to deal with GDPR compliance. If the user doesnât tick the agreement checkbox, it is flagged up so that the user is clear that the form wonât be sent without the agreement. This is probably the only contact form that any RW user would need. It is easy to understand and very flexible with all the customisation you would ever need. Instant purchase.
No it is not sent in the email. Only the existing inputs are sent in the email. Remember that the form can only be submitted if the consent checkbox is checked, so therefore every email you receive from this form you know for 100% sure has user consent.
In this update the subject line can be customised (if you do not want to use the one a user provides) so you could very easily include consent text in there if you prefer.
[EDIT] I should also add that when you reply to the email a customer sends you, ideally there should be a signature on the message which provides the normal legal disclaimer about the message being for the person intended and provides links again to your privacy policy / right to be forgotten etc.
Iâm using a foundation form base. I need it, because I have complex forms.
Itâs perfect, but no error message for the privacy policy required checkbox.
Is there any solution to this problem? (sorry for my english)
@emelon Thatâs just how the Foundation form works in my experience and I also reported this on the WS forums to Joe Workman.
If it helps, Willâs CompactForm does the checkbox correctly and a big red warning message appears if you donât tick the agreement and you canât send until the tick is applied - which is how it should be done.
