Firearms training plugin privacy
Where does the class roster that maps the armed households go?
A firearms-training or concealed-carry-class signup can ask for name, home address, date of birth, sometimes a permit-application number, and an emergency contact. Each row pairs a home address with strong evidence a firearm lives there — and the class date tells you roughly when the permit paperwork started. Aggregated, a small range's booking table is a neighborhood map of armed households, held in WordPress tables behind one admin login. The roster also says where the owner is every Saturday morning. A marketing tag on the same page can send a page request to a vendor host before anyone submits. A page request is not proof that anyone enrolled. A signup is not proof of firearm ownership or permit issuance. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries, where uploaded files land, which tags load on the signup page, and how long records, files, and backups are kept.
Documentation review only. This is not legal advice, a Second Amendment assessment, an ATF assessment, a state-permit-law assessment, a firearms-law assessment, a carry-permit assessment, a training-requirement 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 class roster fields and page tags go
Entries and bookings handled on your WordPress site
Check which name, home-address, date-of-birth, permit-application-number, or emergency-contact fields you enable, who can open form entries and bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a signup that never became a completed class. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect a home address next to a class time on the first public form, and not to store permit-application numbers in one open submissions list.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the firearms-training signup page. That page request can reach a vendor host before anyone submits — and a third party can learn that someone sought concealed-carry training. Review which tags you enable, account access, and retention there. Keep marketing tags off signup pages if you do not want that page request. A browser scan cannot inspect stored form entries. A "secure client forms" badge is not a verified storage path.
Firearms-training booking, form, 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 range SaaS platforms 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 booking and intake (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 Saturday CCW or firearms-training class slot is a booking you create; a service name such as concealed carry class is a label you configure. Neither is a documented default. Name, home address, date of birth, permit-application number, or emergency-contact fields are custom fields you add (textarea, select, or input); they are not documented defaults. A signup is not proof of firearm ownership or permit issuance. Notes can store a home address next to a class time that shows when the owner may be away. Emails can include those custom fields. 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. | Class-slot bookings and custom intake fields 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. Name, home address, date of birth, permit-application number, or emergency-contact questions are fields you add; they are not documented defaults. ID photos or permit paperwork attached to a signup are files you accept; they are not documented defaults. One signup entry can store a home address next to strong evidence a firearm lives there. A signup is not proof of firearm ownership or permit issuance. Notification emails can copy field values off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Form entries stored in WordPress; file uploads 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 home address, date of birth, or permit number was sent. A page request from this script is not proof that anyone enrolled. Consent timing has not been tested. Review which tags you enable on firearms-training signup 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. Home addresses, dates of birth, permit-application numbers, or emergency contacts often depend on the fields you configure. A signup is not proof of firearm ownership or permit issuance. A marketing-tag page request is not proof that anyone enrolled. Aggregated roster rows can map which households appear armed and when owners may be in class. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the signup page, and how long records and backups are kept. A "secure" or "client forms" 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 Second Amendment rights, ATF rules, state permit laws, firearms laws, carry-permit rules, or training requirements. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on signup pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-firearms-training-plugin-privacy