Just so that we are clear, Brian and I and the other support team members have beat this opt-in topic up over and over many times. There have been reviews of applicable regulations by professionals (& TM WHQ), and we have considered many different approaches. What we have now is a "best case compromise", all things considered.
1. Everyone needs to opt-in to the website system one way or another. We need to have basic information in our system database that indicates when they opted-in and demonstrates that they actually did so.
2. The applicable regulations define roles. The clubs have a role that is different than the one we have. (We are essentially a data "processor".) We cannot ensure that clubs are fulfilling their roles correctly--we can only ensure that we fulfill our role. This is why it is not sufficient for the clubs to just use their opt-in processes in lieu of ours. Clubs/districts should have their appropriate opt-in processes, but the FTH system still needs to have its own opt-in process. Also, we need to control the verbiage that is most relevant to us and the FTH system. Clubs sometimes like to pretend that the FTH system is not really there behind the scenes providing the underpinnings of their website, but in reality, they can only go so far with that--FTH is there behind the scenes, and we must ensure that every user follows the rules of its use and does not cause a problem for the system as a whole.
3. You need to trust that we have done our homework on this--Brian, in particular, has read up on this quite a bit. We get this whole opt-in thing brought up periodically by people that have not done their homework, have not reviewed and discussed this as much as we have, and yet think they know better than us. It is certainly possible that we have missed something or unaware of a new regulatory wrinkle, but do not discount all the investigation we already have done in in the past.
4. To be clear, we really were not that enthusiastic about adding the opt-in functionality in the past--we were essentially forced into it by the changing data privacy regulatory landscape. We knew opt-in would be cause for a lot of push back. If you had the chance to read some of the initial posts when we implemented it, you would have seen that.
However, part of what we do is to implement functionality that is not just what users want, but also what is needed to keep the system viable and usable for all users, not just the ones that are the most vocal.