Legal
Privacy & Analytics
Effective date: November 10, 2026
SoundToMIDI is designed to keep music files private. This page explains what stays on your device, what limited information our service providers may process, and how to control analytics.
1. Local audio processing and optional cloud projects
Compatible audio is decoded and transcribed in your browser. Conversion does not upload audio. “Save project” uploads your editable notes, project name, settings, Raw MIDI and edited MIDI to private Cloudflare storage. Original audio is uploaded only when you check “Also back up original audio”. Audio backups support up to 25 MB; for videos we back up only the decoded audio track as WAV. Unchecking audio backup and saving removes an existing cloud audio copy. Save again after edits. Older note-only projects cannot recover an original MIDI or audio file that was never saved. You can delete a cloud copy and its audio from My projects. Sign-in and checkout may keep a temporary draft, including the source file, in this browser for up to seven days to restore your work when you return. Clearing browser data can remove unsaved drafts sooner. Download a backup of important work.
Google sign-in provides your account identifier, name, email address, verification status and profile image. We store a session cookie, account details, orders, shared credit balance and project entitlements to provide sign-in and purchase recovery. We also retain signup attribution and basic security information such as IP address and country. Deleting a cloud copy does not remove transaction records or restore spent credits. Contact contact@soundtomidi.com to request account deletion; records needed for payment reconciliation may be retained.
Changing language can temporarily save your current recording, selection and note edits in this browser so the equivalent page can restore them. A handoff is valid for five minutes and is deleted after use; expired handoffs are removed on the next handoff access. These files are not sent to us or a translation service. Clearing this site's browser data removes locally stored work.
Optional cloud music arrangements
Music arrangements are separate from the local converter. Only after you choose an audio file, confirm you have permission to use it, and press Generate do we upload the decoded audio excerpt to private Cloudflare storage and share a temporary signed download link with Kie, our music generation provider. Kie processes the audio and style instructions to produce new audio. This is not local processing. Do not submit confidential recordings or material you cannot share with an external processor. See Kie's privacy policy. Provider file-link availability is not a guarantee of deletion from provider systems.
Our source link expires after 24 hours. We attempt to remove our temporary source copy when processing finishes and retry cleanup when the result is accessed. We retain generated audio privately with your account for playback and download, along with the job status and credit debit or refund records. Contact us to remove stored arrangement files. Download a backup of results you want to keep. Public style demos use our own synthetic melody, not customer audio.
2. Analytics and advertising measurement
Umami is enabled by default to measure site use and completed purchases. You can turn it off using the controls below. A previously saved choice to disable analytics is respected on later visits. We do not save a personal choice until you select a setting. Change your choice using Analytics settings in the footer or the settings below. Umami is hosted at s.zenkit.io and does not set analytics cookies. Measurement URLs exclude query strings except registered public campaign tags. Measurements may include the page path and title, referrer information, browser and device details, and approximate location derived from network information. We disable advertising personalization in our separate Google Ads tag. We do not send audio, MIDI, filenames, payment-card details, email addresses, or form content to analytics.
When analytics is enabled, an arrangement failure notice can create a random recovery-flow reference. This lets us connect that notice with a later retry and its server-confirmed result. It is not an account ID and expires for attaching new retries after seven days. We send only this random reference, fixed step/error categories and whether the prepared audio changed to Umami—not account IDs, task IDs, filenames or audio hashes. Audio comparison uses hashes already held by the service; this measurement does not upload additional audio. Disabling analytics stops new recovery references and detailed recovery events.
If you choose Disable analytics, analytics storage is denied and accessible legacy Google Analytics and Clarity cookies are removed. Umami pageviews and feature events stop immediately. The separate Google Ads tag may send limited cookieless measurements for the remainder of an already-open page. Analytics scripts do not load on later pages while your choice remains denied. Your choice is saved in this browser.
We do not use heatmaps or session replay recording.
While analytics is enabled, we also measure feature use: choosing a file or demo, microphone recording, selecting a time range, conversion outcomes and cancellations, preview playback, cleanup settings, downloads, navigation, and checkout steps. These events include coarse duration ranges, file format, selected presets, time spent preparing the converter and transcribing audio, and fixed error categories. They never include the file itself, its name, musical notes, recorded sound, or raw error messages. Disabling analytics stops these detailed events; earlier actions are not replayed.
While analytics is enabled, we measure time spent at tool stages only while the page is in the foreground and the tool is visible, using 10-second and 30-second milestones. Time while analytics is disabled is not counted; disabling analytics clears the current stage timer. You may also choose fixed result feedback: Useful result, Wrong notes, Wrong timing, or Too slow. This optional feedback contains no free text and is sent only while analytics is allowed.
While analytics is enabled, we also load Google Ads measurement for our own advertising campaigns. This is separate from displaying advertisements on this website. Advertising storage, advertising user data, and personalization remain denied, including while analytics is enabled. The Google tag may send limited cookieless advertising measurements. Enhanced conversions and remarketing personalization are not enabled. Measurement URLs omit query strings and fragments.
While analytics is enabled, a purchase event is sent only after our payment service verifies a completed payment. It contains the paid amount, currency, and a one-way transaction identifier used to prevent duplicate counting. It does not contain your Stripe session, download token, email, audio, MIDI, or filename. Disabling analytics stops these purchase events. Advertising attribution may be incomplete without advertising consent.
3. Website advertising and your choices
We are preparing to use Google AdSense on eligible content pages. The AdSense ownership meta tag and ads.txt seller listing do not themselves display ads or set advertising cookies. This site does not currently load AdSense display-ad code. Allowing analytics does not give permission for personalized advertising.
If display advertising is enabled, third-party vendors, including Google and its partners, may place and read cookies or use web beacons, IP addresses, and other identifiers to deliver and measure ads. Where personalized advertising is permitted and you consent, Google and its partners may use advertising cookies to select ads based on visits to this and other websites or apps.
Before enabling personalized ads for visitors in the European Economic Area, the United Kingdom, or Switzerland, we will provide a separate advertising-consent message through a Google-certified consent management platform. The analytics controls on this page are not that advertising-consent platform. Ads will not be enabled until the applicable consent and disclosure requirements are met.
Read how Google uses information from sites and apps and manage personalization in Google My Ad Center. You can also use your browser's cookie controls. Disabling personalization does not necessarily remove all advertising or all measurement.
4. Payments
Stripe processes optional one-time payments. Stripe receives the information needed to complete checkout. SoundToMIDI receives payment status and limited transaction identifiers used to verify the purchase. We do not receive or store your full card number, audio, or MIDI through checkout.
5. Hosting and security logs
Cloudflare provides hosting, network delivery, and security. Like most infrastructure providers, it may process IP addresses, request details, and diagnostic information to deliver the site, prevent abuse, and maintain service reliability.
6. Service-provider policies
You can read the privacy information published by Google, Microsoft, Stripe, and Cloudflare. Their policies govern information they process as independent service providers.
7. Your choices and contact
You can disable analytics, clear this site’s browser data, or stop using the service. For privacy questions or requests, email contact@soundtomidi.com.