Privacy

Plain-English privacy policy.

What we collect, why we collect it, and what we do with it. Written for the people who actually have to read it.

Last updated: June 1, 2026

The short version

We collect the information a studio needs to run, a parent needs to keep up, and a dancer needs to track their record. We do not sell it. We do not use it for advertising. We share it only with the services we need to run StageSide (Stripe for payments, hosting providers, email). Dancers and Primary Caregivers control whether the studio can hand off, change, or remove their record.

Who this applies to

This policy covers everyone who uses StageSide: studio owners, studio staff, teachers, teaching assistants, parents and other caregivers, dancers, alumni, and the people who follow comp day on a share link.

What we collect

Account information

When you sign up, we collect your name, email, and the role you hold (owner, teacher, parent, dancer, and so on). Studios additionally provide the studio name, address, and contact information.

Dancer profiles

For each dancer, the studio enters basic information needed to run classes and competitions: name, date of birth, allergies, pronouns, photo-release preference, caregiver links. Parents and dancers can review and request changes to this information at any time. The studio and the dancer share ownership of the record.

Payment information

Tuition, costume, and competition payments run through Stripe. We do not store your full card number or banking details on StageSide servers. Stripe handles that under their own published security standards.

Messaging

Direct messages, group threads, and studio announcements are stored in StageSide so studios meet their record-keeping obligations and parents have a complete history. Messages between adults and minors are subject to additional safety rules: every thread with a minor must include at least three people, and one-to-one private messages between an adult and an unrelated minor are not allowed at the data layer, not just in the app.

Schedule and attendance

We store class enrollments, attendance status, comp-day schedules, running-order changes, and adjudication results. This is the dancer's permanent record.

Device and usage data

We collect basic technical information needed to keep StageSide working: device type, app version, error logs, push-notification tokens. We use this to diagnose problems and improve the app. We do not use it for advertising.

How we use this information

To operate StageSide: schedule classes, run comp day, process payments, send messages and notifications, generate reports for studio owners, and keep the dancer's record. To communicate with you: account notifications, billing receipts, product updates, and replies to support requests. To improve StageSide: diagnose errors, prioritize the next feature, and measure whether changes help.

What we do not do

We do not sell personal information. We do not rent it. We do not use it for advertising. We do not share it with third parties for their own marketing. We do not use it to train models for unrelated purposes.

Who we share information with

The studio, parents, dancers, and others on your StageSide account see only what their role permits. Beyond your account, we share information with a small set of service providers we use to operate StageSide: Stripe for payments, our hosting and database providers, our email delivery provider, and the App Store and Play Store for app distribution. Each is bound by its own privacy and security commitments. We will share information when required by a court order, subpoena, or other legal process, and we will tell you when we do unless the law forbids it.

Children and minors

StageSide is used by families. Many dancers are under 13. Parents and legal guardians control the account and the dancer's profile. We follow the spirit of the Children's Online Privacy Protection Act and similar laws around the world. If you believe a child's information is in our system without proper consent, contact us at the address below and we will resolve it quickly.

Your rights and choices

You can review and update most information directly in the app. For records that are part of the dancer's permanent history (awards, attendance, signed forms, payment history) we use a consent workflow: the studio requests an archive or a change, the affected user (or their Primary Caregiver for minors) approves or rejects it, and the action is logged. Studios cannot quietly delete a dancer's record on their own.

You can request a full export of your data at any time by emailing privacy@stagesidedance.com. If you are in a region with additional rights (GDPR, CCPA, similar) we will honor those rights on the same timeline the law sets.

How long we keep information

Permanent records are kept for the life of the dancer's StageSide profile because that is the point of the product. Account information is kept while the account is active and for a short period after closure in case it is reopened. Payment records are kept for the period required by tax and accounting law. Backup copies are rotated on a schedule and eventually purged.

Security

Information is encrypted in transit and at rest. Access is limited to the small set of people who need it to run StageSide. Sensitive operations are logged. No system is perfectly secure, and if a breach ever affects your information we will tell you promptly and tell you what we are doing about it.

Changes to this policy

When we change this policy, we will post the new version here with an updated date. If a change materially affects how we handle your information, we will also notify you directly through the app or by email.

Contact

Questions about this policy, requests for your data, or anything else privacy-related can go to privacy@stagesidedance.com. For general support, see stagesidedance.com/support.

This policy is offered in good faith and in plain English so it is actually readable. It is not legal advice. StageSide is reviewing this document with counsel ahead of general availability and will publish a final version then.

Have a question we did not answer here?