Privacy policy

Effective: November 13, 2026

CleanBeatz is operated by Serious Business Software LLC, the business behind Serious Business. This policy explains how we handle information when you use cleanbeatz.com, the CleanBeatz web app, the CleanBeatz app for iPhone, iPad and Mac, and the CleanBeatz Android app. It covers the service’s account, audio-processing, billing, waitlist, and feedback features. Contact us at [email protected] with questions or requests about your information.

What happens to your song

CleanBeatz is an online processing service. Your upload is stored in private Cloudflare R2 storage and sent to our processing service on Modal to separate the vocals from the music. The separated vocals are transcribed with Deepgram and Whisper models through Cloudflare Workers AI. For some or all songs they are also transcribed with ElevenLabs Scribe, which we reach through OpenRouter. Only the separated vocal track is sent, as an audio file with no account, email, song title or file name. Lyric text is checked for explicit content using Google’s Gemini API through Cloudflare AI Gateway, with a Llama model on Workers AI as a fallback.

To identify a song, our processing service can send one or two 12-second clips of the original recording to AudD. Those requests contain the clip and recognition settings, rather than your CleanBeatz account ID or email. We also use the file’s song tags, when present. To find published lyrics for an additional check, we send song-title and artist search terms to LRCLIB. Those terms can come from your file’s name or tags or from recognition results. Avoid putting personal information in file names or tags.

We store the upload, vocal and instrumental tracks, preview audio, word-level transcript and flags, your lyric-sheet edits, and any exported clean version to provide the result. Exports are rendered on Cloudflare. Playback in the browser and in the apps mixes the preview tracks on your device. The Android app keeps a temporary copy of those tracks on your device while you review a song and removes it when you sign out. The iPhone, iPad and Mac app keeps the preview tracks of the song you last opened in its cache, and a downloaded clean version in a temporary folder until you save or share it.

Songs are private to your account and are not published for other users. Processing involves the providers described here; “private” does not mean that the audio stays on your device. Download links are temporary access links: anyone you give a valid link to may be able to use it until it expires.

Word fingerprints (optional sharing)

When you start a song you can choose to share “word fingerprints”. This is a checkbox on the upload screen. It is off by default, it applies to the song you are starting, and your choice is remembered on that device. Turning it off stops sharing for later songs.

What a word fingerprint is. After we find explicit words in your song, we make a small set of numbers for each one from the sound in the few seconds around it: values describing pairs of frequency peaks, with their timing relative to the word. Each set also carries the word’s category (such as “strong”) and an approximate position in the song. These are numbers; they cannot be played back, and they contain no audio, lyrics, transcript, file name, or edits.

Where they go and what they are for. If you opt in, we send them to our own song database (Radio Edit), which runs on Cloudflare. We only send them when the database already holds that song as an explicit entry of about the same length. The database uses them to find the same words in other people’s copies of the song, so the next person’s copy is cleaned more accurately. We do not sell or publish them.

How they are linked to you. Each fingerprint is stored with a key made from your account and the song, using a secret that only the CleanBeatz service holds. The database does not store your name, email, or account ID. Because we can recompute that key from your account, we can find your contributions and remove them. Your own record of which keys you used is kept with your account and moves with it if an anonymous account is merged into a signed-in one.

Your consent and withdrawing it. Sharing is based on your consent, which you can withdraw at any time. Choose “Remove shared fingerprints” in the account menu of the web app. It stops any song still being processed from sharing, removes the fingerprints you shared across all your songs from the database, and turns sharing off on that device. Deleting your account does the same first. If other people’s copies of the same song confirmed the same word, that word’s entry stays, without your confirmation. If we cannot reach the database, the app tells you so and you can try again; it does not say it worked unless it did.

Without opting in. Whether or not you share, while we process a song we may compute its fingerprints in memory on our processing service and compare them with fingerprints already in the database, to find explicit words more accurately. This uses the title and artist we identify for the song, as our lyrics lookup does, and nothing from your audio is stored or sent as a result. We also ask the database how many explicit words a song is expected to contain, using that title and artist, and keep only a verdict and two counts with the job’s processing statistics.

Other information we handle

Accounts and sign-in

We store an account ID, sign-in provider details, the name and email supplied by Apple or Google, session records, and your plan, song balance, and usage. The app can create an anonymous account before sign-in. An anonymous account still has an identifier; it is not a promise that your activity is unidentifiable. Signing in can merge that account’s songs and balances into your signed-in account.

The Android app stores your session and settings on your device, and has no analytics or advertising SDK. The iPhone, iPad and Mac app keeps your session token in the device Keychain and its settings on the device, and has no analytics or advertising SDK. Before its first upload it shows the processing providers named above and asks for your permission; you can withdraw it in Settings under Song processing, after which songs are no longer uploaded. To give each device its free songs once, it sends Apple’s DeviceCheck token, which lets us ask Apple whether that device already claimed them without receiving a device identifier. The web app uses browser storage to keep you signed in and remember settings such as your theme and purchase choice. Sign-in also uses authentication cookies. These are separate from analytics.

Song-ready alerts and Lock Screen progress

If you allow notifications in the iPhone, iPad or Mac app, it sends us the push token Apple issues for that device, and we store it with your account so we can tell you when a song is ready or could not be cleaned. On iPhone, a song you start can also show its progress as a Live Activity on the Lock Screen; for that, the app sends us that activity’s push token, which we store with the song. We send these updates through Apple Push Notification service, and each one contains the song’s name and its progress or result, including how many words were marked. Notifications are optional: the app works the same without them, and you can turn them off in your device’s Settings at any time.

Payments

Stripe handles web checkout and billing. We send Stripe the account reference, email, and name needed to associate the purchase with your account. We receive and store customer and transaction identifiers, products, purchase or subscription status, dates, and entitlement information. Our payment ledger also records provider-verified captured and refunded amounts, currency, dispute status, and payment, checkout-session, or invoice references. We do not collect your full payment-card number through the CleanBeatz app. Stripe handles payment details under its privacy policy.

Where a client uses App Store or Google Play purchases, Apple or Google handles payment and we verify purchase records to apply the entitlement. App Store purchases carry an account token that links them to your CleanBeatz account, and the app sends the signed transaction records to us so we can add your plan or songs. Their payment and account services have their own privacy terms.

Optional feedback and support

You can send feedback without rating a song. After listening to a clean output, you can optionally give a thumbs up or down, select a reason, and add a comment. Playback, editing, and downloading do not depend on giving feedback.

Feedback is linked to your account, including an anonymous account if that is what you are using. Song feedback includes the song’s internal ID, whether you rated preview or full output, the edit version, cleaning level and treatment, and the client version. We also store your rating, selected reasons, comment, and submission time. General feedback has no song reference. Feedback submissions do not attach audio, lyrics, file names, or media links. Please do not put personal information, private lyrics, or other sensitive material in your comment.

The service owner reviews feedback through a protected admin console to understand problems and improve CleanBeatz. Feedback is not a public review. If you email us, we also receive your address and whatever you include in the message. Support email is stored in HeardKit, our support desk running on Cloudflare. Its automated triage can categorize and summarize message content using Cloudflare Workers AI to help us respond.

Waitlist and service email

If you join the waitlist, we store your email, selected platforms, locale if provided, signup source, and confirmation and notification dates. Confirmation and launch messages are sent through our freesend email service, which uses Amazon Simple Email Service. Cloudflare Turnstile processes browser signals to check for automated submissions. You can use the unsubscribe link in waitlist email to remove your signup.

Security, operation, and usage information

Requests to our hosting and processing providers include technical information such as IP addresses, browser or client details, request paths, and times. Our operational records include job IDs, processing states, durations, error codes, and billing events. We use these to run the service, investigate failures, reconcile song balances, and prevent abuse.

For the owner’s private operations console, the service also keeps a short activity log of product events (for example, a song started, a download requested, a payment completed), each with the approximate city, region, country and rounded coordinates (to about 10 km) that our hosting provider derives from the connection. These entries are not linked to an account, job or IP address, and are deleted after 30 days.

For signup and feedback rate limits, the application stores keyed representations of account or network identifiers rather than raw IP addresses in its rate-limit tables. This does not prevent the hosting providers from receiving IP addresses when handling a request.

The website and web app use Abner for cookieless page-view and product-usage analytics. Product events describe actions such as starting cleaning, opening checkout, or requesting a download, with settings or product identifiers. The event properties sent by CleanBeatz do not contain audio, lyrics, file names, email addresses, or feedback comments. The current web-app sender uses the app home address rather than the song-review URL, limits referral information to the referring origin, and does not automatically track download-link destinations. It respects browser Do Not Track and Global Privacy Control signals. The analytics server still receives technical information such as the connection IP address and user agent. The marketing website uses Abner’s page-view script. These analytics are separate from the account and job records used to provide the service.

Before the October 28, 2026 update, the web app used Abner’s general tracking script, which could send full page URLs and automatically tracked link destinations, including internal song references and temporary download links. Removing that behavior does not itself delete previously sent analytics records.

Why we use this information

We use it to provide sign-in, process and deliver your song, save edits, manage purchases and song balances, answer feedback and support requests, send requested waitlist messages, understand usage, and protect the service against abuse. Optional feedback helps us find product problems; it does not give us access to another copy of your audio.

Providers and their data practices

The main providers and services involved are:

Provider or serviceInformation and purpose
CloudflareWebsite and API hosting, account and job storage, audio storage and delivery, export rendering, Workers AI transcription and fallback classification, AI Gateway, email routing, and Turnstile
Radio Edit (our own song database, on Cloudflare)Song title and artist for lookups, and, only if you opt in, the word fingerprints described above
ModalThe uploaded recording, temporary working files, and job details needed for vocal separation and song identification
OpenRouterRoutes speech-to-text requests to ElevenLabs; receives the separated vocal track of an uploaded song for transcription
ElevenLabsSpeech-to-text (Scribe) of the separated vocal track, reached through OpenRouter
Google Gemini APILyric text and classification instructions sent through Cloudflare AI Gateway to check explicit content
AudDShort original-audio clips for song identification
LRCLIBSong-title and artist search terms for published-lyrics lookup
Stripe, Apple, and GoogleSign-in or purchase information for the features they provide
Apple Push Notification servicePush tokens, and the song name and progress or result in the alerts and Live Activity updates you allow
Amazon Web Services through freesendAddresses and message content for transactional and waitlist email
AbnerWebsite and web-app usage analytics

The model names above identify the models used through Workers AI; they do not mean that CleanBeatz sends the recording directly to separate Deepgram or OpenAI API accounts.

We share information with these providers only to run CleanBeatz, and each one is bound by its terms with us to protect the information it receives at least as well as this policy describes. AudD receives only the short clips described above, without your account ID or email, and may keep fingerprints of them for music recognition. LRCLIB receives only song-title and artist search terms, which are not linked to you or your account.

Provider handling is not the same as our media-storage schedule. Cloudflare AI Gateway can log or cache model requests and responses. We use the Gemini API as a paid service. Under Google’s terms for paid services, Google does not use the lyric text we send to improve its products, though it can keep it for a limited time to detect abuse. See Google’s API terms and data logging and sharing documentation. For the ElevenLabs path we ask OpenRouter to use only endpoints with zero data retention, to refuse providers that collect data for training or other purposes, and to send the request to no other provider; we rely on OpenRouter’s and ElevenLabs’ terms for how they honor this. We do not promise that every provider operates with zero retention. Do not upload confidential or sensitive recordings that you do not want processed by these services.

Retention and deletion

InformationCurrent retention and deletion behavior
Uploads, separated tracks, preview audio, transcript files, and exports in our audio storageScheduled for deletion 7 days after a song becomes ready. Cleanup runs periodically, so deletion is not instantaneous at the seven-day mark. The audio bucket also has an eight-day object-age deletion rule as a backstop.
Failed, canceled, or abandoned uploadsFailed and canceled files are removed by the cancellation or cleanup flow. Uploads that are not started are scheduled for cleanup after two hours.
Job metadata, including the song title, settings, edits, state, and datesRetained after audio expires so the app can show song history. Deleting the song removes its job record; deleting the account removes its job records.
FeedbackScheduled for deletion after 180 days, or earlier when its account is deleted. Deleting a song removes the feedback’s song link but does not delete the feedback itself.
Rate-limit recordsScheduled for deletion after one day.
Waitlist signupKept until you unsubscribe or request removal; a signup that has received its launch notification is scheduled for deletion 30 days later.
Push tokens for alerts and Live ActivitiesA device’s token is deleted when Apple reports it is no longer valid, and with your account. A song’s Live Activity token is removed after the song finishes, when Apple reports it is no longer valid, and with the song.
Account and session informationKept to operate your account; account deletion removes the service’s account, sessions, linked sign-in records, songs, and feedback.
Purchase and support recordsSome transaction identifiers, support-credit records, and billing or security records remain after account deletion for reconciliation and abuse prevention. The payment ledger does not store your account or Stripe customer ID, but its provider payment references remain. The application does not have a single automatic deletion period for all such records. Payment providers keep their own records under their terms.
Word fingerprints you chose to shareKept in our song database until you remove them (account menu, or by deleting your account) or the song’s entry is removed. The temporary file of the song’s fingerprints used to prepare them is deleted right after they are sent, and in any case with the job’s other files.
Processing statisticsWhile a job exists, operational outcome records include its ID, dates, duration, status, and errors. On song or account deletion, these are reduced to daily aggregate counters without the account or job ID, title, lyrics, or media. Those aggregate statistics are retained.
Processing coordination on ModalKeyed job references, request digests, operation states, provider invocation identifiers, and timestamps help prevent duplicate processing. These records do not contain audio, lyrics, titles, or account IDs. Modal expires them after seven days without access.
Operational and provider logsSeparate from the audio bucket and may have different retention periods. The seven-day audio deletion schedule does not delete records held in provider logs, model-request logs or caches, analytics, or payment systems.

You can delete an individual song or your account from the account controls in the web app or the Android app, or in Settings in the iPhone, iPad and Mac app. How to delete your account has the steps, including what to do without the app. Account deletion first requests cancellation of any web subscription so it does not continue billing an account that has been removed. For a subscription billed through an app store, use that store’s subscription controls as well.

Deleting CleanBeatz data does not delete a file you downloaded to your device or a copy you shared yourself. If you need help with deletion, access, correction, or another privacy request, contact [email protected]. We may need to verify that the request concerns your account before acting on it.

Children and sensitive material

CleanBeatz is intended for adult instructors, coaches, DJs, and other adult users. Do not submit children’s personal information or sensitive personal recordings as song uploads or feedback. Contact us if you believe such information has been submitted so we can investigate and remove it where appropriate.

Security and changes

We use encrypted connections, private audio storage, authenticated account access, and restricted administrative access. No online service can guarantee absolute security.

We update this page when our practices change and show the revision date above. Contact [email protected] with questions about this notice or your information.