Dry cleaner plugin privacy
The rack of clothes with strangers' phone numbers stapled to them
A dry cleaner's privacy surface is visible from the sidewalk: a conveyor of garments, each tagged with a name and phone number anyone at the counter can read. The booking plugin moves that rack online — pickup/delivery routes that learn when your house is empty, order histories that log the uniform (your employer), the gown (your event), the same suit cleaned every Monday (your routine). The ticket was always public; the plugin makes it queryable. Those fields are configured, not documented defaults. A cleaning booking is a calendar row, not proof anyone dropped off a garment or that a route ran. A garment or route answer is a form answer or typed note, not a verified routine. A page request is not proof anyone used a dry cleaner. The page URL can say dry cleaner even when no form is submitted. Ask what happens to the names, the phone numbers, the garment descriptions, and the delivery routes after an order closes — the stack that made the sidewalk rack queryable outlives the ticket. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the ticket or booking page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a laundry-business-regulation claim, an employer-uniform-inference claim, an event-attendance-inference claim, a vacancy-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 tickets, pickup bookings, and page tags go
Tickets and bookings on your WordPress site
Check which name, phone, garment-description, pickup/delivery-address, route-window, order-history, or intake-upload fields you enable, who can open form entries and pickup bookings, which inboxes receive copies, and how long records, emails, and backups are kept after an order closes — when the name-plus-phone-plus-garment-plus-route row still holds a queryable ticket rack. Notification emails can also copy those fields off-site. One table can list every "ticket #4412 · Jordan · 555-0142 · navy suit Mon pickup · delivery route Tue 10am · 12 Oak St" stack next to a customer name. Ask your web vendor not to keep phone numbers and garment tickets next to delivery routes in one open submissions list longer than operations need, and to purge those fields when an order closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored cleaning booking is not proof anyone dropped off a garment or that a route ran. A garment or route answer is not a verified routine.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the ticket or booking page. That page request can reach a vendor host before anyone submits. The page URL can say dry cleaner even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off ticket and booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "dry cleaner privacy" badge is not a verified storage path.
Dry-cleaner ticket, pickup 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 dry-cleaner 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 Monday pickup window or a Tuesday delivery slot is a booking you create; a service name such as suit press or garment delivery is a label you configure. Neither is a documented default. Name, phone, garment-description, pickup/delivery-address, route-window, or order-history 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 dropped off a garment or that a route ran — and a CSV export of "ticket #4412 · Jordan · 555-0142 · navy suit Mon pickup · delivery route Tue 10am · 12 Oak St" next to a customer name is still a calendar that pairs a queryable ticket rack 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. | Dry-cleaner pickup 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. Name, phone, garment-description, pickup/delivery-address, route-window, or order-history fields are fields you add; they are not documented defaults. Completing the form can store a name-plus-phone-plus-garment-plus-route stack ("ticket #4412 · Jordan · 555-0142 · navy suit Mon pickup · delivery route Tue 10am · 12 Oak St") — typed once so a cleaner can tag a rack and run a route, into the same tables as a "dry cleaner" label. A garment or route answer is a form answer or typed note, not a verified routine. A cleaning booking is a calendar row, not proof anyone dropped off a garment — and a staff login can open "Jordan, 555-0142, navy suit, Mon pickup, Tue 10am delivery, 12 Oak St" 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, phone, garment, and route answers stored in WordPress; optional 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 name, phone, garment, or route field was sent. A page request from this script is not proof anyone used a dry cleaner. The page URL can say dry cleaner even when no form is submitted. Consent timing has not been tested. Review which tags you enable on ticket and booking 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. Name, phone, garment-description, pickup/delivery-address, route-window, or order-history fields often depend on the fields you configure. A cleaning booking is a calendar row, not proof anyone dropped off a garment or that a route ran. A garment or route answer is a form answer or typed note, not a verified routine. A marketing-tag page request is not proof anyone used a dry cleaner. The page URL can say dry cleaner even when no form is submitted. The name-plus-phone-plus-garment-plus-route row that made the sidewalk rack queryable — that is a storage path next to delivery addresses, not a feature these plugins claim. This page is about that queryable ticket rack, not a house-cleaning in-home worker schedule, a consignment letting-go intake, a jewelry-repair custody ticket, or a snow-removal two-address empty-house contract. Ask your web vendor who can open entries, whether a marketing tag loads on the ticket or booking page, and how long records and backups are kept. A "dry cleaner privacy" or "laundry 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 laundry-business regulation, employer-uniform inference, event-attendance inference, or vacancy inference. Review stored records, bookings, connected services, exports, notification emails, marketing tags on ticket and booking 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-dry-cleaner-plugin-privacy