Petting zoo plugin privacy
The field-trip form that uploads an entire classroom in one click
A field-trip booking is the only form where one adult submits an entire classroom: twenty-five children's names, ages, and animal-allergy flags uploaded in a single roster by a teacher — children whose parents never saw the website, never ticked a consent box, and will never know the farm's form plugin holds their kid's medical flag next to their school's name and visit date. One submission, twenty-five data subjects, zero of them the person who clicked submit. Those fields are configured, not documented defaults. A field-trip booking is a calendar row, not proof anyone visited. An allergy flag is what a teacher typed or uploaded, not a medical finding. A page request is not proof anyone toured a barn. The page URL can say petting zoo even when no form is submitted. Ask what happens to the school reservation, the children's names, the ages, and the animal-allergy flags after the field trip ends — the classroom roster that one teacher uploaded outlives the last goat. 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 farm-liability-law claim, a COPPA assessment, a FERPA assessment, a school-district-policy claim, an allergy-claim assessment, 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 school-indexed classroom rosters, field-trip bookings, and page tags go
Intakes and bookings on your WordPress site
Check which school-name, child-name, age, animal-allergy, or classroom-roster fields you enable, who can open form entries and field-trip bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the visit ends — when the classroom roster that one teacher uploaded still holds that row. Notification emails can also copy those fields off-site. One table can list a school reservation next to twenty-five legal names, ages, and animal-allergy flags. Ask your web vendor not to keep school-indexed children's allergy flags next to classmate rosters in one open submissions list longer than operations need, and to purge those fields when a field-trip booking closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored field-trip booking is not proof anyone visited. An allergy flag is not a medical finding.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the petting-zoo field-trip booking page. That page request can reach a vendor host before anyone submits. The page URL can say petting zoo even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "petting zoo privacy" badge is not a verified storage path.
Field-trip roster, booking, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty farm / agritourism SaaS tools without a WordPress.org listing are outside this sample.
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
| 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 school field-trip block or a barn visit window is a booking you create; a service name such as petting zoo or field trip is a label you configure. Neither is a documented default. School-name, child-name, age, animal-allergy, or classroom-roster 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 visited — and a CSV export of "Lincoln Elementary class trip, Maya Chen, age 8, peanut/hay allergy" next to a teacher contact is still a calendar that holds twenty-five children's allergy flags under one school reservation. 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. | Field-trip and farm 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. School-name, child-name, age, animal-allergy, or classroom-roster fields are fields you add; they are not documented defaults. Completing the form can store a child legal name next to an animal-allergy flag, an age, a school reservation label, a teacher contact, and optional roster uploads — typed once by a teacher so the farm does not have to re-key twenty-five kids, into the same tables as a petting-zoo label. An allergy flag is what a teacher typed or uploaded, not a medical finding. A field-trip booking is a calendar row, not proof anyone visited — and a staff login can open "Lincoln Elementary — Maya Chen, age 8, peanut/hay allergy" next to everyone else's classmates. 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. | Classroom-roster and animal-allergy 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 school-name, child-name, age, animal-allergy, or classroom-roster field was sent. A page request from this script is not proof anyone toured a barn. The page URL can say petting zoo even when no form is submitted. Consent timing has not been tested. Review which tags you enable on field-trip booking 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. School-name, child-name, age, animal-allergy, or classroom-roster fields often depend on the fields you configure. A field-trip booking is a calendar row, not proof anyone visited. An allergy flag is what a teacher typed or uploaded, not a medical finding. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone toured a barn. The page URL can say petting zoo even when no form is submitted. The classroom roster that one teacher uploaded — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that school-indexed field-trip roster, not a summer-camp medical card, a laser-tag party roster, a youth-sports season roster, a homeschool-coop education group, or a school-carpool map. 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 "petting zoo privacy" or "field-trip-safe" 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 farm liability law, COPPA, FERPA, school-district policy, or allergy claims. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking 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-petting-zoo-plugin-privacy