Tree service plugin privacy

The hazard quote that becomes dated evidence of the limb you knew about

A tree-service quote can look like a photo and a date. It is also a timestamped admission: photos of the dead oak over the swing set, your own written danger note ("worried it hits the neighbor's roof"), crane-access notes that map the yard, and the gate code to get back there. If the limb falls before you book, the form you filled out is the negligence record waiting in a submissions table. Hazard-description, limb-photo, crane-access, neighbor-risk, and gate-code fields are configured, not documented defaults. Optional yard photos go in the site uploads folder. A tree-service booking is not proof a tree was removed. A danger description is a form answer, not a verified hazard. A gate code is a stored instruction, not proof anyone used it. A page request is not proof anyone ordered a removal. The page URL can say tree service 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 quote pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a negligence claim, a liability claim, a tree-failure claim, a property-damage 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 hazard quotes, bookings, and page tags go

Hazard quotes and forms handled on your WordPress site

Check which hazard-description, limb-photo, crane-access, neighbor-risk, or gate-code fields you enable, who can open form entries and bookings, where uploaded yard 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 danger note and gate code off-site. One table can name the house, the limb, the neighbor risk, and the gate code next to a name, even when the crew never comes. Ask your web vendor not to collect a gate code next to a hazard description on the first public form, not to store neighbor-risk notes next to yard photos in one open submissions list, and to purge unused quotes after the date passes. A privacy-policy page does not by itself limit who can export a quote list. A stored booking is not proof a tree was removed.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the tree-service booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say tree service 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 hazard notes, yard photos, or gate codes. A "hazard quote ready" badge is not a verified storage path.

Tree-service booking, hazard-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 arborist or crane-dispatch software without a WordPress.org listing is 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). 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 tree removal is a booking you create; a service name such as hazard removal, crane job, or stump grind is a label you configure. Neither is a documented default. Hazard-description, limb-photo, crane-access, neighbor-risk, or gate-code questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked removal is not proof a tree was cut, and a hazard note is not proof a limb was dangerous. Cancelling or missing the slot later does not erase the danger description, limb photo, crane-access note, or gate code already stored next to a name, 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.

Hazard-quote bookings, custom intake fields, and automatic confirmation emails 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. Hazard-description, limb-photo, crane-access, neighbor-risk, or gate-code questions are fields you add; they are not documented defaults. A limb photo or yard map is a file you accept; that file type is not a documented default. A tree-service request is not proof a tree will be removed. A hazard description is a stored note, not a verified danger. A gate code is a stored instruction, not proof anyone used it. 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 hazard-quote form entries stored in WordPress; file 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 stack-location, gate-code, away-window, or stop-reorder field was sent. A page request from this script is not proof anyone ordered tree service. The page URL can say tree service even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote pages. Keep marketing tags off those pages if you do not want that page request. A tagged delivery page can re-confirm tree service interest next to a stored address and gate code; this row does not claim a delivery from that request.

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. Hazard-description, limb-photo, crane-access, neighbor-risk, or gate-code fields often depend on the fields you configure. A tree-service booking is a calendar row, not proof a tree will be removed or that a limb was dangerous on a named date. A hazard description, photo, or crane-access answer is a form answer or uploaded file, not a verified hazard. A marketing-tag page request is not proof anyone booked a removal. The page URL can say tree service even when no form is submitted. This page is about a hazard-quote stack that can become dated evidence of what a homeowner knew, not a gutter-cleaning yard-photo log, not a snow-removal seasonal route, not a pool-service nobody-home day, and not a pressure-washing before/after gallery. 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 "tree privacy" or "hazard 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 negligence, liability, tree failure, or property damage. 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-tree-service-plugin-privacy