Mastectomy boutique plugin privacy

The fitting appointment that records the diagnosis behind a retail purchase

A mastectomy boutique fitting form can look like a shop booking a bra, prosthesis, or wig slot. The same form can store surgery date, surgery type, which side, insurance details, and a chemo timeline for a wig consult. The visitor came for a fitting in a dressing room. The plugin table can hold those answers next to a retail booking. A marketing tag on the fitting page can send a page request to a vendor host before anyone submits. A page request is not proof anyone had surgery. A fitting booking is not a diagnosis record. The page URL can say mastectomy or fitting even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open bookings and entries, where uploaded files land, which tags load on the fitting page, and how long records, files, and backups are kept.

Documentation review only. This is not legal or medical advice, a HIPAA review, a medical-outcome claim, an insurance-coverage claim, an FDA 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 bookings, form entries, uploaded insurance-card or prescription scans, email inboxes, staff permissions, vendor accounts, or backups.

Where fitting bookings, intake files, and page tags go

Bookings and files handled on your WordPress site

Check which surgery-date, surgery-type, which-side, insurance, or chemo-timeline fields you enable, who can open bookings and form entries, where uploaded insurance-card or prescription scans live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect surgery details or insurance-card scans on the first public form, not to mix a chemo timeline with a public fitting calendar, and to purge bookings that never became purchases. A privacy-policy page does not by itself limit who can open a fitting list on a boutique site.

Page tags handled by a vendor

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

Mastectomy-boutique booking, form-upload, 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 boutique or mastectomy clinic software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

Documented self-hosted appointment plugin marketed for clinics and health practices (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 service name such as bra fitting, prosthesis fitting, or wig consult is a label you configure. It is not a documented default. Surgery-date, surgery-type, or which-side questions are custom fields you add (textarea, select, or input); they are not documented defaults. Completing the booking can record a fitting slot. A fitting booking is not a diagnosis record. Emails can include those custom fields. 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.

Fitting bookings and custom intake fields 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. Surgery-date, surgery-type, which-side, insurance, or chemo-timeline questions are fields you add; they are not documented defaults. Insurance-card or prescription scans are files you accept; they are not documented defaults. Completing the form can record a fitting intake. A form entry is not a diagnosis record. Notification emails can copy field values off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified.

Form entries stored in WordPress; file 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 surgery date, surgery type, which side, insurance, or a chemo timeline was sent. A page request from this script is not proof anyone had surgery. The page URL can say mastectomy or fitting even when no form is submitted. Consent timing has not been tested. Review which tags you enable on fitting 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. Surgery-date, surgery-type, which-side, insurance, chemo-timeline, insurance-card, or prescription fields often depend on the fields you configure. A fitting booking is not a diagnosis record. A form entry is not a finished fitting. A marketing-tag page request is not proof anyone had surgery. The page URL can say mastectomy or fitting even when no form is submitted. This page is about the fitting form that stores surgery details next to a retail booking, not salon appointments, pharmacy refill uploads, or therapy notes. Ask your web vendor who can open bookings and entries, where uploaded files live, whether a marketing tag loads on the fitting page, and how long records and backups are kept. A "secure" or "private fitting" 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 HIPAA, FDA rules, medical outcomes, or insurance coverage. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on fitting pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-mastectomy-boutique-plugin-privacy