Campground plugin privacy
The site map that says which numbered pitch your kids sleep on tonight
A campground reservation ties a family to a numbered site on a public map for specific nights: names and ages of everyone in the party, the plate and rig description parked in plain view, arrival and departure dates — a precise answer to "where do your kids sleep tonight," held in a WordPress booking plugin. Seasonal-site holders are worse off: the same system becomes a registry of who owns a second address and exactly which weekends their house stands empty. Hospitality software with the data gravity of a residency record. Those fields are configured, not documented defaults. A campsite booking is a calendar row, not proof anyone pitched a tent. A party-name answer is what a guest typed, not a park census. An intake upload is a client document in a site uploads folder. A page request is not proof anyone checked in. The page URL can say campground even when no form is submitted. Ask what happens to the named party, site number, plate, rig, and stay dates after a weekend in the loop ends — the site map that says which numbered pitch your kids sleep on tonight outlives the checkout. 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 camping-law claim, a hospitality-law claim, a residency-law claim, an empty-home-law claim, a vehicle-registration-law 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 site-reservation intakes, campsite bookings, and page tags go
Intakes and bookings on your WordPress site
Check which party-name, age, numbered-site, plate, rig-description, seasonal-site, arrival, or departure fields you enable, who can open form entries and campsite bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a weekend in the loop ends — when the site map says which numbered pitch your kids sleep on tonight. Notification emails can also copy those fields off-site. One table can list every named guest a booker typed next to site 42, a Friday-to-Sunday stay, a plate number, and a fifth-wheel description. Seasonal-site rows can sit beside home-address fields that mark which weekends a second address stands empty. Ask your web vendor not to keep plate and rig answers next to party and site rows in one open submissions list longer than operations need, and to purge booking rows when a stay ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored campsite booking is not proof anyone pitched a tent. A party-name answer is not a park census.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the campground reservation or site-map intake page. That page request can reach a vendor host before anyone submits. The page URL can say campground even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off reservation and site-map intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "campground privacy" badge is not a verified storage path.
Site-reservation-intake, campsite-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 campground / RV-park 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-to-Sunday tent-site slot or a seasonal full-hookup package is a booking you create; a service name such as campground or RV park is a label you configure. Neither is a documented default. Party-name, age, numbered-site, plate, rig-description, seasonal-site, arrival, or departure 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 pitched a tent — and a CSV export of site 42 next to "Alex, Jordan (8), Sam (5)", a plate number, and a fifth-wheel note is still a calendar that holds a party roster and pitch assignment 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. | Campsite 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. Party-name, age, numbered-site, plate, rig-description, seasonal-site, arrival, or departure fields are fields you add; they are not documented defaults. Completing the form can store a named party next to a campsite booking, a contact name, a site number, stay dates, optional ID or waiver uploads, a plate number, and a rig description — typed once so the park knows which pitch the kids sleep on tonight, into the same tables as a tent-site package name. A party-name answer is what a guest typed, not a park census. A campsite booking is a calendar row, not proof anyone pitched a tent — and a staff login can open "Alex + kids, site 42, ABC-1234, fifth-wheel, Fri–Sun" 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. | Party, site, and plate answers stored in WordPress; optional ID or waiver 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 party-name, age, numbered-site, plate, rig-description, seasonal-site, arrival, or departure field was sent. A page request from this script is not proof anyone checked in. The page URL can say campground even when no form is submitted. Consent timing has not been tested. Review which tags you enable on reservation and site-map intake 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. Party-name, age, numbered-site, plate, rig-description, seasonal-site, arrival, or departure fields often depend on the fields you configure. A campsite booking is a calendar row, not proof anyone pitched a tent. A party-name answer is what a guest typed, not a park census. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone checked in. The page URL can say campground even when no form is submitted. The site map that says which numbered pitch your kids sleep on tonight — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that numbered-site and party-roster stack, not a boat-rental float plan, a limo-service passenger list, a summer-camp kids' enrollment file, or a pet-sitting empty-home schedule. 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 "campground privacy" or "RV-park 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 camping law, hospitality law, residency law, empty-home law, or vehicle-registration law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on reservation and site-map intake 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-campground-plugin-privacy