Tailor plugin privacy
The alteration ticket that logs your measurements and the funeral they were for
An alteration ticket is a body ledger nobody thinks of as data: chest, waist, hip, inseam — exact numbers you would not read aloud — pinned to your name and the occasion you need the garment for. "Let out 2 inches since last fitting" turns revision notes into a weight-change timeline; "needed by the 14th — funeral" attaches your worst week to your measurements. Tailors keep customer records for decades; their booking plugin now does too, on a website last updated when the shop opened. Those fields are configured, not documented defaults. An alteration booking is a calendar row, not proof anyone was measured or attended a fitting. A revision note is a shop label, not a medical weight record. A page request is not proof anyone booked an alteration. The page URL can say tailor even when no form is submitted. Ask what happens to the measurements, name, occasion date, and revision notes after the fitting ends — the ticket that mapped a body ledger to a funeral week outlives the hem. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the alteration page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a garment-fit claim, an alteration-quality claim, a funeral or wedding-service claim, a body-image-counseling claim, a medical-fitting 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 measurement answers, alteration bookings, and page tags go
Intakes and bookings on your WordPress site
Check which chest/waist/hip/inseam, occasion-date, revision-note, fitting-photo, or name fields you enable, who can open form entries and tailor alteration bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the fitting ends — when the ticket that mapped a body ledger to a funeral week still holds that row. Notification emails can also copy those fields off-site. One table can list every decade of customers next to chest and waist numbers, a named client, a funeral-week due date, and a "let out 2 inches" revision note. Ask your web vendor not to keep body measurements next to names and occasion dates in one open submissions list longer than operations need, and to purge those fields when a ticket closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored tailor alteration booking is not proof anyone was measured or attended a fitting. A revision note is not a medical weight record.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the tailor alteration page. That page request can reach a vendor host before anyone submits. The page URL can say tailor even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off alteration pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "tailor privacy" badge is not a verified storage path.
Tailor alteration-booking, measurement-intake, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty tailor / alterations SaaS tools without a WordPress.org listing are outside this sample.
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
| 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 funeral-week occasion date or a hem-and-take-in service name is a booking you create; a service name such as tailor or alterations is a label you configure. Neither is a documented default. Chest/waist/hip/inseam, occasion-date, revision-note, fitting-photo, or name 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 was measured — and a CSV export of "chest 42 / waist 36 / needed by the 14th — funeral" next to a named customer is still a calendar that holds a body ledger under one tailor reservation. 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. | Tailor alteration 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. Chest/waist/hip/inseam, occasion-date, revision-note, fitting-photo, or name fields are fields you add; they are not documented defaults. Completing the form can store chest, waist, hip, and inseam next to a named customer, a "needed by the 14th — funeral" occasion, a "let out 2 inches since last fitting" revision note, and a fitting-photo upload — typed once so the shop does not have to re-measure, into the same tables as a tailor label. A revision note is a shop label, not a medical weight record. An alteration booking is a calendar row, not proof anyone was measured — and a staff login can open "chest 42 / waist 36 — funeral by the 14th + named customer" next to every other decade-old ticket the shop still keeps. 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. | Alteration measurement answers stored in WordPress; optional fitting-photo 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 a chest/waist/hip/inseam, occasion-date, revision-note, or name field was sent. A page request from this script is not proof anyone booked an alteration. The page URL can say tailor even when no form is submitted. Consent timing has not been tested. Review which tags you enable on tailor alteration 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. Chest/waist/hip/inseam, occasion-date, revision-note, fitting-photo, or name fields often depend on the fields you configure. An alteration booking is a calendar row, not proof anyone was measured or attended a fitting. A revision note is a shop label, not a medical weight record. A marketing-tag page request is not proof anyone booked an alteration. The page URL can say tailor even when no form is submitted. The ticket that mapped a body ledger to a funeral week — that is a storage path next to names and measurements, not a feature these plugins claim. This page is about that decade-scale alteration body ledger, not a dance-studio child measurement chart, a clinical weigh-in form, a wig-salon appearance change, a mastectomy-boutique fitting, or a wedding-planner event-date record. Ask your web vendor who can open entries, whether a marketing tag loads on the alteration page, and how long records and backups are kept. A "tailor privacy" or "alterations-safe" 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 garment fit, alteration quality, funeral or wedding services, body-image counseling, or medical fitting. Review stored records, bookings, connected services, exports, notification emails, marketing tags on alteration 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-tailor-plugin-privacy