Marina plugin privacy
The slip ledger that knows which weekends your house is empty
A marina slip agreement is a second mortgage's worth of identity in one form: boat registration, insurance policy, home address, emergency contacts, gate code. Then the moorage ledger starts keeping time — which weekends the boat leaves, when it winters out, which slips are liveaboards whose entire residence status sits in a billing row. A boat is the one asset whose location log doubles as its owner's. Those fields are configured, not documented defaults. A moorage booking is a calendar row, not proof anyone left home or that a boat moved. A registration or schedule answer is a form answer or uploaded file, not a verified vacancy. A page request is not proof anyone holds a slip. The page URL can say marina even when no form is submitted. Ask what happens to the registration, the home address, the gate code, the emergency contacts, and the departure/return log after a season ends — the stack that dated which weekends the house stood empty outlives the slip. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the slip or moorage page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a maritime-law claim, an insurance-underwriting claim, a liveaboard-residency-rules claim, a premises-security-advice 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 slip agreements, moorage bookings, and page tags go
Agreements and bookings on your WordPress site
Check which slip, registration, insurance, home-address, emergency-contact, gate-code, departure/return, or intake-upload fields you enable, who can open form entries and moorage bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a season ends — when the slip-plus-registration-plus-home-plus-schedule row still holds which weekends the house stood empty. Notification emails can also copy those fields off-site. One table can list every "slip B-14 · reg FL-4421-AB · insurance ACME · home 12 Oak St · emerg: Pat 555-0199 · gate 4412 · left Fri 6pm / back Sun 4pm" stack next to a customer name. Ask your web vendor not to keep gate codes and departure logs next to home addresses and registrations in one open submissions list longer than operations need, and to purge those fields when a season closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored moorage booking is not proof anyone left home or that a boat moved. A registration or schedule answer is not a verified vacancy.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the slip or moorage page. That page request can reach a vendor host before anyone submits. The page URL can say marina even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off slip and moorage pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "marina privacy" badge is not a verified storage path.
Marina slip agreement, moorage 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 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 Friday haul-out window or a winter-storage slot is a booking you create; a service name such as slip renewal or liveaboard check-in is a label you configure. Neither is a documented default. Slip, registration, insurance, home-address, emergency-contact, gate-code, or departure/return 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 home or that a boat moved — and a CSV export of "slip B-14 · reg FL-4421-AB · insurance ACME · home 12 Oak St · emerg: Pat 555-0199 · gate 4412 · left Fri 6pm / back Sun 4pm" next to a customer name is still a calendar that pairs a boat location log with a home address. 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. | Marina moorage 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. Slip, registration, insurance, home-address, emergency-contact, gate-code, or departure/return fields are fields you add; they are not documented defaults. Completing the form can store a slip-plus-registration-plus-home-plus-schedule stack ("slip B-14 · reg FL-4421-AB · insurance ACME · home 12 Oak St · emerg: Pat 555-0199 · gate 4412 · left Fri 6pm / back Sun 4pm") — typed once so a marina can bill and open the gate, into the same tables as a "marina" label. A registration or schedule answer is a form answer or uploaded file, not a verified vacancy. A moorage booking is a calendar row, not proof anyone left home — and a staff login can open "Jordan, slip B-14, FL-4421-AB, 12 Oak St, left Fri 6pm" 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. | Slip, registration, home-address, and schedule answers stored in WordPress; optional 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 slip, registration, home-address, or schedule field was sent. A page request from this script is not proof anyone holds a slip. The page URL can say marina even when no form is submitted. Consent timing has not been tested. Review which tags you enable on slip and moorage 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. Slip, registration, insurance, home-address, emergency-contact, gate-code, or departure/return fields often depend on the fields you configure. A moorage booking is a calendar row, not proof anyone left home or that a boat moved. A registration or schedule answer is a form answer or uploaded file, not a verified vacancy. A marketing-tag page request is not proof anyone holds a slip. The page URL can say marina even when no form is submitted. The slip-plus-registration-plus-home-plus-schedule row that dated which weekends the house stood empty — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that moorage location log, not a boat-rental day float plan, a self-storage unit custody file, or a snow-removal two-address empty-house contract. Ask your web vendor who can open entries, whether a marketing tag loads on the slip or moorage page, and how long records and backups are kept. A "marina privacy" or "moorage 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, insurance underwriting, liveaboard residency rules, or premises security advice. Review stored records, bookings, connected services, exports, notification emails, marketing tags on slip and moorage 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-marina-plugin-privacy