Personal trainer plugin privacy

The PAR-Q that files your heart condition next to your phone number

A personal trainer's intake page can look like a session booking and a contact form. The same form often asks name and phone, a Physical Activity Readiness Questionnaire (PAR-Q) with seven yes/no medical questions — including whether a doctor has ever said you have a heart condition — plus injury history, emergency contact, weigh-in or measurement logs, and session notes, and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. Before the first squat, the PAR-Q asks the load-bearing cardiac questions at signup. The injury-history box is a body's biography in the client's own words: "left knee reconstruction 2019, still avoids deep lunges." Weigh-in and measurement logs are a dated time series of private progress (or relapse). The emergency contact is the person to call when it goes wrong, named on day one. Session notes record, by date, what the body couldn't do. A session booking is a calendar row, not proof a client is cleared to train. A PAR-Q yes answer is the client's disclosure, not a diagnosis. An injury-history story is the client's account, not a chart. A weigh-in log is a dated measurement entry, not a verified outcome. A session note is a staff note, not a medical record. A page request is not proof anyone trains anywhere. The page URL can say personal trainer even when no form is submitted. Ask what happens to the PAR-Q answer and the weigh-in log after the package ends — the PAR-Q that files your heart condition next to your phone number outlives the first session. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a training-outcome or fitness-certification claim, a medical-advice or HIPAA claim, or a GDPR or other compliance assessment.

Scan your site for third-party requests

The 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 session bookings, PAR-Q intakes, and page tags go

Intakes and bookings on your WordPress site

Check which PAR-Q, injury-history, emergency-contact, weigh-in, or session-note fields you enable, who can open form entries and session bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a booking closes — when the PAR-Q files a heart condition next to a phone number. Notification emails can also copy those fields off-site. One table can list every cardiac yes answer a client typed next to a session slot and a weigh-in log. Ask your web vendor not to keep weigh-in logs next to PAR-Q answers in one open submissions list longer than operations need, and to purge booking rows when the intake is declined or closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored session booking is not proof a client is cleared to train. A weigh-in log is not a verified outcome.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the personal-trainer intake page. That page request can reach a vendor host before anyone submits. The page URL can say personal trainer even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off intake and session-booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "cleared to train" badge is not a verified storage path.

Session booking, PAR-Q intake, 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 personal-trainer CRM SaaS platforms without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 consult or recurring training-session booking is a booking you create; a service name such as intake consult, personal training, or online coaching is a label you configure. Neither is a documented default. PAR-Q, injury-history, emergency-contact, weigh-in, or session-note questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof a client is cleared to train — and a CSV export of session slots next to a PAR-Q yes answer and a named client is still a booking row after someone asked about a first session. 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.

Training-session and consult bookings stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
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. PAR-Q yes/no questions, injury-history, emergency-contact, weigh-in, or session-note fields are fields you add; they are not documented defaults. Completing the form can store a heart-condition yes next to an injury narrative, a phone number, a weigh-in log, and optional uploads — typed once by a client into the same tables as a newsletter signup. A session booking is a calendar row, not proof a client is cleared to train. A PAR-Q yes answer is the client's disclosure, not a diagnosis. An injury-history story is the client's account, not a chart. A weigh-in log is a dated measurement entry, not a verified outcome. A session note is a staff note, not a medical record. An uploaded file is a client document in uploads/forminator. A staff login can open the heart-condition answer next to the Tuesday 6am session slot. 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.

PAR-Q and injury-intake entries stored in WordPress; optional uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 PAR-Q, injury-history, emergency-contact, weigh-in, or session-note field was sent. A page request from this script is not proof anyone trains anywhere. The page URL can say personal trainer even when no form is submitted. Consent timing has not been tested. Review which tags you enable on intake and session-booking pages.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. PAR-Q, injury-history, emergency-contact, weigh-in, or session-note fields often depend on the fields you configure. A session booking is a calendar row, not proof a client is cleared to train. A PAR-Q yes answer is the client's disclosure, not a diagnosis. An injury-history story is the client's account, not a chart. A weigh-in log is a dated measurement entry, not a verified outcome. A session note is a staff note, not a medical record. A marketing-tag page request is not proof anyone trains anywhere. The page URL can say personal trainer even when no form is submitted. The PAR-Q that files your heart condition next to your phone number — that is a storage path next to names and phones, not a feature these plugins claim. This page is about that one-on-one trainer intake, not a gym membership BMI dashboard, a weight-loss program weigh-in, a physical-therapy clinical rehab form, or a chiropractic clinic intake. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long records and backups are kept. A "cleared to train" 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 training outcomes, fitness certification, medical advice, or HIPAA. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake pages, and backups.

Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-personal-trainer-plugin-privacy