RECITAL FLOW Built for Google Workspace™
Legal Documentation

Privacy Policy

Last Updated: August 29, 2026 • Effective Date: August 29, 2026

Student Privacy & Google Workspace Containment

Recital Flow is architected natively for Google Workspace™. All student records, registration responses, backing tracks, sheet music PDFs, and presentation slides remain 100% inside your school's own Google Drive™ account. When organizers broadcast a live audience schedule, only the masked public lineup is rendered via Amazon Web Services (AWS) serverless edge caching, which is instantly purged when a recital is unpublished or deleted.

1. Information We Process

Recital Flow operates as a workflow orchestration tool within Google Apps Script. Depending on how you configure your recitals, the application processes the following data within your Google Drive:

  • Performer Information: Student given name, surname, tutor group/year level, instrument, and teacher name.
  • Performance Details: Musical piece titles, composers, performance duration, accompaniment requirements, and equipment needs.
  • Media Attachments: Backing track audio files/links, sheet music PDF scores, and audition video links provided by students or organizers.
  • Organizer Preferences: School logo image URLs, concert welcome notes, audience guidelines, and privacy mask preferences.

2. Google Workspace Scopes & Permissions

To function, Recital Flow requests authorization for specific Google Workspace scopes. These permissions are executed purely on your behalf:

Google Forms™ & Google Sheets™
Used to create concert registration forms, receive performer responses, and store lineup sequencing.
Google Drive™
Used to organize recital folders, upload backing tracks/scores, and save collated media packages.
Google Slides™
Used strictly to generate presentation decks for live stage projector display during recitals.
Google Apps Script Triggers
Used to monitor form submission capacity limits and automatic opening/closing schedule dates.

3. Compliance with Google API Services User Data Policy

Recital Flow's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We do not use Google Workspace data to train artificial intelligence or machine learning models.

4. Student Privacy, Minor Protections & Public Schedule Broadcasting

Because Recital Flow is designed for schools, academies, and youth music departments, safeguarding minor identities is paramount:

  • Public Schedule Name Masking: Organizers can enforce strict privacy formats on audience schedule views (e.g. First Initial + Surname like "J. Thorne" or Initials Only like "J. T.") to safeguard student identities on public display links.
  • Audience Schedule Broadcasting (AWS Serverless): When an organizer publishes a public schedule link for parents, only the masked public lineup (performer name mask, piece title, instrument, and time) is cached on high-speed Amazon Web Services (AWS) serverless edge infrastructure for low-latency spectator viewing. No private student emails, parent contact information, raw files, or internal notes are ever broadcast.
  • School-Controlled Data: Master student records reside exclusively under the school's own Google Workspace for Education domain, respecting institutional data retention and compliance policies (FERPA, COPPA, GDPR-K).
  • No Advertising or Behavior Tracking: We never display advertisements, profile student behavior, or track visitors across the web.

5. Payment Processing (Stripe)

Payment transactions for Recital Flow PRO subscriptions are handled securely by Stripe. We do not store or process credit card numbers or financial account credentials on our systems.

6. Data Retention & Immediate Deletion

You retain total ownership of all generated recitals, spreadsheets, and files:

  • Immediate Cloud Purge: When an organizer unpublishes or deletes a recital in the Director's Console, Recital Flow dispatches an immediate delete request to remove any cached public schedule data from the AWS cloud infrastructure.
  • Google Drive Purge: Deleting a recital moves its associated Google Form, Sheet, and recital subfolders directly into your Google Drive Trash. No ghost copies or shadow databases are retained.

7. Contact Us

If you have any questions or inquiries regarding this Privacy Policy or institutional compliance, please contact:

Recital Flow — Privacy & Governance