Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 COPPA | Event Espresso - Staging Server
As far as I can interpret (http://www.coppa.org/comply.htm), all you need is a link to your privacy policy if you are collecting information for internal use only.
No according to coppa you can not gather personal information electronically from anyone under 13 years old. Since my events are open to all ages, I need to make sure a 13 year cannot submit their email address or phone number.
Typically on a form for instance, you can have users enter a birthday and redirect them if they are under 13.
Typically on a form for instance, you can have users enter a birthday and redirect them if they are under 13
That’s not necessarily true. I’ve seen lots of forms that simply have a checkbox saying “I acknowledge that I am over 13 years of age” (or whatever age requirement). That is something that’s possible with Event Espresso. Just create a required question with that as the “question” and only one response (I acknowledge).
Would it work to only ask for a Parent or Guardians email address?
I’ve created a feature request ticket so the dev team is aware of this issue. If the only way to make the registration form COPPA compliant is to redirect someone away from the form by using an age selection question, then it would involve some custom development. At the very least, some custom jQuery could be added to add some “Age” validation, and not allow the form to be submitted if it didn’t meet the criteria.
Viewing 5 reply threads
The support post ‘COPPA’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.