Rock climbing plugin privacy
The belay card that stores your heart condition next to your emergency contact
Before a climbing gym lets you touch the wall, the intake asks the questions your doctor asks — heart condition, pregnancy, medications, prior injuries — because someone will be hanging from a rope you hold. The belay certification then becomes a standing permission record: who is allowed to keep whom alive, stored with an emergency contact the gym hopes it never dials. It's health data collected by a gym membership plugin, with none of the handling rules a clinic would be forced to follow. Those fields are configured, not documented defaults. A wall or class booking is a calendar row, not proof anyone climbed. A heart-condition answer is what a guest typed, not a diagnosis. A belay-cert flag is a staff permission bit, not a federation credential. An intake upload is a client document in a site uploads folder. A page request is not proof anyone clipped in. The page URL can say rock climbing even when no form is submitted. Ask what happens to the heart-condition answer, pregnancy flag, medication list, prior-injury note, belay-cert bit, and emergency contact after the session ends — the belay card that stores your heart condition next to your emergency contact outlives the climb. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the check-in page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a HIPAA claim, medical advice, a belay-certification-standard claim, a climbing-gym-liability-law claim, a fitness-clearance 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 health answers, wall bookings, and page tags go
Intakes and bookings on your WordPress site
Check which heart-condition, pregnancy, medication, prior-injury, belay-cert, or emergency-contact fields you enable, who can open form entries and wall bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the session ends — when the belay card that stores your heart condition next to your emergency contact still holds that row. Notification emails can also copy those fields off-site. One table can list a legal name next to a heart-condition yes, a medication list, a belay-cert permission bit, and an emergency contact. Ask your web vendor not to keep clinic-grade answers next to belay permissions and emergency contacts in one open submissions list longer than operations need, and to purge those fields when a membership closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored wall booking is not proof anyone climbed. A heart-condition answer is not a diagnosis.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the rock-climbing check-in or booking page. That page request can reach a vendor host before anyone submits. The page URL can say rock climbing even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off check-in and booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "rock climbing privacy" badge is not a verified storage path.
Health-intake, booking, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty climbing-gym / belay 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 Saturday wall slot or a belay-class block is a booking you create; a service name such as rock climbing or intro belay is a label you configure. Neither is a documented default. Heart-condition, pregnancy, medication, prior-injury, belay-cert, or emergency-contact 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 climbed — and a CSV export of "Sam Rivera, heart condition: yes, meds: beta blocker, belay certified, ICE: Morgan Rivera" next to a contact name is still a calendar that holds clinic-grade answers next to a rope permission. 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. | Wall and class 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. Heart-condition, pregnancy, medication, prior-injury, belay-cert, or emergency-contact fields are fields you add; they are not documented defaults. Completing the form can store a heart-condition yes next to a pregnancy flag, a medication list, a prior-injury note, a belay-cert permission bit, an emergency contact the gym hopes it never dials, a contact name, and optional waiver or medical-card uploads — typed once so the front desk does not have to re-key the check-in, into the same tables as a rock-climbing-session label. A heart-condition answer is what a guest typed, not a diagnosis. A wall booking is a calendar row, not proof anyone climbed — and a staff login can open "Sam Rivera, heart condition: yes, pregnant: no, meds: beta blocker, prior shoulder injury, belay certified, ICE: Morgan Rivera, waiver PDF" 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. | Heart-condition and emergency-contact answers stored in WordPress; optional waiver or medical-card 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 heart-condition, pregnancy, medication, prior-injury, belay-cert, or emergency-contact field was sent. A page request from this script is not proof anyone clipped in. The page URL can say rock climbing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on check-in and 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. Heart-condition, pregnancy, medication, prior-injury, belay-cert, or emergency-contact fields often depend on the fields you configure. A wall or class booking is a calendar row, not proof anyone climbed. A heart-condition answer is what a guest typed, not a diagnosis. A belay-cert flag is a staff permission bit, not a federation credential. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone clipped in. The page URL can say rock climbing even when no form is submitted. The belay card that stores your heart condition next to your emergency contact — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that climbing-gym health-intake and belay-permission stack, not a personal-trainer PAR-Q, a martial-arts enrollment fitness history, a summer-camp minor medical card, or a swim-school drowning-risk lesson intake. Ask your web vendor who can open entries, whether a marketing tag loads on the check-in page, and how long records and backups are kept. A "rock climbing privacy" or "gym-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 HIPAA, medical advice, belay-certification standards, climbing-gym liability law, or fitness-clearance rules. Review stored records, bookings, connected services, exports, notification emails, marketing tags on check-in and 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-rock-climbing-plugin-privacy