Legal overview

Policy needs for Stagely

Overview

This page summarizes the policy coverage Stagely uses for its dance studio, family, staff, and dancer workflows.

Child and dancer privacy

Stagely stores dancer names, ages or birthdates, classifications, photos, attendance notes, routines, form responses, and family links. If children under 13 use the service or submit data directly, COPPA-style parental notice, verifiable consent, parent access, deletion, and retention limits should be built into the launch plan.

Studio as customer and data contributor

Studios create rosters, invite staff and families, upload documents and songs, take attendance, issue invoices, and message families. The Terms should make studios responsible for having authority to upload dancer and family information and for honoring requests they receive from families.

Family and guardian accounts

Parents and guardians need clear rules for creating accounts, connecting to a family or dancer, keeping contact details accurate, supervising dancer access, requesting deletion, and reporting unauthorized access.

User content and media

The app handles profile photos, dancer photos, routine images, form uploads, studio updates, comments, family messages, and official music cuts. The Terms should grant Stagely a limited license to host and transmit content while keeping ownership with the uploader.

Payments and invoices

The app tracks invoices, balances, payment links, e-transfer instructions, and future payment provider status. The Terms should separate Stagely platform fees from studio-to-family payment obligations and identify third-party payment processors where used.

App store compliance

Apple and Google both require accurate privacy disclosures. The Privacy Policy should match App Store privacy details, Google Play Data safety, account deletion flows, and any Families or children-targeting declarations.

Recommended documents

Required

Privacy Policy

Explains what personal information Stagely collects, how it is used, how child-related information is handled, and how users can request access, correction, deletion, or account removal.

Required

Terms and Conditions

Defines account rules, studio responsibilities, acceptable use, user content permissions, payment terms, data controls, suspension rights, and service limits.

Store and launch checklist

  • Publish the Privacy Policy URL in the app, App Store Connect, and Google Play Console.
  • Publish the Terms URL before accepting studio or family accounts.
  • Add an account deletion route in the app and on the web, or clearly link users to a deletion request flow.
  • Inventory SDKs before release, including Firebase, Google Analytics, payment tools, crash reporting, messaging, and push notification providers.
  • Decide whether the app is directed to children, mixed-audience, or adult-administered, then align COPPA, Apple Kids Category, and Google Play Families answers.
  • Confirm whether launch jurisdictions include Canada, the United States, Quebec, California, the United Kingdom, or the European Economic Area, because each can add privacy-rights wording.
  • Confirm how waivers, medical form categories, photos, music files, tax data, and studio contracts are handled before paid launch.

Research basis

FTC COPPA FAQUsed for child privacy notice, consent, access, deletion, retention, and photo/audio handling considerations.Apple App Review GuidelinesUsed for in-app privacy policy, account deletion, consent, child data, and Kids Category considerations.Apple App Privacy DetailsUsed for App Store privacy label and data category considerations.Google Play Data safetyUsed for store listing privacy policy, data collection, data sharing, security, and deletion declaration considerations.Google Play Families PolicyUsed for children-targeted or mixed-audience app requirements.Office of the Privacy Commissioner of Canada - PIPEDAUsed for Canadian privacy principles including consent, limiting collection, safeguards, openness, access, and retention.