Boat rental plugin privacy

The float plan that names everyone aboard and where you'll anchor

A boat rental's booking form doubles as a float plan: every passenger's name, the route, and where you'll be anchored overnight — filed with a marina so someone knows where to look if you don't come back. Add the boater-license upload, the damage-deposit card, and GPS trackers many fleets run on their hulls, and a weekend on the water becomes a passenger manifest plus a location trail, stored in the same WordPress plugin that rents kayaks. The safety document is the surveillance document; nobody aboard but the renter ever saw the form. Those fields are configured, not documented defaults. A boat booking is a calendar row, not proof anyone left the dock. A passenger answer is what a renter typed, not a Coast Guard file. An intake upload is a client document in a site uploads folder. A page request is not proof anyone boarded. The page URL can say boat rental even when no form is submitted. Ask what happens to the named passenger, route, anchorage, license, deposit, and GPS rows after a weekend on the water ends — the float plan that names everyone aboard and where you'll anchor outlives the pontoon. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the reservation page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a maritime-law claim, a boating-safety-law claim, a location-tracking-law claim, a passenger-manifest-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 float-plan intakes, boat bookings, and page tags go

Intakes and bookings on your WordPress site

Check which passenger-name, route, overnight-anchorage, boater-license-upload, damage-deposit, or hull-GPS fields you enable, who can open form entries and boat bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a weekend on the water ends — when the float plan names everyone aboard and where you'll anchor. Notification emails can also copy those fields off-site. One table can list every named passenger a renter typed next to a Saturday pontoon slot, a north-cove overnight route, a license PDF, a damage-deposit note, and a hull GPS trail. Ask your web vendor not to keep license uploads and GPS trails next to passenger and float-plan rows in one open submissions list longer than operations need, and to purge booking rows when a weekend ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored boat booking is not proof anyone left the dock. A passenger answer is not a Coast Guard file.

Page tags handled by a vendor

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

Float-plan-intake, boat-booking, 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 marina / boat-rental SaaS tools 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 Saturday pontoon slot or a weekend cabin-cruiser package is a booking you create; a service name such as boat rental or kayak day-use is a label you configure. Neither is a documented default. Passenger-name, route, overnight-anchorage, boater-license-upload, damage-deposit, or hull-GPS 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 left the dock — and a CSV export of a Saturday pontoon next to "Alex, Jordan, Sam", "north cove overnight", a license PDF filename, and a damage-deposit note is still a calendar that holds a passenger manifest and float plan 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.

Boat 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. Passenger-name, route, overnight-anchorage, boater-license-upload, damage-deposit, or hull-GPS fields are fields you add; they are not documented defaults. Completing the form can store a named passenger next to a boat booking, a contact name, a float-plan route, an overnight anchorage, optional license uploads, a damage-deposit note, and a GPS trail — typed once so the marina knows where to look if you do not come back, into the same tables as a kayak package name. A passenger answer is what a renter typed, not a Coast Guard file. A boat booking is a calendar row, not proof anyone left the dock — and a staff login can open "Alex + Jordan, north cove overnight, license.pdf, deposit held, Saturday pontoon" 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.

Passenger, route, and deposit answers stored in WordPress; optional boater-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 passenger-name, route, overnight-anchorage, boater-license, damage-deposit, or hull-GPS field was sent. A page request from this script is not proof anyone boarded. The page URL can say boat rental even when no form is submitted. Consent timing has not been tested. Review which tags you enable on reservation and float-plan 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. Passenger-name, route, overnight-anchorage, boater-license-upload, damage-deposit, or hull-GPS fields often depend on the fields you configure. A boat booking is a calendar row, not proof anyone left the dock. A passenger answer is what a renter typed, not a Coast Guard file. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone boarded. The page URL can say boat rental even when no form is submitted. The float plan that names everyone aboard and where you'll anchor — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that passenger-manifest and location-trail stack, not a scuba-shop medical questionnaire, a travel-agency passport scan, or a limo-service ground passenger list. Ask your web vendor who can open entries, whether a marketing tag loads on the reservation page, and how long records and backups are kept. A "boat rental privacy" or "marina 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 maritime law, boating-safety law, location-tracking law, or passenger-manifest law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on reservation and float-plan-intake 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-boat-rental-plugin-privacy