Gold buyer plugin privacy
The appraisal form that photographs the inheritance before the stranger arrives
A gold-buyer appraisal can look like a photo of a ring and a time slot. It is also a map of remaining valuables, the home address where they sit, the story of who died to leave them, and a dated signal of why they are being sold now. Item-description, karat-weight, provenance, visit-window, and jewelry-photo fields are configured, not documented defaults. The form photographs the inheritance before the stranger arrives: a home-visit slot puts an appraiser at the address next to the photos. One WordPress row can hold the pieces, the provenance, the address, and the pictures. An appraisal request is not proof of financial distress. A provenance answer is the seller's story, not an estate record. A photo of a ring is an upload, not an insurance appraisal. A page request is not proof anyone sold anything. The page URL can say gold buyer or cash for gold 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 appraisal pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a precious-metals-dealer-law claim, an appraisal-accuracy claim, a fair-price claim, a theft-risk 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 jewelry photos, provenance stories, appraisal bookings, and page tags go
Appraisal bookings and forms handled on your WordPress site
Check which item-description, karat-weight, provenance, visit-window, or jewelry-photo fields you enable, who can open form entries and bookings, where uploaded jewelry photos and inheritance paperwork 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 sale. Notification emails can also copy the same photos, provenance, and home address off-site. One table can name the pieces, the address, and the inheritance story next to a name, even when the sale never happens. Ask your web vendor not to collect a home address next to jewelry photos on the first public form, not to store provenance next to those photos in one open submissions list, and to purge unused appraisal bookings after the date passes. A privacy-policy page does not by itself limit who can export an appraisal list. A stored booking is not proof an appraisal occurred.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the gold-buyer booking or appraisal page. That page request can reach a vendor host before anyone submits. The page URL can say gold buyer or cash for gold even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and appraisal pages if you do not want that page request. A browser scan cannot inspect stored jewelry photos or provenance answers. A "secure appraisal" badge is not a verified storage path.
Gold-buyer booking, appraisal, 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 gold-buyer or pawn 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 home-visit or walk-in gold appraisal is a booking you create; a service name such as gold buyer, cash for gold, or home jewelry appraisal is a label you configure. Neither is a documented default. Item-description, karat-weight, provenance, preferred-visit-window, or home-address questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked home visit is not proof an appraiser arrived and is not proof of financial distress for anyone named in the request. Cancelling or missing the visit later does not erase the item list, photos, or provenance 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 sale 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. | Home-visit and walk-in appraisal 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. Item-description, karat-weight, provenance, preferred-visit-window, or home-address questions are fields you add; they are not documented defaults. A jewelry photo or inheritance paperwork is a file you accept; neither of those file types is a documented default. An appraisal request is not proof of financial distress. A provenance answer is the seller's story, not an estate record. A photo of a ring is an upload, not an insurance appraisal. 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 appraisal request sits after a visit that never became a sale is not a documented default of the plugin. | Appraisal and document-upload 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 item-description, karat-weight, provenance, visit-window, or jewelry-photo field was sent. A page request from this script is not proof anyone sold anything. The page URL can say gold buyer or cash for gold even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and appraisal pages. Keep marketing tags off those pages if you do not want that page request. A tagged appraisal page can re-confirm interest next to stored jewelry photos and a home address; this row does not claim a sale 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. Item-description, karat-weight, provenance, visit-window, or jewelry-photo fields often depend on the fields you configure. An appraisal request is not proof of financial distress. A provenance answer is the seller's story, not an estate record. A photo of a ring is an upload, not an insurance appraisal. A marketing-tag page request is not proof anyone sold anything. The page URL can say gold buyer or cash for gold even when no form is submitted. The photos and the home address can sit after the sale never happens. This page is about an appraisal form that photographs the inheritance before the stranger arrives, not a pawn-shop ticket, an estate-sale inventory, a security-guard quote, a payday-loan contact list, a car-title-loan application, or a probate-attorney intake. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or appraisal page, and how long records and backups are kept. A "secure" 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 precious-metals dealer law, appraisal accuracy, fair-price claims, or theft risk. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and appraisal pages, and backups.
Documentation snapshot: Oct 14, 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-gold-buyer-plugin-privacy