=== NET360 Form Builder ===
Contributors: net360pe
Donate link: https://www.paypal.com/ncp/payment/R2L6JRLUD6LGJ
Tags: forms, contact form, form builder, recaptcha
Requires at least: 6.2
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.9.30
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Create, publish, and manage WordPress forms and submissions from one place.

== Description ==

NET360 Form Builder is a visual WordPress form builder with submission management, conditional fields, AJAX submission, per-form styling, email notifications, CC and BCC recipients, autoresponders, Google reCAPTCHA v2, and Excel export.

The plugin includes a responsive email notification layout designed for desktop and mobile devices.

Developed by NET360.pe.

== Features ==

* Visual form builder.
* Conditional fields with multiple rules.
* Independent conditional fields.
* AJAX submission support.
* Submission management with search and filters.
* Submission status management.
* Excel export by form and date range.
* Separate email, CC, and BCC notification recipients.
* Responsive HTML email notifications.
* Record ID, form name, and date/time in notification subjects.
* Autoresponder emails.
* Google reCAPTCHA v2 Checkbox.
* Per-form styling and layout controls.
* File upload fields.
* Form duplication.
* Responsive frontend forms.

== Installation ==

1. Upload the `net360-form-builder` folder to `/wp-content/plugins/` or install the ZIP from the WordPress Plugins screen.
2. Activate NET360 Form Builder from the Plugins screen.
3. Open **NET360 Form Builder** in the WordPress administration menu.
4. Create a form and place its shortcode on any page or post.

== Frequently Asked Questions ==

= How do I display a form? =

Use the shortcode generated by the form builder, for example `[360_form id="1"]`.

= Where are submissions stored? =

When submission storage is enabled, submissions are stored in the plugin database tables and can be managed from **NET360 Form Builder → Registros**.

= Can I export submissions? =

Yes. Submissions can be exported to an Excel-compatible file and filtered by form and date range.

= Can I send notifications to CC and BCC recipients? =

Yes. Each form can define the main administrator recipient, additional recipients, CC recipients, and BCC recipients.


== External services ==

This plugin can optionally use Google reCAPTCHA v2 Checkbox to protect forms from spam and automated abuse. Google reCAPTCHA is disabled by default and is only loaded on pages containing a form when the site administrator enables it and configures a reCAPTCHA Site Key.

When reCAPTCHA is enabled for a form, the plugin loads the Google reCAPTCHA JavaScript library from `https://www.google.com/recaptcha/api.js` only when that form is rendered. When that form is submitted, the plugin sends the reCAPTCHA response token to Google at `https://www.google.com/recaptcha/api/siteverify`. The plugin does not send the visitor IP address to Google as part of its server-side verification request. Google may process device, application, and other information as described in its reCAPTCHA documentation and applicable terms. Site owners are responsible for providing any notices or obtaining any consent required by applicable privacy laws.

Service provider: Google LLC.

* [Google reCAPTCHA](https://www.google.com/recaptcha/)
* [Google reCAPTCHA documentation](https://docs.cloud.google.com/recaptcha/docs)
* [Google Privacy Policy](https://policies.google.com/privacy)
* [Google Terms of Service](https://policies.google.com/terms)

== Source code ==

The plugin's PHP, JavaScript, CSS, and other source files are included in the distributed plugin. The frontend JavaScript source is included in both `src/forms.js` and `public/assets/js/forms.js` in human-readable form. The distributed files do not require a build step to run.

== Privacy ==

When submission storage is enabled, the plugin stores the form data submitted by visitors so site administrators can manage submissions. New submissions do not store the visitor IP address or HTTP referrer URL. The plugin does not include analytics, advertising trackers, or telemetry. If Google reCAPTCHA is enabled, Google receives the information required to provide the reCAPTCHA service as described above.

== Changelog ==

= 1.9.30 =
* Hardened administrative input handling and aligned all internal version references with the NET360 Form Builder identity.

= 1.9.27 =
* Updated the administrative visual branding while retaining NET360 Form Builder as the official plugin name and WordPress.org identity.

= 1.9.26 =
* Updated the plugin display name to NET360 Form Builder and aligned the translation text domain with the assigned WordPress.org slug.
* Improved input sanitization for form definitions and settings before database persistence.
* Removed stored visitor IP addresses and referrer URLs from new submissions.
* Documented Google reCAPTCHA external service usage and included readable frontend source code.

= 1.9.14 =
* Improved WordPress security and Plugin Check compatibility.
* Escaped administrative output consistently.
* Improved database query handling for dynamic table names and prepared values.
* Added the required Tested up to readme header.
* Updated the readme content to standard English for WordPress.org.
* Preserved the existing plugin functionality and database schema.

= 1.9.13 =
* Updated WordPress.org author metadata while retaining `net360pe` as the contributor account.
* Maintained the official plugin page and PayPal donation link.

= 1.9.12 =
* Fixed administrative asset loading after the administration slug migration.

= 1.9.10 =
* Improved responsive email notification layout for mobile devices.

= 1.9.9 =
* Added the submission ID, form name, and date/time to notification email subjects.

= 1.9.6 =
* Improved Excel export so each form field is exported in its own column.
* Removed the Status column from the exported file.

= 1.9.4 =
* Added Excel-compatible submission export with form and date filters.

== Upgrade Notice ==

= 1.9.26 =
Updated identity, security hardening, source documentation, and WordPress.org compatibility improvements.
Security and WordPress.org compatibility improvements. Existing forms, submissions, email settings, CC/BCC settings, and database tables are preserved.
