Auto detailing plugin privacy
The add-on checklist that inventories your household through your car
Nobody types a confession into a detailing form. They tick boxes: pet-hair removal, child-seat deep clean, smoke-odor treatment, biohazard interior recovery. Each checkbox is a fact about the people who ride in that car, and the service menu quietly assembles a household profile keyed to a name, address, and vehicle. That row can sit in a form plugin entries table any staffer can open. Pet-hair, child-seat, smoke-odor, biohazard, add-on-checklist, vehicle, plate, make-model, address, owner-name, phone, drop-off-window, and interior-photo fields are configured, not documented defaults. Optional interior photos go in the site uploads folder. A pet-hair add-on is a stored service label, not proof they have a pet. A child-seat add-on is a stored service label, not proof of children. A smoke-odor add-on is a stored service label, not proof of smoking. A biohazard add-on is a stored service label, not proof of an incident. An add-on checklist is a stored selection, not a household census. A vehicle or plate is a stored label, not a verified registration. A property address is a stored location, not a verified residence. An interior photo is an upload, not proof of what is in the car. An auto-detailing booking is not proof anyone booked a detail. A page request is not proof anyone booked. The page URL can say auto detailing even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on booking and quote pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a carpet-cleaning claim, a car-wash claim, a windshield-repair claim, an auto-repair claim, an insurance 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 detailing quotes, interior photos, and page tags go
Detailing bookings and forms handled on your WordPress site
Check which pet-hair, child-seat, smoke-odor, biohazard, add-on-checklist, vehicle, plate, make-model, address, owner-name, phone, drop-off-window, or interior-photo fields you enable, who can open form entries and bookings, where uploaded interior photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a detailing job. Notification emails can also copy the same add-on ticks, vehicles, plates, addresses, interior photos, and owner names off-site. One table can name the household through the car, the add-on checklist, and the address next to a phone, even when the detail is never sold. Ask your web vendor not to collect a pet-hair, child-seat, smoke-odor, or biohazard add-on next to a name, address, and vehicle on the first public form, not to store those interior photos next to a drop-off window in one open submissions list, and to purge unused quotes after the date passes. A privacy-policy page does not by itself limit who can export a quote list or republish an upload. A stored quote is not proof anyone booked a detail.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the auto-detailing booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say auto detailing 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 add-on checklists, interior photos, or vehicle labels. A "mobile detailing" badge is not a verified storage path.
Auto-detailing booking, quote, 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 auto-detailing shop software without a WordPress.org listing is 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). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. An auto-detailing visit is a booking you create; a service name such as auto detailing, interior detail, pet-hair removal, child-seat deep clean, smoke-odor treatment, or biohazard interior recovery is a label you configure. Neither is a documented default. The stored service name can say auto detailing in plain text before anyone arrives. Pet-hair, child-seat, smoke-odor, biohazard, add-on-checklist, vehicle, plate, make-model, address, owner-name, phone, or drop-off-window questions are custom fields you add (textarea, select, or input); they are not documented defaults. A pet-hair add-on is a stored service label, not proof they have a pet. A child-seat add-on is a stored service label, not proof of children. A smoke-odor add-on is a stored service label, not proof of smoking. A biohazard add-on is a stored service label, not proof of an incident. An add-on checklist is a stored selection, not a household census. A vehicle or plate is a stored label, not a verified registration. A property address is a stored location, not a verified residence. A booked slot is not proof anyone booked a detail, and is not proof a car was cleaned. Cancelling or missing the slot later does not erase the add-on ticks, vehicle, address, or drop-off window already stored next to a name, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never became a detailing job is not a documented default of the plugin. The appointments list can show who is booked this week and which add-ons they ticked. 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. | Auto-detailing bookings, custom add-on fields, and automatic confirmation emails 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. Pet-hair, child-seat, smoke-odor, biohazard, add-on-checklist, vehicle, plate, make-model, address, owner-name, phone, or drop-off-window questions are fields you add; they are not documented defaults. Interior photos are files you accept; those file types are not documented defaults. A pet-hair add-on is a stored service label, not proof they have a pet. A child-seat add-on is a stored service label, not proof of children. A smoke-odor add-on is a stored service label, not proof of smoking. A biohazard add-on is a stored service label, not proof of an incident. An add-on checklist is a stored selection, not a household census. A vehicle or plate is a stored label, not a verified registration. A property address is a stored location, not a verified residence. An interior photo is an upload, not proof of what is in the car. An auto-detailing booking is not proof anyone booked a detail. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a pairing sits after a request that never became a detailing job is not a documented default of the plugin. | Quote and interior-photo entries stored in WordPress; file 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 pet-hair, child-seat, smoke-odor, or biohazard add-on field was sent. A page request from this script on an auto-detailing quote page is not proof anyone booked, and a pre-consent tag on that page can still treat auto-detailing interest as an audience segment from the URL alone. The page URL can say auto detailing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote pages. Keep marketing tags off those pages if you do not want that page request. A tagged quote page can re-confirm auto-detailing interest next to a stored address; this row does not claim a detailing job from that request. | 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. Pet-hair, child-seat, smoke-odor, biohazard, add-on-checklist, vehicle, plate, make-model, address, owner-name, phone, drop-off-window, or interior-photo fields often depend on the fields you configure. A pet-hair add-on is a stored service label, not proof they have a pet. A child-seat add-on is a stored service label, not proof of children. A smoke-odor add-on is a stored service label, not proof of smoking. A biohazard add-on is a stored service label, not proof of an incident. An add-on checklist is a stored selection, not a household census. A vehicle or plate is a stored label, not a verified registration. A property address is a stored location, not a verified residence. An interior photo is an upload, not proof of what is in the car. An auto-detailing booking is not proof anyone booked a detail. A marketing-tag page request is not proof anyone booked. The page URL can say auto detailing even when no form is submitted. The add-on checklist, the vehicle, and the address can sit after a request that never became a detailing job. This page is about the add-on checklist that inventories your household through your car, not a carpet-cleaning stain log, not a car-wash plate log, not a windshield mobile location, and not an auto-repair license scan. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or quote page, and how long records and backups are kept. A "mobile detailing" 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 carpet-cleaning, car-wash, windshield, auto-repair, or insurance claims. Review stored records, uploaded files, 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-auto-detailing-plugin-privacy