Car wash plugin privacy
The unlimited-wash membership that logs your plate every visit
Unlimited-wash memberships work by reading a license plate at the gate — so a low monthly subscription quietly builds a visit log keyed to that plate: which location, what time, how often, tied to a name, card, and home address in a WordPress membership or booking stack. It is a small ALPR-style visit ledger run by a car wash, and nobody at the register calls it surveillance because it is just the camera that opens the gate. Those fields are configured, not documented defaults. A membership booking is a calendar row, not proof anyone washed a car. A plate answer is what a member typed or a gate system wrote, not a DMV record. An intake upload is a client document in a site uploads folder. A page request is not proof anyone opened the gate. The page URL can say car wash even when no form is submitted. Ask what happens to the plate answers and the visit timestamps after a membership lapses — the unlimited-wash membership that logs your plate every visit outlives the rinse. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, an ALPR-law or surveillance-law claim, a traffic-camera-legality claim, an insurer-underwriting claim, a police-use-of-wash-logs 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 wash memberships, plate intakes, and page tags go
Intakes and bookings on your WordPress site
Check which plate, membership-ID, visit-timestamp, location, home-address, or intake-upload fields you enable, who can open form entries and wash-membership bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a membership lapses — when the unlimited-wash membership logs your plate every visit. Notification emails can also copy those fields off-site. One table can list every plate answer a member typed next to a Friday slot and a location label. Ask your web vendor not to keep intake uploads next to plate answers in one open submissions list longer than operations need, and to purge booking rows when a membership ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored membership booking is not proof anyone washed a car. A plate answer is not a DMV record.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the car-wash membership or plate-intake page. That page request can reach a vendor host before anyone submits. The page URL can say car wash even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off membership signup and plate-intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "wash privacy" badge is not a verified storage path.
Wash-membership booking, plate-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 wash or ALPR 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 Friday express-wash slot or an unlimited-wash membership package is a booking you create; a service name such as car wash or plate membership is a label you configure. Neither is a documented default. Plate, membership-ID, visit-timestamp, or location 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 washed a car — and a CSV export of a Friday 3pm express slot next to a plate answer and a home address is still a calendar that holds a visit ledger beside a contact name. 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. | Wash-membership 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. Plate, membership-ID, visit-timestamp, location, or home-address fields are fields you add; they are not documented defaults. Completing the form can store a plate answer next to a visit timestamp, a location label, a membership ID, a home address, and optional intake uploads — typed once as the unlimited-wash membership that logs your plate every visit, into the same tables as a monthly wash bill. A plate answer is what a member typed or a gate system wrote, not a DMV record. A membership booking is a calendar row, not proof anyone washed a car — and a staff login can open "Alex, plate ABC1234, North site, Friday 3pm, license.pdf" 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. | Car-wash membership and plate-intake answers stored in WordPress; optional intake 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 plate, membership-ID, visit-timestamp, or location field was sent. A page request from this script is not proof anyone opened the gate. The page URL can say car wash even when no form is submitted. Consent timing has not been tested. Review which tags you enable on membership signup and plate-intake 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. Plate, membership-ID, visit-timestamp, location, home-address, or intake-upload fields often depend on the fields you configure. A membership booking is a calendar row, not proof anyone washed a car. A plate answer is what a member typed or a gate system wrote, not a DMV record. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone opened the gate. The page URL can say car wash even when no form is submitted. The unlimited-wash membership that logs your plate every visit — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that plate-keyed visit ledger, not an impound tow log, a repossession file, a title-loan packet, or an ignition-interlock device record. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long records and backups are kept. A "wash privacy" or "ALPR 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 ALPR law, surveillance law, traffic-camera legality, insurer underwriting, or police use of wash visit logs. Review stored records, bookings, connected services, exports, notification emails, marketing tags on membership and plate-intake 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-car-wash-plugin-privacy