Skydiving plugin privacy
The manifest that weighs you, films you, and keeps the waiver forever
A dropzone's booking manifest is built from the three things tandem physics and liability demand: your exact weight (rig limits), a health attestation (heart, blindness, recent dives/flights), and a next-of-kin contact — the form literally asks who to call if you die. Add the souvenir jump video tied to your name and the lifetime-retained waiver, and a weekend thrill leaves a permanent record: weight, health claims, emergency kin, and footage, all in a WordPress booking plugin at a grass airstrip. Those fields are configured, not documented defaults. A tandem booking is a calendar row, not proof anyone jumped. A weight answer is what a jumper typed, not a clinic chart. An intake upload is a client document in a site uploads folder. A page request is not proof anyone left the ground. The page URL can say skydiving even when no form is submitted. Ask what happens to the named weight, health, next-of-kin, and jump-video rows after a jump weekend ends — the manifest that weighs you, films you, and keeps the waiver forever outlives the freefall. 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, an FAA/USPA-rules claim, a tandem-liability-law claim, a medical-privacy-law claim, a dropzone-compliance 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 manifest intakes, tandem bookings, and page tags go
Intakes and bookings on your WordPress site
Check which weight, health-attestation, next-of-kin, waiver-upload, or jump-video fields you enable, who can open form entries and tandem bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a jump weekend ends — when the manifest weighs you, films you, and keeps the waiver forever. Notification emails can also copy those fields off-site. One table can list every named weight a jumper typed next to a Saturday tandem slot, a health claim, Mom's emergency phone, and a waiver PDF. Ask your web vendor not to keep waiver uploads and jump videos next to weight and next-of-kin 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 tandem booking is not proof anyone jumped. A weight answer is not a clinic chart.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the skydiving reservation or manifest-intake page. That page request can reach a vendor host before anyone submits. The page URL can say skydiving even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off reservation and manifest-intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "skydiving privacy" badge is not a verified storage path.
Manifest-intake, tandem-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 dropzone 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 Saturday tandem slot or a weekend jump package is a booking you create; a service name such as skydiving or tandem manifest is a label you configure. Neither is a documented default. Weight, health-attestation, next-of-kin, waiver-upload, or jump-video 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 jumped — and a CSV export of a Saturday 9am tandem slot next to 185 lb, a heart/eye attestation, Mom's emergency phone, and a waiver PDF filename is still a calendar that holds a liability manifest 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. | Tandem 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. Weight, health-attestation, next-of-kin, waiver-upload, or jump-video fields are fields you add; they are not documented defaults. Completing the form can store a named weight next to a tandem booking, a contact name, a health claim, an emergency-kin phone, optional waiver uploads, and a souvenir jump video — typed once so the dropzone can set rig limits and know who to call, into the same tables as a package name. A weight answer is what a jumper typed, not a clinic chart. A tandem booking is a calendar row, not proof anyone jumped — and a staff login can open "Alex, 185 lb, no recent heart issues, call Mom at …, waiver.pdf, jump.mp4, Saturday tandem" 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. | Weight, health, and next-of-kin answers stored in WordPress; optional waiver and jump-video 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 weight, health-attestation, next-of-kin, waiver, or jump-video field was sent. A page request from this script is not proof anyone left the ground. The page URL can say skydiving even when no form is submitted. Consent timing has not been tested. Review which tags you enable on reservation and manifest-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. Weight, health-attestation, next-of-kin, waiver-upload, or jump-video fields often depend on the fields you configure. A tandem booking is a calendar row, not proof anyone jumped. A weight answer is what a jumper typed, not a clinic chart. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone left the ground. The page URL can say skydiving even when no form is submitted. The manifest that weighs you, films you, and keeps the waiver forever — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that dropzone liability manifest, not a ski-rental equipment-weight form, a race-registration waiver, or a trampoline-park kiosk waiver. 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 "skydiving privacy" or "USPA 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 FAA/USPA rules, tandem liability law, or medical privacy law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on reservation and manifest-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-skydiving-plugin-privacy