Advanced Forms for ACF vs GDPress

Documentation | Purchase Pro Advanced Forms is a WordPress plugin for creating front-end forms using Advanced Custom Fields. It supports all ACF field types, including repeaters and flexible content fields, and provides the same field editing interface you are already familiar with. Advanced Forms requires ACF PRO v5.7 or later. Email notifications: Configure an unlimited number of email notifications, including support for dynamic recipients and field includes. AJAX submissions: Use AJAX for a better user experience with faster submissions and no page reloads. Entries: Save form submissions as entries with all fields. Spam protection: Every form is protected against spam using a honeypot. If you need more sophisticated spam protection, Advanced Forms Pro includes support for reCAPTCHA. Restrictions: Place limits on your form using the built-in restrictions or create your own: Limit the total number of submissions Limit your form to only logged-in users Limit the time when your form can be used User-friendly UI: Create forms either through the admin panel or programmatically for easy integration. Gutenberg support: Add forms to your site using Gutenberg blocks. Developer-friendly: Designed for developers with a large variety of hooks and helper functions and comprehensive documentation. Pro On top of that, Advanced Forms Pro offers even more features for advanced use cases. You can purchase a license through Hookturn which can be used on an unlimited number of sites. Priority support: Get direct support with an average response time of 1-2 days. Post editing: Set up forms to create and edit posts. Configure the post title, content and status and automatically map your existing ACF fields. User editing: Register new users or let people edit their user profile with automatic mapping of your user fields. Calculated fields: Give your users immediate feedback as they fill out your form. Calculated fields update live with the values from other fields. Calculated fields are also fully programmable for more complex calculations. Slack: Get a message in Slack for each form submission, including all form data. Mailchimp: Create a form to sign users up for your Mailchimp mailing list. Zapier: Connect your form to thousands of third-party services using Zapier. Google reCAPTCHA: Protect your forms against spam using an invisible captcha. Support If you need help, have a feature request, or think you’ve found a bug, don’t hesitate to reach out. Either create a ticket on the WordPress Support Forums or an issue on Github. For Pro users, please send an email to [email protected] and we’ll respond as fast as we can, most often within 1-2 days. Documentation The documentation has been moved to a new site, check it out: advancedforms.github.io

GDPress is providing tools for privacy and more. Major features in GDPress include : a privacy request form a menu in the admin_bar to see at once confirmed privacy requests and since version 2.0 a set of tools to help you comply with GDPR * a set of protection and wellness tools, because protecting personal data starts with a healthy and protected installation to prevent potential data breach. * a RoPA assistant to help you building your Records of Processing Activities – a GDPR obligation (Article 30). * a logging of all events related to export/erase requests by/for the data subject (see settings page). * a specific wp role for dpo. * and a dedicated Privacy/GDPR/ISO27701 dashboard for your d.p.o. ! GDPR compliancy is a never ending process. Technical Details n/a Privacy GDPress is not calling any external web services and is not using any external software other than WordPress core. GDPress stores events related to the data subject and core privacy processes if archive setting is set. Archives are under the authority of the Data Protection Officer for legal purpose ONLY. They are retrieved to the data subject, but not deleted. Accountability/Auditability These are legal obligations in GDPR. In front of your local data protection authority or a judge : * You are accountable of your actions to reach GDPR compliancy and must prove it (activating this plugin is not enough). * If sued, you will have to provide some evidence : you acted lawfully and replied to the request of the data subject (archive all activities for Legal Purpose is allowed in GDPR and must be declared in your Records of Processing Activities). Other Major Obligations Records of Processing Activities, expecting WordPress team to publish it for core. And for any theme or plugin, adding a new Privacy Section in readme.txt is a must do. Communication of a personal data breach to the data subject (and to your local D.P.A.) Privacy by design This concept is in GDPR too. In wp, Privacy is a component like Gutenberg, Admin, wp-cron … Privacy by design is or should be declined and included in ALL wp components. Should all components publish their “Privacy Section” just like the above recommandation for themes and plugins ? Pending Questions Privacy settings in core : only one setting on a unique page that cannot be amended (no hook) : the privacy policy page any privacy request is a personal data and should be retrieved to the data subject removing an export request do not delete the export file (security issue, potential data breach) external processors to be identified (privacy by design) Gutenberg blocks coherence with embed handlers and oembed providers as set on the server side (privacy by design) oEmbed responses cached in transients (no more postmeta html cached) for blog posts or oembed providers (privacy by design) ability to remove blocks in Gutenberg such as “/map” for Mapbox (privacy by design) future “Icon” component : from Dashicons to svg (privacy by design) Nowadays, emails such as “θσερ@εχαμπλε.ψομ” are valid but rejected by wp function is_email() (privacy requests rejected) Web standards should apply and this can be a legal issue : one of the “variety of privacy issues around the world” !