Fishing charter plugin privacy
The manifest that posts who is miles offshore until 6pm
A fishing-charter WordPress stack is not only a trip calendar — it is often an away-from-home certificate. Every confirmed booking can name the whole party, their addresses, and the exact window nobody is reachable offshore, with medical-waiver answers and emergency contacts on the same row. Catch-photo uploads kept for marketing can add faces to that schedule. A page request is not proof anyone booked. A trip window is a stored calendar slot, not proof anyone left shore. A catch photo is a stored file, not a GPS fix. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where catch photos land, which inboxes receive copies, and how long past manifests, files, and backups are kept.
Documentation review only. This is not legal advice, a maritime-safety claim, a medical claim, a burglary-risk claim, a catch claim, a GDPR or other compliance assessment, or a judgment about captains.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, bookings, uploaded photos, email inboxes, staff permissions, vendor accounts, or backups.
Where charter manifests, waivers, and catch photos go
Entries, bookings, and uploads on your WordPress site
Check which party-name, address, trip-window, medical-waiver, or emergency-contact fields you enable, who can open form entries and charter bookings, where uploaded catch photos live in the uploads folder, which inboxes receive copies, and how long past manifests, files, and backups are kept after a trip that never left the dock. Notification emails can also copy the same party roster and photo links off-site.
Uploads or connected destinations off your WordPress site
Some upload tools can send files to FTP, SFTP, or cloud destinations you enable. Review which destinations you turn on, account access, and retention there. A browser scan cannot inspect stored form entries, bookings, or who opened the trip calendar. A "private charter roster" badge is not a verified storage path.
Fishing-charter booking, waiver intake, and catch-photo 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 charter SaaS platforms 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 frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. A catch photo is a file you accept; that file type is not a documented default. An uploaded photo is a stored file, not proof of a catch or a GPS fix. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. | Catch-photo uploads stored under the site wp-content path | 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. Reason-for-appraisal, rush-order, access-instructions, lockbox-code, owner-at-work, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional interior-photo or document uploads are files you accept; those file types are not documented defaults. A reason-for-appraisal answer is a stored select, not proof a divorce was filed. A rush order is a stored priority label, not proof a crisis happened. An interior-photo upload is a stored file, not a valuation. Access instructions are stored text, not proof anyone entered the home. A fishing-charter form is not proof anyone completed an appraisal. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a pairing sits after an appraisal that never happened is not a documented default of the plugin. | Appraisal intake and reason-for-appraisal entries stored in WordPress; optional uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| Iptanus File Upload Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. An interior photo, floor plan, or prior appraisal PDF is a file you accept; that file type is not a documented default. An uploaded interior photo is a stored file, not a valuation. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. How long an interior-photo file sits after an appraisal that never happened is not a documented default of the plugin. | Interior-photo and document uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Party-names, addresses, trip-windows, medical-waiver fields, emergency contacts, or catch-photo uploads often depend on the fields you configure. A trip window is a stored calendar slot, not proof anyone left shore. A medical-waiver answer is a stored note, not a diagnosis. A catch photo is a stored file, not proof of a catch or a GPS fix. A fishing-charter booking is not proof anyone boarded. A page request is not proof anyone booked. The page URL can say fishing charter even when no form is submitted. Ask your web vendor who can open entries and uploads, whether catch photos remain reachable by direct URL, and how long records and backups are kept. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess maritime safety, medical advice, or burglary risk. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 20, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress gallery plugin privacy
- All privacy guides
/wp-fishing-charter-plugin-privacy