Handle express consent in a way that doesn't jeopardize our database
Under CASL, when Canadian organizations offer the option to subscribe to email communications, the subscription checkbox must not be pre-checked. The current issue with Luminate is that if a constituent has already provided express consent, they must re-check that box each time they have an interaction with a Luminate form on your site (whether that’s a donation form, event registration form, TeamRaiser event, etc.). We need to be able to include an unchecked email-subscription checkbox on our forms, etc., without the risk of unintentionally losing constituents who don’t resupply express consent each time they complete a form (which happens regularly as people come back to make new donations or participate in our variety of monthly workshops).
We need this solution to be easy to implement and duplicate (i.e. the solution must be intuitive enough that someone with only basic computer literacy could handle). Many of the employees responsible for key features of the system (like event registration and donation management) only have basic computer literacy.
-
Guest
- Dec 21 2015
- Reviewed: Need Further Info
| Area of the Product | Database |
| Org/Company Name | Alzheimer Society of Toronto |
Related ideas
Also, if this request is to productize what I described above instead of having our services team handle it then let me know I will mark this idea as such. Otherwise if I've answered your question I'll mark as having a solution that already exists.
Thanks,
Ken
Hi Jovan,
The solution to your issue while also abiding by CASL is to require your constituents to be logged in so the system knows who they are and what their previous preference was. If they aren't logged in and the form must be unchecked by default then there is no way of telling if they are intentionally opting out or if they just didn't realize the box was unchecked.
We recommend auto-logging in your constituents from emails when pushing them toward taking actions like this. If there areas of LO which do not automatically have that box reflecting a logged in users' current preference by default you can talk with our services team about the possibility of writing some code that lives in the pagewrapper which will check that box accordingly. Once set this solution wouldn't require maintenance by your team. If you are interested you can reach out to your CSM to start that scoping process.
Thanks,
Ken