Drone photography plugin privacy

The booking whose deliverable is a geotagged aerial archive of your property

A drone shoot is ordered for one photo and delivers a folder. Roofline, skylights, pool gate, the path from the back fence to the unlocked porch, the neighbor's yard over the fence. The booking form can record why it was ordered: listing photos, insurance claim, storm damage. Those reasons date the roof and the sale before any public record does. Optional photo uploads go in the site uploads folder. Reason-for-shoot, address, parcel, geotag, photo-upload, and date fields are configured, not documented defaults. The deliverables folder is a geotagged bird's-eye file of a named parcel. It can sit after the listing closes. A booking is not proof a shoot happened. An aerial photo is an upload, not a published listing. Publishing listing photos is the site's choice, not the plugin's. A page request is not proof anyone booked. The page URL can say drone photography 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, an FAA or drone-regulation claim, a trespass claim, an insurance-fraud claim, a listing-outcome claim, a neighbor-privacy-statute 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 aerial photos, shoot bookings, and page tags go

Shoot bookings and forms handled on your WordPress site

Check which reason-for-shoot, address, parcel, geotag, photo-upload, or date fields you enable, who can open form entries and bookings, where uploaded aerial 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 shoot. Notification emails can also copy the same photos and address off-site. One table can name the house, the parcel, and the aerial files next to a name, even when the shoot never happens. A later listing gallery can reuse those files. Ask your web vendor not to collect a geotagged aerial next to an address on the first public form, not to store that photo next to a reason-for-shoot in one open submissions list, and to purge unused bookings after the date passes. A privacy-policy page does not by itself limit who can export a booking list or republish an upload. A stored booking is not proof a shoot occurred.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the drone-photography booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say drone photography 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 aerial photos or addresses. A "geotagged aerial archive" badge is not a verified storage path.

Drone-photography booking, upload, 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 flight or mapping 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 drone-photography booking is a booking you create; a service name such as listing aerials, roof inspection, or storm-damage photos is a label you configure. Neither is a documented default. Reason-for-shoot, address, parcel, geotag, or date questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked slot is not proof a shoot happened, and is not a published listing. Cancelling or missing the slot later does not erase the address or reason 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 shoot 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.

Shoot 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. Reason-for-shoot, address, parcel, geotag, or photo-upload questions are fields you add; they are not documented defaults. An aerial photo is a file you accept; that file type is not a documented default. A booking is not proof a shoot happened. An aerial photo is an upload, not a published listing. Publishing those photos on a listing or portfolio is a choice the site makes after the file is stored; it is not a documented default of the plugin. 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 a booking sits after a request that never became a shoot is not a documented default of the plugin.

Booking and aerial-upload 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 reason-for-shoot, address, or parcel field was sent. A page request from this script is not proof anyone booked. The page URL can say drone photography 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 booking page can re-confirm aerial-photo interest next to a stored address and files; this row does not claim a shoot 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. Reason-for-shoot, address, parcel, geotag, photo-upload, or date fields often depend on the fields you configure. A booking is not proof a shoot happened. An aerial photo is an upload, not a published listing. Publishing listing photos is the site's choice, not the plugin's. A marketing-tag page request is not proof anyone booked. The page URL can say drone photography even when no form is submitted. The photos and the address can sit after the listing closes. This page is about a booking whose deliverable is a geotagged aerial archive of your property, not a photography client gallery, not a roofing open-sky quote, not a solar kilowatt-hour upload, not a land surveyor boundary filing, and not a seasonal-lights photographed house. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or quote page, and how long records and backups are kept. A portfolio 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 FAA rules, drone regulation, trespass, insurance-fraud law, listing outcomes, or neighbor-privacy statutes. Review stored records, uploaded files, 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-drone-photography-plugin-privacy