Bee removal plugin privacy
The quote that photographs the hole in your house and files who inside is allergic
A bee-removal quote can look like a ladder and a hive. It is also a building-envelope photo: the wall void, the soffit gap, the roofline entry — stored next to the address — plus an intake question that asks whether anyone in the home is allergic. The uploads folder keeps annotated pictures of exactly where a structure can be entered, long after the hive is gone. Entry-photo, soffit-gap, wall-void, roofline-entry, allergy-flag, and hive-location fields are configured, not documented defaults. Optional entry photos go in the site uploads folder. A removal booking is not proof a hive was removed. An allergy answer is a stored note, not a verified medical fact. A page request is not proof anyone booked a removal. The page URL can say bee removal even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on booking and account pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a break-in claim, an anaphylaxis claim, a medical-emergency 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 removal bookings, entry-photo intakes, and page tags go
Removal bookings and quote forms handled on your WordPress site
Check which entry-photo, soffit-gap, wall-void, roofline-entry, allergy-flag, or hive-location fields you enable, who can open form entries and bookings, where uploaded envelope photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a removal. Notification emails can also copy the same allergy answer and photo link off-site. One table can name the house, the entry photo, and the allergy flag next to a name, even when the crew never comes. Ask your web vendor not to collect an allergy answer next to an entry photo on the first public form, not to store soffit-gap notes next to addresses in one open submissions list, and to purge unused removal bookings after the date passes. A privacy-policy page does not by itself limit who can export a customer list. A stored booking is not proof a hive was removed.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the bee-removal booking or account page. That page request can reach a vendor host before anyone submits. The page URL can say bee removal even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and account pages if you do not want that page request. A browser scan cannot inspect stored entry photos, allergy flags, or hive locations. A "hive removed" badge is not a verified storage path.
Bee-removal booking, 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 pest-relocation or apiary software without a WordPress.org listing is 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). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A bee removal or live hive relocation is a booking you create; a service name such as live relocation, cut-out, or trap-out is a label you configure. Neither is a documented default. Entry-photo, soffit-gap, wall-void, roofline-entry, allergy-flag, or hive-location questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked removal is not proof a hive was removed, and an allergy answer is not a verified medical fact. Cancelling or missing the slot later does not erase the entry photo reference, allergy flag, or hive location already stored next to an address, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a removal is not a documented default of the plugin. 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. | Removal bookings, custom intake fields, and automatic confirmation emails 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. Entry-photo, soffit-gap, wall-void, roofline-entry, allergy-flag, or hive-location questions are fields you add; they are not documented defaults. A photo of a soffit gap or wall void is a file you accept; that file type is not a documented default. A removal request is not proof a hive was removed. An allergy answer is a stored note, not a verified medical fact. An entry photo is an uploaded file, not a verified breach. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long an account row sits after a request that never became a removal is not a documented default of the plugin. | Account and quote 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 an entry-photo, allergy-flag, soffit-gap, or hive-location field was sent. A page request from this script is not proof anyone booked a removal. The page URL can say bee removal even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and account pages. Keep marketing tags off those pages if you do not want that page request. A tagged bee-removal page can re-confirm removal interest next to a stored address and entry photo; this row does not claim a removal from that request. | 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. Entry-photo, soffit-gap, wall-void, roofline-entry, allergy-flag, or hive-location fields often depend on the fields you configure. A removal booking is not proof a hive was removed. An allergy answer is a stored note, not a verified medical fact. A marketing-tag page request is not proof anyone booked a removal. The page URL can say bee removal even when no form is submitted. The entry photo and the allergy flag can sit after the crew never comes. This page is about a quote that photographs a structural entry and files an allergy answer, not a home-inspection defect list, not a roofing open-sky quote, and not a gutter-cleaning yard photo. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or account page, and how long records and backups are kept. A "hive removed" 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 break-in risk, anaphylaxis, or medical-emergency response. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and account 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-bee-removal-plugin-privacy