Last updated September 2, 2026

Privacy & data use

This is the straightforward version: what Beat Board sees, why it needs it, and which services help process it. Beat Board is operated by Bad Ass SaaS LLC.

The short version

We use your material to operate the studio, create what you request, keep projects available to you, calculate generation costs, and diagnose failures.

Beat Board does not currently sell personal information or use third-party advertising trackers. There is no separate undisclosed human-review or moderation service in the application. The generation providers named below may still log, review, or restrict requests under their own terms.

What Beat Board stores

  • Account data: email address, internal user ID, authentication sessions, and account timestamps.
  • Creative work: songs, lyrics, scripts, prompts, reference photos, faces and characters, costumes, props, storyboards, generated clips, edits, exports, and related project settings.
  • Director activity: tool names and arguments, estimates, confirmations, results, failures, and undo information. Tool arguments can include prompts and selected project details.
  • Operations: provider task IDs, generation status, costs, durations, route and request IDs, errors, and security or reliability logs.

Public music-video pages

Public watch pages record a view and viewing milestones at 25%, 50%, 75%, and 100%, plus replays, shares, and “Make your own” clicks. Records can include the video slug, time watched, referral or promotion code, browser user-agent, and a random watch-session ID.

The watch-session cookie lasts up to one year. Promotion, source-video, and referral cookies last up to 90 days. If an IP-hash secret is configured, Beat Board stores a short daily one-way hash rather than the raw IP in its application database. Hosting and security providers may still process network addresses in their infrastructure logs.

Who processes the work

SupabaseAccount authentication, the application database, and stored project media.
VercelApplication hosting, scheduled jobs, isolated render workers, and build/runtime logs.
OpenAIAI Director conversations and the project context or attachments needed to answer.
xAI / GrokGeneration requests, prompts, and reference media sent to Grok features.
KlingVideo, motion, avatar, and reusable Element requests sent to Kling features.
Music.aiUploaded audio and analysis requests used for music, vocal, beat, and timing work.
fal.aiSeedance 2.5 video-generation requests, plus video and vocal audio when the Sync3 lip-sync route is selected.
ReplicateOnly when it is explicitly configured as the optional Seedance 2.5 provider route.

Only the material needed for the feature you choose is sent to that provider. Those companies operate their own infrastructure and may have independent retention, safety, or abuse-prevention systems.

Cookies and local storage

Beat Board uses Supabase authentication cookies to keep signed-in users authenticated. Public watch pages use the session and attribution cookies described above. These are used for account access, watch-page measurement, referrals, and promised promotions—not third-party behavioral advertising.

Access, retention, and deletion

Project data is kept while it is needed to provide your account and reusable library. Operational records and provider logs can remain longer for reliability, billing reconciliation, security, backups, or legal requirements. Each external provider controls its own retention period.

Access is limited to the user who owns the project and authorized operators or service providers who need it to run and secure Beat Board. Tenant separation is enforced through authenticated requests and database row-level security; privileged service credentials are reserved for server-side jobs that require them.

To ask what is held about you, correct it, or request deletion, email james@badasssaas.com.

When this changes

This page will be updated when Beat Board adds a provider, starts collecting a new category of information, or materially changes how information is used. The date at the top identifies the current version.