Okay
  Public Ticket #2635614
GDPR
Closed

Comments

  •  1
    Martin Grether started the conversation
    December 18, 2020 at 1:20am

    What is the best way to make the event-form GDPR-compatible? As we are collecting personal data, we need to get a consent.

  • [deleted] replied
    December 18, 2020 at 12:57pm

    Hello Martin, 

    You can try adding a custom field to the event for that purpose. You can check out instructions on how to create and add custom fields here, there are several types, and they can be mandatory in the booking process or not. 

    If you have any other questions or concerns feel free to open a new ticket and we will gladly help out. 


  •  1
    Martin Grether replied
    December 18, 2020 at 3:07pm

    With a lot of events this is not a good solution. is there a way to hook into that layout or use a child-theme template?

  • [deleted] replied
    December 18, 2020 at 6:22pm

    There are some JS hooks in Amelia, that are triggered depending on the view:

    window.beforeAddToCalendarLoaded()
window.beforeBookingLoaded()
window.beforeSearchLoaded()
window.beforeSearchFiltered()
window.afterSearchFiltered()
window.beforeConfirmedBooking()
window.beforeCatalogLoaded()
window.afterSelectCatalogCategory(object_category)
window.beforeCatalogCategoryLoaded(object_category)
window.beforeCatalogServiceLoaded(object_category, object_service)
window.afterSearchActivateService(object_appointment, object_serviceActive)
window.afterSearchGoToSecondStep(object_appointment, object_serviceActive)
window.afterBookingSelectDateAndTime(object_appointment, object_serviceId, object_providerId, object_locationId)
window.afterBookingSelectService(object_appointment, object_serviceId, object_providerId, object_locationId)
window.beforeConfirmBookingLoaded(object_appointment, object_service, object_provider, object_location)
window.afterConfirmBooking(object_appointment, object_service, object_provider, object_location)

     

    Not sure if they could be useful for that use case, but you can check if you can use one of these to achieve what you need.

    If you have any other questions or concerns feel free to open a new ticket and we will gladly help out. 


  •  1
    Martin Grether replied
    December 20, 2020 at 3:48pm

    i am not happy, that it is not possible to use this plugin according to the GDPR regulations. i tried to add a least a text within the last string before sending the form but here no html tags will be rendered. I feel lost here.

    #: src/Infrastructure/WP/Translations/FrontendStrings.php:74
    msgid "Base Price:"
    msgstr ""
    "Bitte das Eintrittsgeld vor Ort passend bereithalten. <br/>Mit dem Absenden "
    "der Daten erklären Sie sich damit einverstanden, dass Ihre Daten auf dieser "
    "Website gespeichert werden, damit wir auf Ihre Anfrage antworten können. "
    "Bitte lesen Sie unsere Datenschutzerklärung. Ihre Daten werden nach dem Ende "
    "der Veranstaltung gelöscht."


  •  1
    Martin Grether replied
    December 20, 2020 at 3:57pm

    OK, i am using a custom field now. Does that mean, that i have to add every new event manually?

  • [deleted] replied
    December 21, 2020 at 2:27pm

    Hello Martin, 

    Yes, the events need to be added manually to the custom fields in Amelia. There isn't another way of adding custom fields to service or events rather than adding/choosing them on the Amelia -> Customize page for the custom field in question. 

    Regarding GRPR compliance, in one of the version releases of Amelia, we added an option for customers to delete their data from the Customer panel, which makes Amelia GDPR compatible. 

    If you have any other questions or concerns feel free to open a new ticket and we will gladly help out.