Privacy policy
Last updated
This policy describes the free separation, tempo, bass boost and audio practice tools at vocalseparator.com. Listening examples use publicly licensed audio and recorded processing results. Playing an example does not upload your files. Selecting a file for cloud separation first previews it in your browser. Uploading starts when you confirm your audio rights and choose Separate audio, Split into 4 stems, Prepare bass practice or the corresponding extract/remove action on a separation page. Tap tempo measures taps locally. The BPM counter can analyze an audio file on your device, and bass boost applies EQ and prepares a WAV locally, without uploading audio. Audio practice plays your saved file locally, with waveform selection, loop, speed and pitch controls, and MP3/WAV practice export. The result workbench reads your existing stems and applies mixing and practice changes on your device. These local tools do not record from your microphone. Audio, filenames, tap times, BPM estimates and boost settings are not saved to browser storage. Clear the file or leave the page to release local previews and exported audio. Practice settings are kept only in memory unless you explicitly choose to save them as described below.
What we process
Metronome clicks are generated on your device without an audio file or microphone. Its settings stay in memory. Choosing Use in metronome includes the displayed BPM in the destination URL to fill the tempo; that URL may appear in browser history and hosting access logs. It contains no audio, filename or tap times, and does not start playback.
Choosing Save practice setup stores a local file fingerprint (or a hashed result identifier), duration, practice part, speed, pitch, track levels, mute/solo settings, named passages, loop setting, A/B points and save time in this browser. The fingerprint matches the same file when you select it again; audio, source URLs and filenames are not stored. These records are not sent to our server or analytics. Up to 20 setups are kept for 30 days after saving, with expired records removed the next time they are read. You can forget an individual setup or all saved setups in Audio Practice. Clearing this site’s browser storage also removes them. Restoring requires selecting the file again, or recovering an unexpired result, and choosing Restore saved setup; it does not autoplay. Saving settings does not extend the lifetime of separation results. A local clear revision, containing no audio or personal data, prevents a pending save in another tab from undoing Forget all.
When you choose free separation, we process the file, its filename, size and duration. No registration or email address is required. We use a random browser identifier for your daily allowance and a keyed hash of your IP address to limit abuse; application job records do not store the raw IP. Our hosting providers may maintain operational security logs under their own policies.
Before you select a file, we check current free processing availability using that essential browser identifier and network hash. Checking availability does not upload audio, reserve processing or use a free job. The same checks run again when you start separation.
Where your file goes
Paid accounts use Neon Auth to verify your email and manage login sessions. Neon Postgres stores your account identifier, purchase references, minute ledger, private batch metadata and refund status. Waffo Pancake handles billing details and card data on its hosted checkout; we do not receive full card details. Necessary account cookies keep you signed in. Private account pages, checkout tokens and batch names are excluded from our Google Analytics page tracking.
Uploads are sent to private Cloudflare R2 storage. Replicate receives a temporary signed link to run audio separation. The website runs on Vercel, and an Upstash-compatible Redis service stores short-lived job records and usage counters. These providers may process data outside your country. We do not create a public audio library or use your uploads to train our own models.
When bass practice is enabled, our server reads the existing four stems to make listening and practice mixes. This does not send another separation request. These mixes are kept in private R2 storage and share the original result’s download deadline. They are scheduled for deletion when that deadline passes and removed by a subsequent daily cleanup. Download expiry does not mean immediate physical deletion. The one-day lifecycle backup described below also applies. We remove temporary mixing files during normal completion or failure cleanup.
Retention and downloads
The practice workbench reads existing WAV stems in your browser and prepares local MP3 or WAV audio with your chosen levels, speed, pitch and passage. It makes no new separation request and uploads no mix. Prepared audio stays in memory until you leave; save it before closing the page or the result links expire. Settings stay in memory unless you explicitly save them as described above.
Free uploads and processing copies are scheduled for deletion 23 hours after an upload begins. Cleanup runs once a day and processes due files on its next run, normally around 23–48 hours after the upload begins. A one-day R2 lifecycle rule also expires stored files as a backup; physical deletion is asynchronous and can happen after that eligibility time. If cleanup is interrupted, deletion may take longer. Download access expires separately from physical file deletion.
Paid uploads and processing copies use separate private storage prefixes and are deleted during paid maintenance after their jobs finish, or after an abandoned upload has been inactive for a day. Completed paid WAV results are available for seven days after each file is ready; access then ends and maintenance schedules deletion. An eight-day lifecycle backstop is used for paid results, independently of the free one-day rule. Physical deletion is asynchronous. Account, payment and minute-ledger records remain while the account or purchased balance is active and for legitimate accounting, dispute and legal requirements. Contact support for access, correction or deletion requests; records required for those obligations may be retained.
Replicate removes API input parameters, output files and logs after approximately one hour. Free cloud separation downloads expire 55 minutes after processing finishes, independently of the upload deletion schedule. Job metadata expires after 25 hours, and daily usage counters expire within 48 hours. Failure-refund markers expire within 25 hours of the latest confirmed status check. We also keep a cumulative, site-wide processing count without audio or browser identifiers to track overall usage. Read Replicate’s retention policy.
Service reliability records
We keep anonymous daily totals of task outcomes, audio duration and reported processing time to detect failures and control costs. These totals contain no audio, filenames, download links, IP addresses or browser identifiers, and expire within 35 days of their last update. Maintenance summaries are kept for up to seven days. Temporary upload reservations expire within 15 minutes. Job records also hold the processing status and temporary result links so a refresh can recover completed work; saving a link does not extend the file’s lifetime.
Optional usage measurement
When enabled, we count tool views and actions such as file selection, playback, download preparation, practice download link requests and links between tools to improve them. Counts are grouped by tool and a fixed page label. For audio practice, we count file selection and playback, setup save/restore/removal, clip and pitch preparation, playback, download requests and export failures; loop and speed actions are also counted on result pages. These events contain no filenames, loop positions, speed values or semitone changes. For the connected workbench, we count opening, actual playback, setup save/restore, export preparation, preview, download requests and failures. Saved passage names, fingerprints and mix settings are not sent. For stem mixes, we count preparation requests, ready mixes, playback, download requests and failures; track levels, mute and solo settings are not sent. For the BPM counter, we count actions such as starting a tap or audio measurement, finding a reading, an unsuccessful analysis and copying; tap times and BPM values are not sent in these events. For the metronome, we count start requests, successful starts, tempo changes, taps, interruptions and failures; events contain no tempo, beat pattern or volume values. For bass boost, we count selecting a file, preparing or playing a result, requesting a download and failures; audio and EQ settings are not sent. A download request does not tell us whether a file was saved. You can also choose to give fixed-choice result feedback, including whether it helped and one optional improvement category. We do not collect free-text feedback in these counters. Public example playback and clicks back to the tool are counted separately from your own processing results and downloads. These first-party counters do not contain audio, filenames, download links, job credentials, referrers or user identifiers, and do not use analytics cookies or browser storage. Each action is counted at most once per loaded tool page; a refresh starts a new visit. They do not identify unique people or prove a file was saved to disk.
Daily totals expire within 35 days. A keyed network hash is used only for analytics request limits and expires within two minutes. We honor Do Not Track and Global Privacy Control signals for this measurement. Hosting providers may still keep operational logs. Analytics being unavailable does not prevent you from using the audio tool.
Google Analytics
We may use Google Analytics 4 to understand visit sources and tool use. It loads only after you choose Allow analytics. Declining leaves the tools available. When enabled, Google receives public page paths, titles, a simplified referring website, browser and device information, and fixed action labels such as starting separation, playing a result or requesting a download. Analytics cookies distinguish visits and sessions and are configured to expire after 60 days. Audio, filenames, temporary download URLs, job credentials, tap timings, BPM values, EQ settings, page query strings and fragments are excluded from these events.
Choose Analytics cookies in the footer to change or withdraw your choice. We store only the choice and its expiry in local browser storage for up to 180 days. Withdrawing disables further measurement and clears our analytics cookies; it does not erase data already received by Google. Do Not Track and Global Privacy Control prevent this measurement. Google signals, advertising storage, advertising personalization and automatic enhanced measurement are disabled. Google may process analytics data outside your country. See how Google uses information from sites that use its services. Analytics consent is separate from the first-party aggregate counters and essential job recovery cookies described in this policy.
Capacity measurement
When measurement is enabled, we also count requests refused because of capacity, allowance or request limits, grouped by reason and UTC hour. These anonymous totals include repeated attempts; they do not identify people. They expire within 35 days and honor the same privacy signals. Only temporary, two-minute network hashes limit collection traffic. We do not attach filenames, audio, job credentials or browser identifiers to these summaries.
Access and controls
Temporary, unguessable credentials protect your job. Anyone you share a signed download URL with can access the file until that URL expires. An essential, HttpOnly cookie for each tool remembers its latest job for up to 25 hours so refreshing this browser can recover its status. It contains a temporary job credential, not the audio. The stem splitter, bass remover, bass extractor and drum extractor share the same latest four-track job. The BPM counter does not use these cookies. Starting with another file clears that recovery entry; closing the tab does not cancel processing. A separate essential cookie stores a signed, random browser identifier for up to 30 days to apply your shared free allowance across both tools and network changes. It does not grant access to your audio. Analytics cookies are optional and controlled separately. We do not fingerprint your device, use advertising cookies or sell uploaded audio. Contact us about a data request and include your approximate upload time, without sending sensitive audio unless requested.
Privacy questions
You can reach us through the contact page. Please do not send passwords, card details or private audio in an initial support message.
Contact: support@vocalseparator.com. For copyright reports, use the subject “Copyright report”.