Privacy Policy
How LyricCut handles your audio files, browser-local edits, optional AI lyric transcription, and account data.
Local Editing vs. Cloud AI Processing
LyricCut is built with a strict separation between local browser editing and opt-in cloud AI processing:
- Local browser tools (default, no upload) — Opening MP3, WAV, M4A, AAC, FLAC, or OGG files, viewing waveforms, importing or tap-syncing
.lrclyrics, trimming, applying fades, merging clips, and exporting 192 kbps MP3 or 16-bit PCM WAV happen entirely inside your browser via the Web Audio API and local encoding. These audio files never leave your device. - Opt-in Cloud AI (
AI Lyrics) — Only when you sign in and explicitly trigger AI Lyrics is your audio file (up to 60 MB / 15 minutes) uploaded over HTTPS to our processing backend.
AI Models and Sub-processors
When you run a cloud AI task, your uploaded audio is processed solely to generate timestamped lyrics for your project:
- Storage and preparation — Cloudflare R2 stores uploads privately. Our backend filters audio for transcription and estimates cut boundaries.
- Lyric transcription (ASR) — Spoken and sung vocals are transcribed using Whisper Large v3 via the Groq API. The service may use track metadata to look up timed lyrics in LRCLIB.
- No model training — We do not sell your audio or lyrics, and we do not use your uploaded audio files to train general-purpose AI models.
Retention and Automatic Deletion
- Local sessions — Unsaved editor states and theme preferences are stored locally in your browser via
IndexedDB(LyricCut_DB) andlocalStorage. Clearing your browser site data removes them immediately. - Cloud AI assets — Uploaded audio and temporary processing files are scheduled for deletion after 7 days.
Account, Billing, and Usage Data
You can use all local cutting tools without an account. If you create an account or purchase AI minutes, we collect only what is required to run your account:
- Account identity — Your email address, display name, and profile avatar (when signing in with email/password or Google OAuth), managed via secure session cookies.
- Credit ledger and jobs — Records of your AI credit balance, audio job duration, processing status, and automatic refunds for failed or canceled jobs.
- Payment records — Checkout and billing are handled by third-party payment processors (such as Stripe, Creem, or PayPal). LyricCut never stores full payment card numbers or CVV codes.
- Essential diagnostics — Basic error logs and request metadata (such as HTTP status and latency) used to keep the studio reliable and prevent abuse.
Cookies and Local Storage
LyricCut uses essential cookies and browser storage for:
- Keeping you signed in across sessions (authentication session cookie).
- Remembering your dark/light theme preference and interface language.
- Restoring your in-progress local editing session in
IndexedDB.
Security
All data transmitted between your browser, our servers, and third-party AI or payment providers is encrypted in transit via HTTPS/TLS. Audio uploads use time-limited signed URLs to private storage.
Your Rights
You may view, update, or delete your account data, export your local clips at any time, or request removal of your stored cloud projects and account history by contacting support through the account settings page or our website contact channel.
Changes to This Policy
When we introduce new processing models, change retention windows, or update our privacy practices, we will revise this page and update the date shown at the top.