Martial arts plugin privacy

The enrollment that records why your kid needs fixing, in the parent's words

A martial-arts studio's site can look like a calendar and a short enrollment form. The same form often asks for a child's name and age, school and grade, why you are enrolling, prior injuries or conditions, an emergency contact, and a photo-release checkbox — and asks for a belt-test photo — and stores those answers next to the parent's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a trial-class booking next to a reason-for-enrolling sentence, a school-and-grade field, a prior-injuries note, a photo-release checkbox beside the belt-test photo it governs, and a marketing pixel — the enrollment that records why your kid needs fixing, in the parent's words, typed once into a vendor table next to a newsletter signup. A trial-class booking is a calendar row, not an enrollment. A reason-for-enrolling answer is the parent's words, not an assessment of the child. A prior-injuries answer is a waiver disclosure, not a medical chart. A photo-release checkbox is a stored preference, not a mechanism that deletes or retrieves anything. A child named in the form never touched it. A page request is not proof any child trains anywhere. The page URL can say martial-arts even when no form is submitted. Ask what happens to the belt-test photos and reason rows after the Tuesday class is scheduled — the quietest pairing is the reason sitting next to school and grade. 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 self-defense or anti-bullying-outcomes claim, a child-safeguarding claim, an instructor-certification claim, a COPPA or child-privacy-law claim, a claim about the studio's data-security practices, a provider-quality 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 trial-class bookings, enrollment reasons, and page tags go

Bookings and notes on your WordPress site

Check which child-name-and-age, school-and-grade, reason-for-enrolling, prior-injuries-or-conditions, emergency-contact, or photo-release fields you enable, who can open form entries and trial-class, belt-test, or private-lesson bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a Tuesday class is scheduled — when the enrollment that records why your kid needs fixing, in the parent's words. Notification emails can also copy those fields off-site. One table can list every trial next to a belt-test photo and a reason-for-enrolling sentence. Ask your web vendor not to keep belt-test-photo uploads next to plaintext reason and school-and-grade rows in one open submissions list longer than operations need, and to purge intake rows when the class is no longer active. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not an enrollment. A reason-for-enrolling sentence in a form table is not an assessment the plugin claims to make.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the martial-arts trial-class or enrollment-intake page. That page request can reach a vendor host before anyone submits. The page URL can say martial-arts even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off trial-class, belt-test, private-lesson, and martial-arts enrollment-intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "trusted dojo partner" badge is not a verified storage path.

Trial-class / belt-test / private-lesson booking, martial-arts enrollment 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 dojo-management 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 Tuesday trial class, a belt-test slot, or a private-lesson booking is a booking you create; a service name such as trial class, belt test, or private lesson is a label you configure. Neither is a documented default. Child-name-and-age, school-and-grade, reason-for-enrolling, prior-injuries-or-conditions, emergency-contact, or photo-release questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not an enrollment — and a CSV export of a trial-class row next to a child name and a reason-for-enrolling note is still a calendar that holds a parent's one-sentence diagnosis 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.

Trial-class, belt-test, and private-lesson 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. Child-name-and-age, school-and-grade, reason-for-enrolling, prior-injuries-or-conditions, emergency-contact, or photo-release fields are fields you add; they are not documented defaults. Completing the form can store a reason-for-enrolling sentence next to a child name and age, a school and grade, a prior-injuries note, a photo-release checkbox, an emergency contact, and optional belt-test-photo uploads — typed once as the enrollment that records why your kid needs fixing, in the parent's words, into the same tables as a newsletter signup. A reason-for-enrolling answer is the parent's words, not an assessment of the child. A prior-injuries answer is a waiver disclosure, not a medical chart. A photo-release checkbox is a stored preference, not a mechanism that deletes or retrieves anything — and a staff login can open "Jordan, age 11, Lincoln Middle 6th, being bullied at school, prior ankle sprain, photo release yes, mom cell, belt-test.jpg" next to everyone else's resume. A child named in the form never touched it. 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.

Martial-arts enrollment intake stored in WordPress; optional belt-test-photo 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 child-name-and-age, school-and-grade, reason-for-enrolling, prior-injuries-or-conditions, emergency-contact, or photo-release field was sent. A page request from this script is not proof any child trains anywhere. The page URL can say martial-arts even when no form is submitted. Consent timing has not been tested. Review which tags you enable on trial-class, belt-test, private-lesson, and martial-arts enrollment-intake 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. Child-name-and-age, school-and-grade, reason-for-enrolling, prior-injuries-or-conditions, emergency-contact, or photo-release fields often depend on the fields you configure. A trial-class booking is a calendar row, not an enrollment. A reason-for-enrolling answer is the parent's words, not an assessment of the child. A prior-injuries answer is a waiver disclosure, not a medical chart. A photo-release checkbox is a stored preference, not a mechanism that deletes or retrieves anything. A child named in the form never touched it. A marketing-tag page request is not proof any child trains anywhere. The page URL can say martial-arts even when no form is submitted. The enrollment that records why your kid needs fixing, in the parent's words — that is a storage path next to a belt-test photo, not a feature these plugins claim. This page is about that martial-arts enrollment intake, not a dance-studio costume measurement, a youth-sports-league roster, an anger-management intake, or an ADHD-testing parent note. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long reason rows and backups are kept after the Tuesday class is scheduled. A "trusted dojo partner" 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 self-defense or anti-bullying outcomes, child-safeguarding standards, instructor certification, COPPA or child-privacy law, the studio's data-security practices, or provider quality. 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-martial-arts-plugin-privacy