Accounts and profiles
Clerk handles Google and email-code sign-in. We store your account reference, verified email, chosen display name, roles, skills, and any introduction or portfolio link you provide. Your email is not shown publicly. Your chosen display name appears alongside approved song reviews.
Recordings and projects
Microphone access starts only when you choose Record. Recording stays in your browser until you upload it. Uploaded audio is stored privately in Vercel Blob; project records are stored in Neon Postgres. Only you, collaborators assigned by BCMC, and BCMC staff may access your project. Playback and download links expire after fifteen minutes. People who can download a file can retain their copy.
Public demos and feedback
Private submissions are not automatically published. BCMC publishes demos explicitly, using separate public audio storage. Published demos and approved reviews are visible to anyone. Heart counts are public; the site does not publish a list of people who liked a song. New and edited reviews are moderated before public display.
Workspace updates and email
We create workspace notifications for submissions, assignments, new versions, messages, and status changes. Resend delivers transactional email when configured. Emails contain a link to the authenticated workspace, never private audio or message bodies.
Retention and requests
We retain account and project records while they are needed for collaboration and administration. Unfinished uploads may remain in private storage until BCMC removes them. Contact hello@burntchapati.com to request access, correction, or deletion; BCMC will review any ongoing collaboration or recordkeeping needs before responding. Legacy membership applications remain in their separate private review system.
Security and service providers
Vercel hosts this site and audio storage, Clerk provides authentication, Neon stores workspace data, and Resend handles transactional delivery. These providers process the data needed to operate their services. Authentication uses necessary cookies. Server-side permissions protect projects, and rate limits help prevent misuse. No system can guarantee absolute security.