Dance studio plugin privacy

The measurement chart of a child's body, kept with the costume order

A dance studio's site can look like a calendar and a short costume form. The same form often asks for a child's name and age, class level, bust, waist, hips, and girth, medical conditions, a photo-release checkbox, and an emergency contact — and asks for a recital headshot — 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 season's measurements, a medical-conditions note, a photo-release checkbox beside the headshot it governs, and a marketing pixel — the measurement chart of a child's body, kept with the costume order, typed once into a vendor table next to a newsletter signup. A trial-class booking is a calendar row, not an enrollment. A measurement set is what a parent taped and typed, not a fitting record. A medical-conditions answer is the parent's note, not a 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 dances. The page URL can say dance-studio even when no form is submitted. Ask what happens to the headshots and measurement rows after the costume order closes — the quietest field is the photo-release checkbox, consent to publish a child's face stored in the same row as the image it governs. 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 COPPA or child-privacy-law claim, a child-safeguarding claim, a studio or instruction-quality claim, a costume-vendor-practices 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, costume measurements, and page tags go

Bookings and notes on your WordPress site

Check which child-name-and-age, class-level, costume-measurements, medical-conditions, photo-release, or emergency-contact fields you enable, who can open form entries and trial-class or private-lesson bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a costume order closes — when the measurement chart of a child's body, kept with the costume order. Notification emails can also copy those fields off-site. One table can list every Saturday trial next to a recital headshot and a medical-conditions note. Ask your web vendor not to keep recital-headshot uploads next to plaintext measurement and photo-release rows in one open submissions list longer than operations need, and to purge intake rows when the costume order closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not an enrollment. A measurement set in a form table is not a growth chart the plugin claims to build.

Page tags handled by a vendor

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

Trial-class / private-lesson booking, dance-studio costume 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 studio-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 Saturday trial class or a private-lesson slot is a booking you create; a service name such as trial class or private lesson is a label you configure. Neither is a documented default. Child-name-and-age, class-level, costume-measurements, medical-conditions, photo-release, 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 an enrollment — and a CSV export of a trial-class row next to a child name and a measurement note is still a calendar that holds a body chart 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 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, class-level, costume-measurements, medical-conditions, photo-release, or emergency-contact fields are fields you add; they are not documented defaults. Completing the form can store bust, waist, hips, and girth next to a child name and age, a class level, a medical-conditions note, a photo-release checkbox, an emergency contact, and optional recital-headshot uploads — typed once as the measurement chart of a child's body, kept with the costume order, into the same tables as a newsletter signup. A measurement set is what a parent taped and typed, not a fitting record. A medical-conditions answer is the parent's note, not a chart. A photo-release checkbox is a stored preference, not a mechanism that deletes or retrieves anything — and a staff login can open "Maya, age 8, Level 2, bust 24 waist 22 hips 26 girth 38, asthma stage left, photo release yes, dad cell, recital headshot.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.

Dance-studio costume intake stored in WordPress; optional recital-headshot 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, class-level, costume-measurements, medical-conditions, photo-release, or emergency-contact field was sent. A page request from this script is not proof any child dances. The page URL can say dance-studio even when no form is submitted. Consent timing has not been tested. Review which tags you enable on trial-class, private-lesson, and dance-studio costume-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, class-level, costume-measurements, medical-conditions, photo-release, or emergency-contact fields often depend on the fields you configure. A trial-class booking is a calendar row, not an enrollment. A measurement set is what a parent taped and typed, not a fitting record. A medical-conditions answer is the parent's note, not a 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 dances. The page URL can say dance-studio even when no form is submitted. The measurement chart of a child's body, kept with the costume order — that is a storage path next to a recital headshot, not a feature these plugins claim. This page is about that dance-studio costume intake, not a youth-sports-league roster, a tutoring lesson book, a summer-camp enrollment, or an orthodontist child image. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long measurement rows and backups are kept after the costume order closes. A "trusted dance 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 COPPA or child-privacy law, child-safeguarding standards, studio or instruction quality, costume-vendor practices, 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-dance-studio-plugin-privacy