Taxidermy plugin privacy

The intake that records what you killed, where, and the trophy room's address

The drop-off form keeps a hunting record in writing — species, harvest date and location, game-tag and license numbers, field photos — stapled to the customer's name, phone, and the home address where the finished trophy hangs. It is simultaneously a regulatory record (tag numbers an agency can subpoena) and a burglary catalog of high-value mounts, held in a small shop's WordPress uploads. Those fields are configured, not documented defaults. A taxidermy booking is a calendar row, not proof a harvest was lawful or a mount was delivered. A tag or license answer is a form answer or uploaded file, not a verified agency record. A page request is not proof anyone booked a drop-off. The page URL can say taxidermy even when no form is submitted. Ask what happens to the name, the trophy-home address, the harvest details, the tag numbers, and the field photos after a mount ships — the stack that mapped a kill 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 hunting-legality claim, a game-tag-validity claim, a wildlife-agency-compliance claim, a license-validity 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 taxidermy bookings, harvest-to-trophy-address intakes, and page tags go

Bookings and drop-off intakes on your WordPress site

Check which species, harvest-date, harvest-location, game-tag, license, field-photo, name, phone, or trophy-home-address fields you enable, who can open form entries and taxidermy bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a mount ships — when the name-plus-address-plus-harvest row still holds a regulatory record and a mount catalog next to a drop-off window. Notification emails can also copy those fields off-site. One table can list every "Alex · 9 Maple Ave · mule deer · harvest 2024-11-12 · Canyon Unit 12 · tag WLD-88421 · license H-10294 · field photo" stack next to a customer name. Ask your web vendor not to keep game tags, licenses, and field photos next to trophy-home addresses and names in one open submissions list longer than operations need, and to purge those fields when a mount ships. A privacy-policy page does not by itself limit who can open a submissions list. A stored taxidermy booking is not proof a harvest was lawful or a mount was delivered. A tag or license answer is not a verified agency record.

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 taxidermy 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 "taxidermy privacy" badge is not a verified storage path.

Taxidermy booking, harvest-to-trophy-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 taxidermy SaaS tools 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 Saturday drop-off window or a "mount intake" slot is a booking you create; a service name such as shoulder mount or European skull is a label you configure. Neither is a documented default. Species, harvest-date, harvest-location, game-tag, license, field-photo, or trophy-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 harvest was lawful or a mount was delivered — and a CSV export of "Alex · 9 Maple Ave · mule deer · harvest 2024-11-12 · Canyon Unit 12 · tag WLD-88421 · license H-10294 · field photo" next to a customer name is still a calendar that pairs a harvest record with a trophy-room 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.

Taxidermy 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. Species, harvest-date, harvest-location, game-tag, license, field-photo, or trophy-address fields are fields you add; they are not documented defaults. Completing the form can store a name-plus-address-plus-harvest stack ("Alex · 9 Maple Ave · mule deer · harvest 2024-11-12 · Canyon Unit 12 · tag WLD-88421 · license H-10294 · field photo") — typed once so a shop can quote a mount, into the same tables as a "taxidermy" label. A tag or license answer is a form answer or uploaded file, not a verified agency record. A taxidermy booking is a calendar row, not proof a harvest was lawful or a mount was delivered — and a staff login can open "Alex, 9 Maple Ave, mule deer, tag WLD-88421, field photo" 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, trophy address, and harvest answers stored in WordPress; optional field photos 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 species, tag, license, or trophy-address field was sent. A page request from this script is not proof anyone booked a drop-off. The page URL can say taxidermy 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 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. Species, harvest-date, harvest-location, game-tag, license, field-photo, or trophy-address fields often depend on the fields you configure. A taxidermy booking is a calendar row, not proof a harvest was lawful or a mount was delivered. A tag or license answer is a form answer or uploaded file, not a verified agency record. A marketing-tag page request is not proof anyone booked a drop-off. The page URL can say taxidermy even when no form is submitted. The name-plus-address-plus-harvest row that mapped a kill 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 post-hunt evidence stack, not a hunting-outfitter trip coordinate, a firearms-training shooter roster, or a gunsmith serial-to-address repair ticket. 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 "taxidermy privacy" or "game-tag 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 hunting legality, game-tag validity, or wildlife-agency 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

Scan your site for third-party requests

/wp-taxidermy-plugin-privacy