Limo service plugin privacy

The booking that lists other people's children by pickup address

A limo company's booking page can look like a quote call and a reservation form. The same form often asks occasion, pickup address and time, passenger list, destination and return, and special requests — plus route-sheet and event-ticket uploads — and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can record that a parent typed five teenagers' names and home addresses into a prom itinerary so a dispatcher can plan the route — every family on the list is in the row, and only one of them touched the form. The airport run is the opposite disclosure: "pickup 4:15am to JFK, return Sunday" is a signed, dated certificate of an empty house, stored with the address it empties. The quietest field is the occasion dropdown — bachelor party, prom, funeral, anniversary — a one-word label that tells the vendor what kind of night it was, kept long after the ride ends. A reservation is a calendar row, not proof the trip happened. A passenger list is the booker's roster — the passengers named, including minors, never touched the form. An occasion label is the booker's framing, not a verified life event. A pickup time is a plan, not a verified absence. An uploaded event ticket is a client document in a site uploads folder. A page request is not proof anyone is traveling. The page URL can say limo even when no form is submitted. Ask what happens to the passenger list and the event-ticket upload after the ride — the booking lists other people's children by pickup address, and the row outlives the night. 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 livery or chauffeur-licensing claim, an alcohol or DUI-law claim, a driver-vetting claim, a passenger-safety 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 reservation bookings, booking intakes, and page tags go

Intakes and bookings on your WordPress site

Check which occasion, pickup-address-and-time, passenger-list, destination-and-return, or special-requests fields you enable, who can open form entries and reservation bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a booking closes — when the booking lists other people's children by pickup address. Notification emails can also copy those fields off-site. One table can list every minor's name a parent typed next to an occasion label and a pickup address. Ask your web vendor not to keep event tickets next to passenger lists in one open submissions list longer than operations need, and to purge booking rows when the ride is declined or closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored reservation is not proof the trip happened. An uploaded route sheet is not a verified itinerary.

Page tags handled by a vendor

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

Reservation, limo booking 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 limo CRM SaaS platforms without a WordPress.org listing are outside this sample.

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 quote-call or reservation booking is a booking you create; a service name such as airport transfer, prom package, or hourly charter is a label you configure. Neither is a documented default. Occasion, pickup-address-and-time, passenger-list, destination-and-return, or special-requests questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof the trip happened — and a CSV export of reservations next to a passenger list and an occasion label is still a booking row after someone asked about a ride. 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.

Limo quote-call and reservation 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. Occasion, pickup-address-and-time, passenger-list, destination-and-return, or special-requests questions are fields you add; they are not documented defaults. Completing the form can store a passenger list next to an occasion label, a pickup address and time, a destination and return, and optional route-sheet or event-ticket uploads — typed once by a booker into the same tables as a newsletter signup. A reservation is a calendar row, not proof the trip happened. A passenger list is the booker's roster, not the passengers' disclosure — the people it names, including minors, never touched the form. An occasion label is the booker's framing, not a verified life event. A pickup time is a plan, not a verified absence. An uploaded event ticket is a client document in uploads/forminator, not a verified ticket. A staff login can open the passenger list next to the prom pickup addresses. 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.

Limo booking intake entries stored in WordPress; optional route-sheet and event-ticket 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 an occasion, pickup-address-and-time, passenger-list, destination-and-return, or special-requests field was sent. A page request from this script is not proof anyone is traveling. The page URL can say limo even when no form is submitted. Consent timing has not been tested. Review which tags you enable on quote and reservation 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. Occasion, pickup-address-and-time, passenger-list, destination-and-return, or special-requests fields often depend on the fields you configure. A reservation is a calendar row, not proof the trip happened. A passenger list is the booker's roster — the passengers named, including minors, never touched the form. An occasion label is the booker's framing, not a verified life event. A pickup time is a plan, not a verified absence. An uploaded event ticket is a client document in a site uploads folder. A marketing-tag page request is not proof anyone is traveling. The page URL can say limo even when no form is submitted. The booking lists other people's children by pickup address — that is a storage path next to passenger names, not a feature these plugins claim. This page is about that limo booking intake, not a medical-transport ride schedule, a pet-sitting calendar, or a school-carpool roster. 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 "private transportation" 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 livery or chauffeur licensing, alcohol or DUI law, driver vetting, or passenger safety. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-limo-service-plugin-privacy