Metal detecting plugin privacy
The recovery request that geotags the lost ring and maps which private land lets searchers in
A recovery request can geotag where a valuable went missing. A GPS pin on a beach, a yard, a dropped ring's last known square meter, plus what it is worth and the story of why it matters. Landowner permission requests can build a second map: private parcels whose owners let strangers search. The form list can become a treasure map of real valuables and the sentimental pressure to pay for them, indexed by address. Geotag, GPS pin, last-known location, item description, value, story, landowner-permission, parcel, address, and item-photo fields are configured, not documented defaults. Optional item photos go in the site uploads folder. A recovery request is not proof an item was found or is still there. A geotag is a stored pin, not proof the item is at that spot. A landowner-permission answer is a stored note, not a legal right to search. A page request is not proof anyone booked. The page URL can say metal detecting 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 recovery pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a treasure-trove claim, a salvage claim, a trespass claim, a property-title claim, a finder-keeper 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 recovery requests, geotags, and page tags go
Recovery requests and forms handled on your WordPress site
Check which geotag, GPS pin, last-known location, item description, value, story, landowner-permission, parcel, address, or item-photo fields you enable, who can open form entries and bookings, where uploaded item 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 find. Notification emails can also copy the same geotags, item values, and stories off-site. One table can name the ring, the pin, and the parcel next to a name, even when the search never happens. Ask your web vendor not to collect a geotag next to an item value on the first public form, not to store that pin next to a landowner note in one open submissions list, and to purge unused recovery requests after the date passes. A privacy-policy page does not by itself limit who can export a recovery list or republish an upload. A stored request is not proof an item was found.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the metal-detecting booking or recovery page. That page request can reach a vendor host before anyone submits. The page URL can say metal detecting even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and recovery pages if you do not want that page request. A browser scan cannot inspect stored geotags, item values, or landowner notes. A "treasure map" badge is not a verified storage path.
Metal-detecting booking, recovery, 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 detecting or mapping 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 recovery search is a booking you create; a service name such as beach recovery, yard search, or landowner-permission visit is a label you configure. Neither is a documented default. Geotag, GPS pin, last-known location, item description, value, story, landowner-permission, parcel, address, or item-photo questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked search is not proof an item was found, and is not a legal right to enter land. Cancelling or missing the slot later does not erase the geotag, item value, or story 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 find 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. | Search 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. Geotag, GPS pin, last-known location, item description, value, story, landowner-permission, parcel, address, or item-photo questions are fields you add; they are not documented defaults. An item photo is a file you accept; that file type is not a documented default. A recovery request is not proof an item was found or is still there. A geotag is a stored pin, not proof the item is at that spot. A landowner-permission answer is a stored note, not a legal right to search. 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 recovery request sits after a search that never happened is not a documented default of the plugin. | Recovery-request 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 a geotag, item-value, or landowner-permission field was sent. A page request from this script is not proof anyone booked. The page URL can say metal detecting even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and recovery pages. Keep marketing tags off those pages if you do not want that page request. A tagged recovery page can re-confirm metal-detecting interest next to a stored address and files; this row does not claim a find 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. Geotag, GPS pin, last-known location, item description, value, story, landowner-permission, parcel, address, or item-photo fields often depend on the fields you configure. A recovery request is not proof an item was found or is still there. A geotag is a stored pin, not proof the item is at that spot. A landowner-permission answer is a stored note, not a legal right to search. A marketing-tag page request is not proof anyone booked. The page URL can say metal detecting even when no form is submitted. The pin, the value, and the story can sit after the search never happens. This page is about a recovery request that geotags a named valuable and maps which private land lets searchers in, not a drone-photography aerial archive, and not a land-surveyor boundary filing. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or recovery 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 treasure-trove law, salvage, trespass, property title, or finder-keeper rules. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and recovery pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-metal-detecting-plugin-privacy