Piano tuning plugin privacy
The standing appointment that registers your living room's most valuable object and its visiting hours
Every booking stores the make ("Steinway B, inherited"), which room it sits in, the recurring six-month tuning slot, and often the kids' lesson schedule around it. The lateral truth: a burglar can't search houses for valuables, but a tuner's client list is already sorted — every row is a six-figure object that can't go in a safe, at a confirmed address, with a calendar of when someone lets strangers in. Leak it and you've published a valuables registry with visiting hours. Those fields are configured, not documented defaults. A piano-tuning booking is a calendar row, not proof a household owns a six-figure instrument or that someone will be home at a named time. A make, room, recurring-slot, or lesson-schedule answer is a form answer or uploaded file, not a verified inventory. A page request is not proof anyone booked a tuning. The page URL can say piano tuning even when no form is submitted. Ask what happens to the name, the service address, the make and room answers, and the recurring slot after a tuning finishes — the stack that registered the instrument and its visiting hours outlives the appointment. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking or quote page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a burglary claim, a theft-targeting claim, an instrument-valuation claim, an ownership-proof claim, a tuner-licensing claim, a trespass 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 piano-tuning bookings, standing appointments, and page tags go
Bookings and standing appointments on your WordPress site
Check which make, room, recurring-slot, lesson-schedule, access-note, name, or service-address fields you enable, who can open form entries and piano-tuning bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a tuning finishes — when the name-plus-address-plus-piano row still holds a valuables-existence answer next to visiting hours. Notification emails can also copy those fields off-site. One table can list every "Casey · 9 Maple St · Steinway B · inherited · room: living · slot: every Mar/Sep · lessons: Tue 4pm · access note: side door" stack next to a customer name. Ask your web vendor not to keep make, room, recurring-slot, and lesson-schedule answers next to service addresses and names in one open submissions list longer than operations need, and to purge those fields when a standing appointment ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored piano-tuning booking is not proof a household owns a six-figure instrument or that someone will be home at a named time. A make, room, recurring-slot, or lesson-schedule answer is not a verified inventory.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say piano tuning 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 entries or bookings. A "piano tuning privacy" badge is not a verified storage path.
Piano-tuning booking, standing-appointment, 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 piano-tuning 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 March tuning or a September standing slot is a booking you create; a service name such as Steinway concert pitch or upright touch-up is a label you configure. Neither is a documented default. Make, room, recurring-slot, lesson-schedule, access-note, or service-address questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof a household owns a six-figure instrument or that someone will be home at a named time — and a CSV export of "Casey · 9 Maple St · Steinway B · inherited · room: living · slot: every Mar/Sep · lessons: Tue 4pm · access note: side door" next to a customer name is still a calendar that pairs a valuables-existence answer with visiting hours. 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. | Piano-tuning 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. Make, room, recurring-slot, lesson-schedule, access-note, or service-address fields are fields you add; they are not documented defaults. Completing the form can store a name-plus-address-plus-piano stack ("Casey · 9 Maple St · Steinway B · inherited · room: living · slot: every Mar/Sep · lessons: Tue 4pm · access note: side door") — typed or uploaded once so a shop can schedule a visit, into the same tables as a "piano tuning" label. A make, room, recurring-slot, or lesson-schedule answer is a form answer or uploaded file, not a verified inventory. A piano-tuning booking is a calendar row, not proof a household owns a six-figure instrument or that someone will be home at a named time — and a staff login can open "Casey, 9 Maple St, Steinway B, living room, every Mar/Sep, lessons Tue 4pm, side door" 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. | Name, service address, and piano answers stored in WordPress; optional instrument or room 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 make, room, recurring-slot, or lesson-schedule field was sent. A page request from this script is not proof anyone booked a tuning. The page URL can say piano tuning even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote 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. Make, room, recurring-slot, lesson-schedule, access-note, or service-address fields often depend on the fields you configure. A piano-tuning booking is a calendar row, not proof a household owns a six-figure instrument or that someone will be home at a named time. A make, room, recurring-slot, or lesson-schedule answer is a form answer or uploaded file, not a verified inventory. A marketing-tag page request is not proof anyone booked a tuning. The page URL can say piano tuning even when no form is submitted. The name-plus-address-plus-piano row that registered the instrument and its visiting hours for a shop — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that standing-appointment stack, not an alarm-company code-and-away schedule, an appliance-repair garage-code log, a gold-buyer photographed inheritance, or a music-lessons stranger-at-your-child's-door calendar. 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 "piano tuning privacy" or "standing appointment 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 burglary, theft targeting, instrument valuation, or ownership proof. 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
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-piano-tuning-plugin-privacy