Shooting range plugin privacy

The sign-in log that is a gun-owner registry with timestamps

A shooting range's membership page can look like a contact form and a lane booking. The same form often asks name and phone, street address, whether the applicant owns firearms, optional mental-health attestations required by some state waivers, an emergency contact, and a lane sign-in time, and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. Before anyone steps onto a lane, the membership form asks who owns firearms and where they live. The lane sign-in kiosk timestamps when that person is reliably not home. Optional mental-health attestation checkboxes sit in the same row as the address. An emergency contact names who to call when it goes wrong. A lane booking is a calendar row, not proof someone owns a firearm. A membership answer is the applicant's disclosure, not a verified registry entry. A mental-health attestation is a checkbox the applicant typed, not a clinical record. A sign-in timestamp is a visit log, not proof of absence from home. A page request is not proof anyone shoots anywhere. The page URL can say shooting range even when no form is submitted. Ask what happens to the firearm-ownership answer and the sign-in log after the membership ends — the sign-in log that is a gun-owner registry with timestamps outlives the first visit. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the membership page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a firearms-ownership or legal-status or safety-certification claim, a mental-health claim, or a GDPR or other compliance assessment.

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 lane bookings, membership intakes, and page tags go

Memberships and sign-ins on your WordPress site

Check which membership, address, firearm-ownership, mental-health-attestation, emergency-contact, or waiver fields you enable, who can open form entries and lane bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a booking closes — when the sign-in log is a gun-owner registry with timestamps. Notification emails can also copy those fields off-site. One table can list every firearm-ownership checkbox a member typed next to a lane slot and a street address. Ask your web vendor not to keep sign-in timestamps next to firearm-ownership answers and addresses in one open submissions list longer than operations need, and to purge booking rows when the membership is declined or closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored lane booking is not proof someone owns a firearm. A sign-in timestamp is not proof of absence from home.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the shooting-range membership page. That page request can reach a vendor host before anyone submits. The page URL can say shooting range even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off membership and lane sign-in pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "verified member" badge is not a verified storage path.

Lane booking, membership intake, 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-management CRM 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 lane or membership sign-in booking is a booking you create; a service name such as lane rental, membership check-in, or range orientation is a label you configure. Neither is a documented default. Street-address, firearm-ownership, mental-health-attestation, emergency-contact, or membership questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof someone owns a firearm — and a CSV export of lane slots next to a firearm-ownership checkbox, a street address, and a dated sign-in is still a booking row after someone asked to shoot. 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.

Lane and membership sign-in 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. Street-address, firearm-ownership, mental-health-attestation, emergency-contact, or membership questions are fields you add; they are not documented defaults. Completing the form can store a firearm-ownership checkbox next to a street address, a mental-health attestation, an emergency contact, and optional waiver-file uploads — typed once by a member into the same tables as a newsletter signup. A lane booking is a calendar row, not proof someone owns a firearm. A membership answer is the applicant's disclosure, not a verified registry entry. A mental-health attestation is a checkbox the applicant typed, not a clinical record. A sign-in timestamp is a visit log, not proof of absence from home. An uploaded waiver is a client document in uploads/forminator, not a court filing. A staff login can open the firearm-ownership answer next to Tuesday's 10am lane slot. 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.

Membership and sign-in entries stored in WordPress; optional waiver uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 membership, firearm-ownership, mental-health-attestation, address, or waiver field was sent. A page request from this script is not proof anyone shoots anywhere. The page URL can say shooting range even when no form is submitted. Consent timing has not been tested. Review which tags you enable on membership and lane sign-in pages.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Membership, address, firearm-ownership, mental-health-attestation, emergency-contact, or waiver fields often depend on the fields you configure. A lane booking is a calendar row, not proof someone owns a firearm. A membership answer is the applicant's disclosure, not a verified registry entry. A mental-health attestation is a checkbox the applicant typed, not a clinical record. A sign-in timestamp is a visit log, not proof of absence from home. A marketing-tag page request is not proof anyone shoots anywhere. The page URL can say shooting range even when no form is submitted. The sign-in log that is a gun-owner registry with timestamps — that is a storage path next to names and phones, not a feature these plugins claim. This page is about that recurring membership and visit-log intake, not a one-time firearms-training class roster, a security-guard license form, or an executive-protection threat briefing. Ask your web vendor who can open entries, whether a marketing tag loads on the membership page, and how long records and backups are kept. A "verified member" 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 firearms ownership, legal status, safety certification, or mental health. Review stored records, bookings, connected services, exports, notification emails, marketing tags on membership pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-shooting-range-plugin-privacy