You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, the fields for first and last names are mandatory and cannot be disabled. However, there are events where organizers prefer to collect only the nickname of attendees to ensure better personal data protection.
Describe the solution you'd like
I propose that the first and last name questions can be made optional via the admin panel for an event. This would allow organizers to opt-out of collecting this information if it's not necessary for their event.
Describe alternatives you've considered
Using Dummy Data: One alternative is to instruct attendees to input dummy data for the first and last name fields. However, this is not user-friendly and can lead to inconsistent data.
Manual Data Cleaning: Another option is to collect the data as-is and manually remove or anonymize the first and last names afterward. This approach is labor-intensive and prone to errors.
Additional Context
Making these fields optional will help in enhancing privacy and complying with data protection standards for events where full names are not required.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, the fields for first and last names are mandatory and cannot be disabled. However, there are events where organizers prefer to collect only the nickname of attendees to ensure better personal data protection.
Describe the solution you'd like
I propose that the first and last name questions can be made optional via the admin panel for an event. This would allow organizers to opt-out of collecting this information if it's not necessary for their event.
Describe alternatives you've considered
Additional Context
Making these fields optional will help in enhancing privacy and complying with data protection standards for events where full names are not required.
The text was updated successfully, but these errors were encountered: