Wig salon plugin privacy

The fitting appointment that dates the diagnosis

A wig-salon booking page can look like a retail calendar and a style form. The same form often asks why the hair is gone, when treatment starts, whether a cranial-prosthesis claim will be filed, and which style to match — plus a before photo taken while she still has hair — and stores those answers next to the client's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a chemo start date next to a reason-for-hair-loss select and a photo taken for color matching — the fitting that dates the diagnosis, typed once into a vendor table next to a marketing pixel. A fitting request is not a diagnosis. A reason-for-hair-loss answer is what the client chose to type, not a medical record. An uploaded insurance form is a stored document, not proof of coverage or treatment. A before photo is an upload the client made, not a clinical image. A page request is not proof anyone is ill. The page URL can say wig salon even when no form is submitted. Ask what happens to the reason-for-hair-loss answer and the before photo after the fitting — the appointment dates the diagnosis, and the row outlives the visit. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, an insurance-reimbursement claim, an oncology or treatment-outcomes claim, a HIPAA coverage claim for retail salons, a wig quality or medical-suitability 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 fitting bookings, hair-loss notes, and page tags go

Bookings and notes on your WordPress site

Check which reason-for-hair-loss, treatment-timeline, insurance-coverage-question, or style-reference fields you enable, who can open form entries and consult, fitting, or follow-up bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the fitting appointment dates the diagnosis. Notification emails can also copy those fields off-site. One table can list every follow-up fitting next to a chemo start date and a before photo. Ask your web vendor not to keep reason-for-hair-loss next to treatment-timeline in one open submissions list longer than operations need, and to purge intake rows when the booking ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not a diagnosis. An uploaded insurance form is not proof of coverage.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the wig-salon booking page. That page request can reach a vendor host before anyone submits. The page URL can say wig salon even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "medical wig specialist" badge is not a verified storage path.

Consult / fitting / follow-up booking, hair-loss intake, 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 cranial-prosthesis SaaS platforms without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A consult slot, a fitting, or a follow-up six weeks out is a booking you create; a service name such as medical-wig consult, cranial-prosthesis fitting, or follow-up fitting is a label you configure. Neither is a documented default. Reason-for-hair-loss, treatment-timeline, insurance-coverage-question, or style-reference questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a diagnosis — and a CSV export of a follow-up fitting next to a chemo start date is still a calendar of when the hair is expected to be gone. 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.

Consult, fitting, and follow-up bookings stored 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-hair-loss, treatment-timeline, insurance-coverage-question, or style-reference questions are fields you add; they are not documented defaults. Completing the form can store a reason-for-hair-loss answer next to a treatment-timeline field, an insurance-coverage-question, a style-reference note, and optional before-photo or "cranial prosthesis" insurance-paperwork uploads — typed once as the fitting that dates the diagnosis into the same tables as a newsletter signup. A fitting request is not a diagnosis. A reason-for-hair-loss answer is what the client chose to type, not a medical record. An uploaded insurance form is a stored document, not proof of coverage or treatment. A before photo is an upload the client made, not a clinical image — and a staff login can open "chemotherapy, start date June 12, will file cranial prosthesis claim" next to a photo taken while she still had hair. 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.

Hair-loss intake entries stored in WordPress; optional before-photo and insurance-paperwork 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-hair-loss, treatment-timeline, insurance-coverage-question, or style-reference field was sent. A page request from this script is not proof anyone is ill. The page URL can say wig salon even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake pages.

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-hair-loss, treatment-timeline, insurance-coverage-question, or style-reference fields often depend on the fields you configure. A fitting request is not a diagnosis. A reason-for-hair-loss answer is what the client chose to type, not a medical record. An uploaded insurance form is a stored document, not proof of coverage or treatment. A before photo is an upload the client made, not a clinical image. A marketing-tag page request is not proof anyone is ill. The page URL can say wig salon even when no form is submitted. The fitting appointment that dates the diagnosis — that is a storage path next to a treatment-timeline field, not a feature these plugins claim. This page is about that fitting intake, not a cosmetic salon patch test, an elective hair-restoration consult, a prosthetics clinic, a home-care plan, or a hospice intake. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "medical wig specialist" 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 insurance-reimbursement rules, oncology or treatment outcomes, HIPAA coverage status of retail salons, or wig quality or medical suitability. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.

Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-wig-salon-plugin-privacy