Jewelry repair plugin privacy
The repair ticket that appraises the heirloom and staples your address to it
A repair ticket for jewelry is an insurance appraisal with your home address stapled to it: high-resolution photos of the heirloom, its declared replacement value, and where it normally lives. The engraving field quietly maps relationships — "To E, always, 1987" — and the drop-off/pickup dates say when the piece is out of your house and when it's back. Gold buyers see what you'll sell; the repair ticket sees what you'd never part with, which is exactly what's worth stealing. Those fields are configured, not documented defaults. A repair booking is a calendar row, not proof anyone left jewelry or that a piece was repaired. A photo or engraving answer is a form answer or uploaded file, not a verified appraisal. A page request is not proof anyone opened a repair ticket. The page URL can say jewelry repair even when no form is submitted. Ask what happens to the photos, the declared value, the home address, the engraving, and the drop-off/pickup dates after a repair closes — the stack that paired what you'd never sell with where it lives outlives the clasp fix. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake or drop-off page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a jewelry-repair-contract-law claim, an insurance-appraisal-advice claim, a theft-risk-inference claim, an estate-dispute-discovery claim, an engraving-relationship-inference 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 repair tickets, drop-offs, and page tags go
Tickets and bookings on your WordPress site
Check which piece-description, photo-upload, declared-value, home-address, engraving, drop-off, pickup, or intake-upload fields you enable, who can open form entries and repair bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a repair closes — when the photo-plus-value-plus-address-plus-engraving row still holds the heirloom next to where it lives. Notification emails can also copy those fields off-site. One table can list every "heirloom ring.jpg (hi-res) · declared $8,400 · home 12 Oak St · engraving To E, always, 1987 · drop-off 10/12 · pickup 10/19" stack next to a customer name. Ask your web vendor not to keep heirloom photos and declared values next to home addresses and engraving notes in one open submissions list longer than operations need, and to purge those fields when a repair closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored repair booking is not proof anyone left jewelry or that a piece was repaired. A photo or engraving answer is not a verified appraisal.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the intake or drop-off page. That page request can reach a vendor host before anyone submits. The page URL can say jewelry repair even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off intake and drop-off pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "jewelry repair privacy" badge is not a verified storage path.
Jewelry-repair ticket, drop-off booking, 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 jewelry-repair SaaS tools without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A Tuesday 2pm drop-off window or a pickup slot is a booking you create; a service name such as ring resize or clasp repair is a label you configure. Neither is a documented default. Piece-description, photo-upload, declared-value, home-address, engraving, drop-off, or pickup questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone left jewelry or that a piece was repaired — and a CSV export of "heirloom ring.jpg (hi-res) · declared $8,400 · home 12 Oak St · engraving To E, always, 1987 · drop-off 10/12 · pickup 10/19" next to a customer name is still a calendar that pairs an heirloom appraisal with a home address. Emails can include those custom fields and copy the appointment off-site. 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. | Jewelry-repair drop-off bookings stored 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. Piece-description, photo-upload, declared-value, home-address, engraving, drop-off, or pickup fields are fields you add; they are not documented defaults. Completing the form can store a photo-plus-value-plus-address-plus-engraving stack ("heirloom ring.jpg (hi-res) · declared $8,400 · home 12 Oak St · engraving To E, always, 1987 · drop-off 10/12 · pickup 10/19") — typed once so a jeweler can quote and hold the piece, into the same tables as a "jewelry repair" label. A photo or engraving answer is a form answer or uploaded file, not a verified appraisal. A repair booking is a calendar row, not proof anyone left jewelry — and a staff login can open "Jordan, heirloom-ring.jpg, $8,400, 12 Oak St, To E always 1987, drop-off 10/12" next to everyone else's resume. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Piece, photo, value, address, and engraving answers stored in WordPress; optional photos 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 piece-description, photo, declared-value, home-address, or engraving field was sent. A page request from this script is not proof anyone opened a repair ticket. The page URL can say jewelry repair even when no form is submitted. Consent timing has not been tested. Review which tags you enable on intake and drop-off pages. | 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. Piece-description, photo-upload, declared-value, home-address, engraving, drop-off, or pickup fields often depend on the fields you configure. A repair booking is a calendar row, not proof anyone left jewelry or that a piece was repaired. A photo or engraving answer is a form answer or uploaded file, not a verified appraisal. A marketing-tag page request is not proof anyone opened a repair ticket. The page URL can say jewelry repair even when no form is submitted. The photo-plus-value-plus-address-plus-engraving row that appraises the heirloom and staples your address to it — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that repair-ticket appraisal stack, not a gold-buyer sell appraisal, a pawn collateral ticket, a home-theater room inventory, a consignment letting-go timeline, or a tailor service-ticket intimacy form. Ask your web vendor who can open entries, whether a marketing tag loads on the intake or drop-off page, and how long records and backups are kept. A "jewelry repair privacy" or "jeweler compliant" 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 jewelry-repair contract law, insurance-appraisal advice, theft-risk inference, estate-dispute discovery, or engraving-relationship inference. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake and drop-off 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-jewelry-repair-plugin-privacy