Welding plugin privacy

The mobile weld request that photographs the broken gate and everything behind it

A welding WordPress stack is not only a job calendar. It is often a site survey in disguise. Every mobile-weld request can store photos of the broken gate, trailer hitch, or security grille, which show what the metal is protecting. Serial numbers and VINs inventory the equipment in the yard. The access window tells the shop when the yard is open and the rig is parked inside. Fabrication quotes can archive drawings of things that do not exist yet. A page request is not proof anyone booked. A gate photo is a stored file, not a property map. An access window is stored text, not proof anyone entered. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where job photos land, which inboxes receive copies, and how long past tickets, files, and backups are kept.

Documentation review only. This is not legal advice, a property-security claim, a demolition claim, a camera-coverage claim, a GDPR or other compliance assessment, or a judgment about welders.

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 gate photos, serial numbers, and weld bookings go

Entries, bookings, and uploads on your WordPress site

Check which gate-photo, hitch-photo, grille-photo, serial-number, VIN, access-window, fabrication-drawing, yard-open, or permit fields you enable, who can open form entries and service bookings, where uploaded job photos live in the uploads folder, which inboxes receive copies, and how long past tickets, files, and backups are kept after a call that never happened. Notification emails can also copy the same address, serial numbers, and photo 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 welder" badge is not a verified storage path.

Welding booking, gate-photo, and access-window 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 welding 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 mobile-weld window or a "yard open Saturday 7-11 — gate code 4412" access note is a booking you create; a service name such as welding or mobile weld is a label you configure. Neither is a documented default. Gate-photo, hitch-photo, grille-photo, serial-number, VIN, access-window, or fabrication-drawing 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 entry — and a CSV export of "gate code 4412 + broken-gate photo + VIN" next to a named owner is still a calendar that answers when the yard is open for a weld visit. 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.

Welding service 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. Gate-photo, hitch-photo, grille-photo, serial-number, VIN, access-window, fabrication-drawing, yard-open, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional job-photo uploads are files you accept; that file type is not a documented default. A gate photo is a stored file, not a property map. An access window is stored text, not proof anyone entered. A welding form is not proof anyone cut or welded on site. 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 gate photo sits after a call that never happened is not a documented default of the plugin.

Gate and equipment answers stored in WordPress; optional job-photo 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 gate photo or fabrication PDF is a file you accept; that file type is not a documented default. An uploaded gate photo is a stored file, not a property map. 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 job-photo file sits after a call that never happened is not a documented default of the plugin.

Job-photo and drawing 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. Gate-photo, hitch-photo, grille-photo, serial-number, VIN, access-window, fabrication-drawing, or yard-open fields often depend on the fields you configure. A gate photo is a stored file, not a property map. An access window is stored text, not proof anyone entered. A welding booking is not proof anyone cut or welded on site. A page request is not proof anyone booked. The page URL can say welding even when no form is submitted. Ask your web vendor who can open entries and uploads, whether job photos 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 fence maps, teardown, or camera diagrams. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.

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

Related pages

Scan your site for third-party requests

/wp-welding-plugin-privacy