Dance School Software · Enrollment, recital operations, consent-gated media
Privacy
The Consent & Release Ledger — machine-readable consent at the engine layer
Consent is not a folder. It is the data that drives every downstream operation.
Dance School Software does not store consent as a PDF attachment. The Consent & Release Ledger is a machine-readable record: each permission type (photo/video depiction, social media, authorised pickup, costume vendor data sharing, communications opt-in) is a separate, timestamped, scoped record per student. The platform enforces each record at the engine layer: a student without photo consent does not appear in the proofing gallery, not because a staff member checks a list, but because the system refuses to place them there.
A guardian can revoke any consent at any time. The revocation takes effect immediately: existing proofing gallery entries featuring that performer are suppressed; any queued gallery access is revoked. The revocation is recorded with a timestamp in the audit trail. A director can produce a full consent-history export for any student for any date range — timestamped records of every permission given, declined, or revoked — in a format that holds up in a licensing inspection or a guardian inquiry.
Student and family data is owned by the studio and is never sold to or shared with outside companies. No student image is ever placed in a public or searchable gallery. Share links for private galleries are time-limited and guardian-scoped: a link generated for one family does not grant access to another family’s child’s images. One-click export is available in writing as part of the onboarding agreement: if a studio ever leaves, every record leaves with it.
What is built and what is coming — plainly
The consent and roster engines are built. The storefront checkout and charge rail are not live yet.
Built and production-ready today: enrollment and roster engine; Consent & Release Ledger (explicit, timestamped, scoped, revocable, audit-exportable); class scheduling, session management, and family portal; recital lineup builder (roster-tied, propagates on roster changes); backstage performer check-in; media proofing substrate (consent-flag suppression at the data layer, gallery organisation by class and act); print and digital fulfillment infrastructure; and the no-skim payout engine (fee-off-gross-first, exact-cent, largest-remainder reconciliation).
Not yet enabled for live use: the payment rail (the part that moves money), the parent-facing ordering storefront checkout, autopay tuition plan enrollment, costume and measurement tracking boards, performer-conflict detection, and SMS/text carrier delivery for parent communications. These are honest-off — present in the platform, not enabled for live use. There is no live checkout here. No billing. No subscription. We say this directly because a studio owner deciding between platforms deserves the full picture.