Launch-preparation document

Privacy draft

Last updated: July 11, 2026

This launch-preparation draft describes the intended controlled beta. It requires professional review and must be updated with the production legal entity, contact, hosting region, subprocessors, and retention periods before publication.

Data used

Account data may include email, username, skill level, genre preference, and subscription status. Practice data may include session duration, tempo, notes, lesson progress, and files a user explicitly uploads. Do not put sensitive personal information in practice notes.

Workshop diagnostics

The public workshop stores completion and a capped event log in the user’s browser. It is not transmitted automatically. A user may export and voluntarily share that JSON during beta feedback.

Audio and AI

Any optional feedback upload must disclose storage, deletion, and analysis limits at collection time. Automated timing feedback is approximate and must not be represented as pitch-perfect transcription or professional assessment.

Rights and retention

Before beta, provide working access, correction, export, and deletion procedures. Define retention by data category, delete expired uploads, and document backup deletion lag. Never sell practice data or use it to train models without separate, explicit consent.

Cookies and processors

Authentication cookies are necessary. Optional analytics require a consent decision appropriate to launch jurisdictions. Current intended processors include Supabase for application data and Stripe for test/production payments; production terms must list actual subprocessors.

Return to Riff Forge