Backflow testing plugin privacy

The compliance certificate that maps your water access points

A backflow-testing WordPress stack is not only a compliance calendar. It is often a map of every water access point on the property. Every certificate booking can store device locations, the date the tester ladder comes back, and a municipal deadline turned into a recurring appointment at the tap. A page request is not proof anyone booked. A device-location note is stored text, not a plumbing diagram. A return date is stored text, not proof anyone stood at the tap. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where certificate scans land, which inboxes receive copies, and how long past tickets, files, and backups are kept.

Documentation review only. This is not legal advice, a water-quality claim, a plumbing-code claim, a municipal-compliance assessment, a GDPR or other compliance assessment, or a judgment about testers.

Scan your site for third-party requests

The scan checks browser requests on the pages it visits. It cannot inspect form entries, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where device locations, certificates, and backflow bookings go

Entries, bookings, and uploads on your WordPress site

Check which access-point, device-location, test-certificate, municipal-deadline, return-date, property-address, owner-name, phone, email, or appointment-date fields you enable, who can open form entries and service bookings, where uploaded certificate scans live in the uploads folder, which inboxes receive copies, and how long past tickets, files, and backups are kept after a test that never happened. Notification emails can also copy the same address, dates, and file links off-site.

Uploads or connected destinations off your WordPress site

Some upload tools can send files to FTP, SFTP, or cloud destinations you enable. Review which destinations you turn on, account access, and retention there. A browser scan cannot inspect stored form entries, bookings, or who opened the service calendar. A certified-tester badge is not a verified storage path.

Backflow booking, certificate, and access-point setups

No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.

Three plugins reviewed from public documentation. Specialty backflow SaaS platforms without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A window such as "annual test due 15 May, ladder back 8am, device at hose bib east wall" is a booking you create; a service name such as backflow test or recertification is a label you configure. Neither is a documented default. Access-point, device-location, test-certificate, municipal-deadline, return-date, property-address, owner-name, phone, email, or appointment-date questions are custom fields you add (textarea, select, input, checkbox, or file); they are not documented defaults. A booking is a calendar row, not proof of work - and a CSV export of "due 15 May + hose bib east wall + ladder 8am" next to a named owner is still a calendar that answers when the crew is expected. Emails can include those custom fields and copy the appointment off-site. An optional GDPR setting can auto-remove customer data older than six months; that is not a default purge. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified.

Backflow testing bookings stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
Forminator Forms – Contact Form, Payment Form & Custom Form Builder

Documented self-hosted form builder (plugin version 1.58.1). The listing states Forminator stores and organizes submissions so you can sort, analyze, and manage responses, and includes a free file-upload field with multi-file support. Version 1.58.1 helper-fields.php forminator_upload_root() writes under the WordPress uploads directory plus /forminator/, with per-form hashed subfolders from forminator_get_upload_path(). upload.php stores files through that path. Access-point, device-location, test-certificate, municipal-deadline, return-date, property-address, owner-name, phone, email, or appointment-date questions are fields you add; they are not documented defaults. Optional certificate scan uploads are files you accept; that file type is not a documented default. A device-location note is stored text, not a plumbing diagram. A return date is stored text, not proof anyone stood at the tap. A backflow form is not proof anyone tested a device. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a certificate scan sits after a test that never happened is not a documented default of the plugin.

Certificate answers stored in WordPress; optional certificate-scan uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
Iptanus File Upload

Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. A certificate scan or device photo is a file you accept; that file type is not a documented default. An uploaded certificate scan is a stored file, not proof of the test. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. How long a certificate scan file sits after a test that never happened is not a documented default of the plugin.

Certificate-scan and device-photo uploads stored under the site wp-content pathBrowser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Access-point, device-location, test-certificate, municipal-deadline, or return-date fields often depend on the fields you configure. A device-location note is stored text, not a plumbing diagram. A return date is stored text, not proof anyone stood at the tap. A backflow booking is not proof anyone tested a device. A page request is not proof anyone booked. The page URL can say backflow even when no form is submitted. Ask your web vendor who can open entries and uploads, whether certificate scans remain reachable by direct URL, and how long records and backups are kept. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess plumbing emergencies or irrigation controllers. Review stored records, uploaded files, connected services, exports, notification emails, and backups.

Documentation snapshot: Oct 21, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-backflow-testing-plugin-privacy