Wildlife removal plugin privacy

The exclusion quote that photographs every unsecured way into your house

The inspection form collects where you hear the scratching (which bedroom, which wall), photos of the torn soffit and the gap under the deck, attic and crawlspace access notes, and an itemized exclusion bid — one line per hole. The lateral truth: a burglar's first job is finding a way in that isn't locked; the wildlife report has already done that work, with pictures, tied to your address — and every line item you declined to pay for stays open. Those fields are configured, not documented defaults. A wildlife-removal booking is a calendar row, not proof an animal was removed or that a hole stays open. A scratching, entry-photo, access, or bid-line answer is a form answer or uploaded file, not a verified entry inventory. A page request is not proof anyone booked an exclusion. The page URL can say wildlife removal even when no form is submitted. Ask what happens to the name, the service address, the entry photos, and the declined bid lines after an exclusion finishes — the stack that mapped every open entrance 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 home-security-advice claim, a burglary-risk claim, a vacancy-inference claim, a trespass claim, a wildlife-control-licensing 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 wildlife-removal bookings, exclusion quotes, and page tags go

Bookings and exclusion quotes on your WordPress site

Check which scratching-location, entry-photo, attic-access, crawlspace-access, exclusion-bid-line, declined-line, name, or service-address fields you enable, who can open form entries and wildlife-removal bookings, which inboxes receive copies, and how long records, emails, and backups are kept after an exclusion finishes — when the name-plus-address-plus-entry row still holds a photographed break-in inventory next to declined holes. Notification emails can also copy those fields off-site. One table can list every "Sam · 44 Cedar Ln · scratching master bedroom NW wall · torn soffit photo · deck gap photo · attic hatch · crawlspace grate · bid: soffit $280 declined · deck gap $190 declined" stack next to a customer name. Ask your web vendor not to keep entry photos and declined bid lines next to service addresses and names in one open submissions list longer than operations need, and to purge those fields when an exclusion finishes. A privacy-policy page does not by itself limit who can open a submissions list. A stored wildlife-removal booking is not proof an animal was removed or that a hole stays open. A scratching, entry-photo, access, or bid-line answer is not a verified entry inventory.

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

Wildlife-removal booking, exclusion-quote, 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 wildlife-removal 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 Tuesday exclusion window or an "attic inspect" slot is a booking you create; a service name such as raccoon exclusion or soffit seal is a label you configure. Neither is a documented default. Scratching-location, entry-photo, attic-access, crawlspace-access, exclusion-bid-line, declined-line, or service-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 an animal was removed or that a hole stays open — and a CSV export of "Sam · 44 Cedar Ln · scratching master bedroom NW wall · torn soffit photo · deck gap photo · attic hatch · crawlspace grate · bid: soffit $280 declined · deck gap $190 declined" next to a customer name is still a calendar that pairs a photographed entry inventory with a service 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.

Wildlife-removal 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. Scratching-location, entry-photo, attic-access, crawlspace-access, exclusion-bid-line, declined-line, or service-address fields are fields you add; they are not documented defaults. Completing the form can store a name-plus-address-plus-entry stack ("Sam · 44 Cedar Ln · scratching master bedroom NW wall · torn soffit photo · deck gap photo · attic hatch · crawlspace grate · bid: soffit $280 declined · deck gap $190 declined") — typed or uploaded once so a shop can quote an exclusion, into the same tables as a "wildlife removal" label. A scratching, entry-photo, access, or bid-line answer is a form answer or uploaded file, not a verified entry inventory. A wildlife-removal booking is a calendar row, not proof an animal was removed or that a hole stays open — and a staff login can open "Sam, 44 Cedar Ln, scratching master bedroom NW wall, torn soffit photo, deck gap photo, attic hatch, crawlspace grate, soffit $280 declined, deck gap $190 declined" 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, service address, and exclusion answers stored in WordPress; optional entry 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 scratching-location, entry-photo, attic-access, crawlspace-access, exclusion-bid-line, or declined-line field was sent. A page request from this script is not proof anyone booked an exclusion. The page URL can say wildlife removal 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. Scratching-location, entry-photo, attic-access, crawlspace-access, exclusion-bid-line, declined-line, or service-address fields often depend on the fields you configure. A wildlife-removal booking is a calendar row, not proof an animal was removed or that a hole stays open. A scratching, entry-photo, access, or bid-line answer is a form answer or uploaded file, not a verified entry inventory. A marketing-tag page request is not proof anyone booked an exclusion. The page URL can say wildlife removal even when no form is submitted. The name-plus-address-plus-entry row that mapped every open entrance 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 exclusion-quote stack, not a pest-control stigma disclosure, a home-inspection buyer defect list, an alarm-company code-and-away schedule, or an appliance-repair garage-code booking. 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 "wildlife removal privacy" or "exclusion quote 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 home-security advice, burglary risk, or wildlife-control licensing. 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-wildlife-removal-plugin-privacy