Auto repair plugin privacy

The drop-off form that ties your plate to your address and scans your license for the loaner

A repair shop's booking plugin quietly becomes a plate-to-person registry: the drop-off form binds a license plate to a name, phone, and home address, and the loaner-car agreement uploads a driver's license scan to the same database. The "describe the problem" box is a dated diary of where the car was and what it was doing, and the service history says which weekday your driveway is reliably empty. None of it feels medical or financial — which is exactly why nobody treats a muffler shop's WordPress install as an identity store. Those fields are configured, not documented defaults. A drop-off booking is a calendar row, not proof anyone serviced a car. A plate answer is what a customer typed, not a DMV lookup. An intake upload is a client document in a site uploads folder. A page request is not proof anyone repaired a vehicle. The page URL can say auto repair even when no form is submitted. Ask what happens to the plate, address, phone, problem note, service weekday, and license scan after a repair ends — the drop-off form that ties your plate to your address and scans your license for the loaner outlives the visit. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the drop-off page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a plate-privacy-law claim, a driver's-license-law claim, an identity-theft-law claim, an empty-home-law claim, a DMV-record-law 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 form entries, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where drop-off answers, loaner bookings, and page tags go

Intakes and bookings on your WordPress site

Check which plate, name, phone, home-address, problem-description, service-history weekday, or loaner-agreement fields you enable, who can open form entries and drop-off bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a repair ends — when the drop-off form ties your plate to your address and scans your license for the loaner. Notification emails can also copy those fields off-site. One table can list every plate a customer typed next to a name, phone, home address, a "clunk leaving the office lot Tuesday" problem note, a Thursday service slot, and a driver's-license scan. Ask your web vendor not to keep plates next to addresses and license scans in one open submissions list longer than operations need, and to purge identity fields when a repair closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored drop-off booking is not proof anyone serviced a car. A plate answer is not a DMV lookup.

Page tags handled by a vendor

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

Drop-off, loaner-booking, and marketing-tag setups

Three plugins reviewed from public documentation. Specialty shop-management / DMS 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.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 Thursday brake-inspect slot or a loaner handoff window is a booking you create; a service name such as auto repair or oil change is a label you configure. Neither is a documented default. License-plate, home-address, phone, problem-description, service-history weekday, or loaner-agreement 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 serviced a car — and a CSV export of "ABC-1234, 14 Oak St, clunk leaving the office lot Tuesday, Thu service" next to a contact name is still a calendar that holds a plate-to-person registry beside a customer row. 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.

Drop-off and loaner bookings 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. License-plate, name, phone, home-address, problem-description, service-history weekday, or loaner-agreement fields are fields you add; they are not documented defaults. Completing the form can store a plate next to a name, phone, home address, a dated "describe the problem" note, a Thursday service slot that marks when the driveway sits empty, a contact name, and optional loaner-agreement or driver's-license-scan uploads — typed once so the advisor does not have to rewrite the RO, into the same tables as an oil-change package name. A plate answer is what a customer typed, not a DMV lookup. A drop-off booking is a calendar row, not proof anyone serviced a car — and a staff login can open "ABC-1234, 14 Oak St, clunk leaving the office lot Tuesday, Thu, DL scan" 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.

Plate, address, and problem-note answers stored in WordPress; optional loaner-agreement or driver's-license 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 a plate, address, phone, problem-description, service-history weekday, or loaner-agreement field was sent. A page request from this script is not proof anyone repaired a vehicle. The page URL can say auto repair even when no form is submitted. Consent timing has not been tested. Review which tags you enable on drop-off intake and booking 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. Plate, address, phone, problem-description, service-history, or loaner-agreement fields often depend on the fields you configure. A drop-off booking is a calendar row, not proof anyone serviced a car. A plate answer is what a customer typed, not a DMV lookup. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone repaired a vehicle. The page URL can say auto repair even when no form is submitted. The drop-off form that ties your plate to your address and scans your license for the loaner — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that plate-to-person and loaner-ID stack, not a towing roadside location-at-crisis log, a car-wash plate membership cadence, a DUI-school court-adjacent driving record, a traffic-school violation enrollment, or a limo-service chauffeured itinerary. Ask your web vendor who can open entries, whether a marketing tag loads on the drop-off page, and how long records and backups are kept. An "auto repair privacy" or "shop-management 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 plate-privacy law, driver's-license law, identity-theft law, empty-home law, or DMV-record law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on drop-off and booking pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-auto-repair-plugin-privacy