Hi Everyone,
There appears to be a make-or-break issue for our club (Famous Toastmasters Mainz, Germany) regarding using FreeToastHost and I would like to check that this is not a misunderstanding on my part before sadly having to walk away and close our account. From my personal point of view it is a good system, but lacks one feature that is considered essential by some members.
The feature that EasySpeak offers to see who has signed up for: attend the meeting/will not attend/uncertain seems to be crucial for some members. It appears that on FreeTastHost the TM of the day (and sys admin) can see this, but not other members. Is this correct?
Names of people who have signed up for roles are openly published in the Agenda. Could a list of members and their intention to attend be added? Having worked (briefly) with GDPR and read the GDPR document cover-to-cover it is clear that there is no objection to listing the name of club members planning to attend or not - this is not "sensitive information" as defined in the GDPR. Again, as far as I can see, publishing the name of a club member to other club members does not have any implications at all for GDPR, and indeed EasySpeak publishes this list openly to all internet web users. (And we should remember that GDPR does not care if this information is electronic or written on paper - the same rules apply). The TM of the day can access this information and re-post to all club members but this is so inconvenient as to be unworkable. If this function could be automated and a list of members planning to attend, planning to not attend, or uncertain, could be automatically sent that might be a solution. But including this list for signed-up members to see on the website would be ideal.
Without a resolution of this issue it is likely that club members will reject the move to FreeToastHost and the club will have to continue to use EasySpeak.
Thanks for any feedback/comments - or even better, a workaround.
Russell.
Sys Admin Famous Toastmasters Mainz sysadmin9730@freetoasthost
The topic has been locked.