Windshield repair plugin privacy
The mobile booking that records where your car sits every workday
Mobile glass repair is the only vehicle service you book to meet your car where it sits — so the form asks the question shop-based siblings never need: where does this car spend the day? "Office lot on 5th, parked level 2, there 8-5 Mon-Fri" is a written record of your daily routine, filed with your plate, VIN, and insurance claim number. Shop-based forms know what you drive; this one knows where to find the car — and you — every workday. The shop's WordPress keeps that workday-parking-plus-vehicle row long after the chip is filled. Those fields are configured, not documented defaults. A booking is a service appointment, not proof of a daily parking routine. A parking-location answer is a stored service instruction, not proof anyone followed that routine. A plate, VIN, or claim answer is an identifier field, not an ownership or underwriting finding. A page request is not proof anyone booked a repair. The page URL can say windshield repair even when no form is submitted. Ask what happens to the workday-parking note, the plate, the VIN, the claim number, and any chip photo after the repair closes — the meet-your-car row that answered where to find someone's car 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 booking page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a glass-repair-licensing claim, an insurance-claims-handling claim, a VIN-fraud claim, an ALPR or parking-lot surveillance-law claim, a stalking claim, a traffic-law claim, a technician-background-check 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 booking intakes, service appointments, and page tags go
Intakes and bookings on your WordPress site
Check which workday-parking-location, plate, VIN, insurance-claim-number, or chip-photo fields you enable, who can open form entries and service bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the repair closes — when the workday-parking-plus-vehicle row still holds where the car sits every workday. Notification emails can also copy those fields off-site. One table can list every "Office lot on 5th, level 2, 8-5" note next to a plate, VIN, claim number, and chip photo. Ask your web vendor not to keep parking-location notes next to plate and VIN rows 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 booking is not proof of a daily parking routine. A parking-location answer is not proof anyone followed that routine.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the windshield-repair booking page. That page request can reach a vendor host before anyone submits. The page URL can say windshield repair even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "windshield repair privacy" badge is not a verified storage path.
Windshield-repair-booking, service-appointment, 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-glass / mobile-technician 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 workday-parking note or a "mobile chip repair — Office lot on 5th, level 2, 8-5 Mon-Fri" location answer is a booking you create; a service name such as windshield repair or mobile glass is a label you configure. Neither is a documented default. Workday-parking-location, plate, VIN, insurance-claim-number, or chip-photo questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof of a daily parking routine — and a CSV export of "Office lot on 5th, level 2, 8-5 + plate + VIN + claim #" next to a named driver is still a calendar that answers where to find that car every workday under one service visit. 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. | Windshield-repair service 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. Workday-parking-location, plate, VIN, insurance-claim-number, or chip-photo fields are fields you add; they are not documented defaults. Completing the form can store a workday-parking note ("Office lot on 5th, parked level 2, there 8-5 Mon-Fri") next to a plate, VIN, insurance claim number, and a chip photo — typed once so the mobile tech can meet the car where it sits, into the same tables as a windshield-repair label. A parking-location answer is a stored service instruction, not proof anyone followed that routine. A booking request is a service appointment, not proof of a daily parking pattern — and a staff login can open "Office lot on 5th + plate + VIN + claim #" next to every other mobile-meet booking long after the chip is filled. 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. | Workday-parking and vehicle answers stored in WordPress; optional chip-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 workday-parking-location, plate, VIN, insurance-claim-number, or chip-photo field was sent. A page request from this script is not proof anyone booked a repair. The page URL can say windshield repair even when no form is submitted. Consent timing has not been tested. Review which tags you enable on windshield-repair 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. Workday-parking-location, plate, VIN, insurance-claim-number, or chip-photo fields often depend on the fields you configure. A booking is a service appointment, not proof of a daily parking routine. A parking-location answer is a stored service instruction, not proof anyone followed that routine. A plate/VIN/claim answer is an identifier field, not an ownership or underwriting finding. A marketing-tag page request is not proof anyone booked a repair. The page URL can say windshield repair even when no form is submitted. The workday-parking-plus-vehicle row that holds where a car sits every workday — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that meet-your-car stack, not an auto-repair shop drop-off, a car-wash membership plate log, a towing one-time distress location, or a go-kart license-kiosk intake. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "windshield repair privacy" or "mobile-glass 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 glass-repair licensing, insurance claims handling, VIN fraud, ALPR or parking-lot surveillance law, stalking, traffic law, or technician background checks. Review stored records, bookings, connected services, exports, notification emails, marketing tags on 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-windshield-repair-plugin-privacy