PRIVACY
Murmur handles your recordings, melodies, songs, and payment state so a hum can become a song you can save, edit, and share.
Effective July 11, 2026
A recording is used for melody transcription and, when raw-hum style conditioning is used, sent with the generation request to the music processor. Murmur saves melody and song data by default, not the original hum as a long-term account asset.
Saved songs, arrangements, and visuals live in your account or local demo space. They leave that space only when you export or share them.
Murmur does not currently load generic ad analytics SDKs and does not sell your personal data to data brokers.
Account deletion is available in the app. For a data copy, correction, or privacy help, contact [email protected].
DATA MAP
Following the clearest privacy pages, we split data into the categories people actually ask about: inputs, work, account, payment, local state, and diagnostics.
Collect
Basic profile details from your sign-in provider, such as name, avatar, email, or provider ID.
Use
To identify your song shelf, sync your balance, protect your account, and let you continue across devices.
Keep
Kept while your account exists; after a deletion request, handled through the deletion flow and required billing or security retention.
Collect
Short audio you record or upload, plus derived notes, rhythm, key, quality diagnostics, target instrument, and raw-hum conditioning strength.
Use
To identify melody, repair noise or pitch issues, and optionally condition a generation on the texture and expression of the original hum.
Keep
Raw audio is used for the transcription request and applicable style-conditioning requests by default, and is not kept as an account asset; melody results may be saved with the song.
Collect
Title, vibe, BPM, key, track state, visual settings, audio exports, and share files.
Use
To save, reopen, play, keep editing, render cover art, and export shareable artifacts.
Keep
Kept in your shelf until you delete the song or account; local demo data may live only on the current device.
Collect
Notes balance, spend records, top-up tier, receipt email, amount and currency, payment method, provider order IDs, refund state, and billing callback events.
Use
To debit creation actions, grant purchased notes, process refunds, prevent duplicate grants, and reconcile payments.
Keep
Kept as needed for accounting, tax, fraud prevention, and support. Murmur does not receive or store full card numbers or WeChat Pay credentials.
Collect
Language, creative preference, developer mode, sidebar state, local audio-unlock state, guest notes, and small local event history.
Use
To keep the experience stable on this device without turning every small preference into server data.
Keep
Stored mainly in browser localStorage or sessionStorage; clearing browser data removes it.
Collect
Request IDs, routes, error codes, timing, rate-limit state, audio quality metrics, and non-sensitive runtime diagnostics.
Use
To debug failures, protect the service, prevent abuse, and confirm the hum-to-song path has not regressed.
Keep
Minimized where possible, favoring structured troubleshooting data over raw creative content.
SERVICE PROVIDERS
Murmur keeps sign-in, transcription, music generation, AI editing, payments, and infrastructure behind clear boundaries. Providers should process only the data needed for their role.
Optional sign-in provider
Used for OAuth sign-in. Murmur uses only the basic account details needed to log you in.
Humming transcription service
Processes short audio and returns melody, rhythm, and diagnostics. It is not a public social platform.
Production music processor
Production requests include the generation prompt, clip duration, request identifier, and optional melody. When raw-hum style conditioning is used, Murmur also sends the conditioning strength and original hum audio; otherwise the raw hum is not sent for music generation.
Optional Studio edit understanding
When AI editing is enabled, Murmur sends your edit instruction and necessary context to understand the change, not the full raw recording.
Payment and checkout processing
Waffo may host card checkout; eligible CNY WeChat Pay orders may be initiated through ZPay. Murmur sends the product description, amount and currency, internal account and order references, return and callback URLs, and the receipt email or client IP when required, then receives order results to grant notes.
Infrastructure
Used to run the web app, database, file storage, backups, and necessary security monitoring.
AI AND TRAINING
Murmur does not currently sell or publicly provide your raw hums, saved songs, or exports as general model-training data.
If a future quality program needs to keep raw audio samples, it will be an explicit choice rather than a default setting, with purpose, retention, and opt-out details stated clearly.
YOUR CHOICES
You can request account deletion in the app. A grace period may apply; after it ends, profile and linked content are removed unless limited records are required for law, billing, refunds, security, or dispute handling.
For a data copy, correction, consent withdrawal, complaint, or region-specific privacy request, contact [email protected].
CONTACT
Include your account email, relevant song ID, or order number when useful. Please do not email card numbers, identity documents, or unnecessary sensitive details.
Murmur is a [p → q] project. This notice describes Murmur's current privacy practices. As account, mobile, notification, or quality-improvement features evolve, we will update this page and ask for renewed consent when needed.
