Privacy

What BOOTH AUDIO Collects

• Account and session data, including a BOOTH AUDIO user ID, guest or registered profile status, display name, email address if you add one, account claim events, and an essential signed session cookie.
• SoundCloud data you authorize, including profile ID, username, likes, playlists, track IDs, titles, artist/profile metadata, artwork, duration, public URLs, genre, BPM, download and purchase metadata, license fields, descriptions, and publisher metadata.
• OAuth credentials for connected services, including access tokens, refresh tokens when provided, token expiration times, and granted scopes.
• Source lookup data, including pasted SoundCloud links, lookup queries, candidate store/source URLs, match evidence, confidence scores, source response metadata, latency, status, and error messages.
• Technical and support data, including server logs generated by hosting or Supabase, IP/device data those providers process, email verification delivery data, and messages you send to BOOTH AUDIO.

How BOOTH AUDIO Uses Data

• To create and secure guest and registered BOOTH AUDIO workspaces.
• To connect SoundCloud, refresh authorized tokens, and import a limited library preview for source-prep workflows.
• To match imported tracks against likely source pages, store acquisition candidates, and show confidence or availability signals.
• To verify email ownership, recover or merge workspaces, respond to support/privacy/security requests, debug the beta, and prevent abuse.

Storage, Sharing, and Vendors

BOOTH AUDIO stores product data in Supabase and uses server-side API routes for SoundCloud and acquisition lookups. Verification email may be sent through Resend when configured. BOOTH AUDIO does not sell personal information, does not host audio files, and does not use advertising cookies in the current beta code.

SoundCloud continues to process your data under its own terms and privacy policies. BOOTH AUDIO may send lookup requests to music source providers or public web pages when you ask BOOTH AUDIO to resolve a track source.

Cookies and Local Storage

BOOTH AUDIO uses an essential HTTP-only cookie named booth_session to keep your workspace available across visits. SoundCloud OAuth flows also use short-lived state cookies for security. The current app uses browser local storage only to remember whether a source link was opened. BOOTH AUDIO does not currently use analytics, ads, remarketing pixels, or non-essential tracking cookies.

Your Controls

Use the account page to disconnect SoundCloud, export your BOOTH AUDIO workspace JSON, or delete your BOOTH AUDIO workspace. For correction, recovery, or requests that the account page does not cover, contact privacy@boothaudio.com from the email tied to your BOOTH AUDIO workspace.

You can also remove BOOTH AUDIO from your SoundCloud account settings. Provider-side data remains with SoundCloud under its own policies.

BOOTH AUDIO is not intended for children under 13. If you believe a child under 13 used BOOTH AUDIO, contact privacy@boothaudio.com.

Retention and Security

BOOTH AUDIO keeps account, connection, import, and lookup data while your workspace is active or while needed for beta operations, security, debugging, or legal obligations. OAuth tokens and verification codes are high-risk data and should be treated as confidential. Report security concerns to security@boothaudio.com.