Gunsmith plugin privacy
The repair ticket that pairs a serial number with your name and home address
The work-order form builds a private firearms registry no law required — make, model, serial number, modifications, pickup name and home address — in a WordPress database. A breach does not just leak identity; it publishes a map of which houses hold which guns, and the repair notes characterize each one. Those fields are configured, not documented defaults. A gunsmith booking is a calendar row, not proof a firearm was repaired or returned. A serial or modification answer is a form answer or uploaded file, not a verified registry entry. A page request is not proof anyone booked a repair. The page URL can say gunsmith even when no form is submitted. Ask what happens to the name, the home address, the serial number, and the repair notes after a ticket closes — the stack that mapped a firearm to a house outlives the job. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking or quote page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a firearm-registration-legality claim, an FFL-compliance claim, an ATF-compliance claim, a background-check-validity claim, or a GDPR or other compliance assessment.
Scan your site for third-party requestsThe 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 gunsmith bookings, serial-to-address tickets, and page tags go
Bookings and repair tickets on your WordPress site
Check which make, model, serial, modification, pickup-name, home-address, or intake-upload fields you enable, who can open form entries and gunsmith bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a repair closes — when the name-plus-address-plus-serial row still holds a private firearms map next to a pickup window. Notification emails can also copy those fields off-site. One table can list every "Jordan · 12 Oak St · Remington 870 · serial ABC-123 · mods: choke · pickup Fri" stack next to a customer name. Ask your web vendor not to keep serial numbers and repair notes next to home addresses and pickup names in one open submissions list longer than operations need, and to purge those fields when a ticket closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored gunsmith booking is not proof a firearm was repaired or returned. A serial or modification answer is not a verified registry entry.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say gunsmith even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and quote pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "gunsmith privacy" badge is not a verified storage path.
Gunsmith booking, serial-to-address, and marketing-tag 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 gunsmith SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 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 Friday pickup window or a "serial intake" slot is a booking you create; a service name such as bore work or trigger job is a label you configure. Neither is a documented default. Make, model, serial, modification, pickup-name, or home-address questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof a firearm was repaired or returned — and a CSV export of "Jordan · 12 Oak St · Remington 870 · serial ABC-123 · mods: choke · pickup Fri" next to a customer name is still a calendar that pairs a serial number with a home address. 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. | Gunsmith bookings stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. Make, model, serial, modification, pickup-name, or home-address fields are fields you add; they are not documented defaults. Completing the form can store a name-plus-address-plus-serial stack ("Jordan · 12 Oak St · Remington 870 · serial ABC-123 · mods: choke · pickup Fri") — typed once so a shop can quote a repair, into the same tables as a "gunsmith" label. A serial or modification answer is a form answer or uploaded file, not a verified registry entry. A gunsmith booking is a calendar row, not proof a firearm was repaired or returned — and a staff login can open "Jordan, 12 Oak St, Remington 870, serial ABC-123, choke" next to everyone else's resume. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Name, address, and serial answers stored in WordPress; optional repair photos in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| PixelYourSite – Your smart PIXEL (TAG) & API Manager Documented pixel and tag manager (plugin version 11.4.2.1). When a Meta Pixel ID is saved, version 11.4.2.1 dist/scripts/public.js loads https://connect.facebook.net/en_US/fbevents.js. A noscript image uses https://www.facebook.com/tr. Google Analytics 4, Google Tag Manager, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that a serial, address, or modification field was sent. A page request from this script is not proof anyone booked a repair. The page URL can say gunsmith even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote pages. | Marketing tags handled through Meta, Google, or other configured platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Make, model, serial, modification, pickup-name, or home-address fields often depend on the fields you configure. A gunsmith booking is a calendar row, not proof a firearm was repaired or returned. A serial or modification answer is a form answer or uploaded file, not a verified registry entry. A marketing-tag page request is not proof anyone booked a repair. The page URL can say gunsmith even when no form is submitted. The name-plus-address-plus-serial row that mapped a firearm to a house for a shop — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that asset-registry stack, not a firearms-training class roster, a hunting-outfitter trip coordinate, or a pawn-shop collateral ledger. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or quote page, and how long records and backups are kept. A "gunsmith privacy" or "FFL ready" badge is not a verified storage path. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess firearm-registration legality, FFL compliance, or ATF compliance. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking and quote pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-gunsmith-plugin-privacy