Car rental plugin privacy
The return record that reconstructs every road you took
An independent car rental runs on a form stack that copies what Hertz collects without any of what Hertz is audited for: license scan, second ID, credit card, home address, and — on the return — the toll-transponder and GPS log that reconstruct every road you took. The booking says who you are; the return record says where you went. Chain rentals answer to PCI assessors and privacy counsel; the local lot answers to a contact-form plugin last updated in 2019. Those fields are configured, not documented defaults. A rental booking is a calendar row, not proof anyone drove or that a license was valid. A toll or GPS answer is a form answer or uploaded file, not a verified road-use record. A page request is not proof anyone rented a car. The page URL can say car rental even when no form is submitted. Ask what happens to the license scan, the second ID, the card, the home address, the toll tag, and the GPS trail after the rental closes — the stack that paired who you are with where you went outlives the keys. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking or return page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a PCI-compliance claim, a DMV or license-law claim, a toll-authority claim, a GPS or telematics-law claim, an insurer-underwriting claim, a subpoena-practice claim, a rental-regulation 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 rental bookings, return intakes, and page tags go
Intakes and bookings on your WordPress site
Check which license-scan, second-ID, card, home-address, toll-transponder, GPS-log, or intake-upload fields you enable, who can open form entries and rental bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a rental closes — when the license-plus-second-ID-plus-card-plus-home-plus-toll-plus-GPS row still holds who you are next to where you went. Notification emails can also copy those fields off-site. One table can list every "DL-scan.jpg, passport #X, Visa ••••4242, 12 Oak St, toll tag #8821, GPS trail 10/12–10/14" stack next to a renter name. Ask your web vendor not to keep license and card rows next to toll tags and GPS trails in one open submissions list longer than operations need, and to purge those fields when a rental closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored rental booking is not proof anyone drove or that a license was valid. A toll or GPS answer is not a verified road-use record.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking or return page. That page request can reach a vendor host before anyone submits. The page URL can say car rental even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and return pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "rental privacy" badge is not a verified storage path.
Rental booking, return-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 car-rental 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 Saturday 10am pickup window or a Monday return slot is a booking you create; a service name such as car rental or compact SUV is a label you configure. Neither is a documented default. License-scan, second-ID, card, home-address, toll-transponder, or GPS-log 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 drove or that a license was valid — and a CSV export of "DL-scan.jpg, passport #X, Visa ••••4242, 12 Oak St, toll tag #8821, GPS trail 10/12–10/14" next to a renter name is still a calendar that pairs who you are with where you went. 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. | Rental pickup and return 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. License-scan, second-ID, card, home-address, toll-transponder, or GPS-log fields are fields you add; they are not documented defaults. Completing the form can store a license-plus-second-ID-plus-card-plus-home-plus-toll-plus-GPS stack ("DL-scan.jpg, passport #X, Visa ••••4242, 12 Oak St, toll tag #8821, GPS trail 10/12–10/14") — typed once so a lot can rent and close a return, into the same tables as a "car rental" label. A toll or GPS answer is a form answer or uploaded file, not a verified road-use record. A rental booking is a calendar row, not proof anyone drove — and a staff login can open "Alex, DL-scan.jpg, Visa ••••4242, toll tag #8821, GPS trail 10/12–10/14" 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. | License, second-ID, card, home, toll, and GPS answers stored in WordPress; optional scans 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 license-scan, second-ID, card, home-address, toll-transponder, or GPS-log field was sent. A page request from this script is not proof anyone rented a car. The page URL can say car rental even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and return 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. License-scan, second-ID, card, home-address, toll-transponder, GPS-log, or intake-upload fields often depend on the fields you configure. A rental booking is a calendar row, not proof anyone drove or that a license was valid. A toll or GPS answer is a form answer or uploaded file, not a verified road-use record. A marketing-tag page request is not proof anyone rented a car. The page URL can say car rental even when no form is submitted. The license-plus-second-ID-plus-card-plus-home-plus-toll-plus-GPS row that pairs who you are with where you went — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that car-rental booking-plus-return ledger, not an RV multi-night itinerary, a boat float plan, a go-kart license kiosk, an auto-repair shop custody file, or a windshield-repair workday location. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or return page, and how long records and backups are kept. A "rental privacy" or "PCI ready" 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 PCI compliance, DMV or license law, toll authority practice, GPS or telematics law, insurer underwriting, subpoena practice, or rental regulation. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking and return 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-rental-plugin-privacy