PRIVACY

Privacy policy

This policy describes the current public version of mp3tomidiflow.

Your audio stays in your browser

Selecting or dropping a file lets the converter read that file on your device. The converter does not upload your audio to our server or an external conversion API. Audio decoding, note detection, and MIDI generation run in your browser. The download is generated locally, not retrieved from a server holding your recording.

Temporary processing and downloads

The converter holds the selected file and conversion result in the current page's memory. It does not create an account or save a conversion history. Reloading or closing the page clears its current conversion state. A MIDI file you download remains wherever your browser saves it; closing the page does not delete that downloaded file.

Website requests are separate from audio processing

Your browser requests the page, scripts, styles, and, when needed, model and decoder files from this website. Those requests do not contain the selected audio. Our hosting provider may process technical request information such as IP addresses, requested URLs and timestamps to serve the website. We make no claim of zero server logs or a fixed retention period here.

Optional statistics and your choice

Statistics are off until you explicitly allow them using the statistics controls on a page. No Google statistics script is loaded while you have not allowed statistics or have refused. The converter and MIDI download work without statistics. You can use No thanks / Withdraw at any time without reloading or interrupting conversion. This stops future statistics from this page and applies to other open pages when they receive the updated preference; it does not erase data already sent.

When allowed, Google Analytics 4 records page visits, conversion starts, successes, broad failure categories and the first deliberate MIDI download click per result. Our statistics omit page query strings, fragments and referral/campaign values. These custom events do not include audio, filenames, MIDI contents, raw errors or account identifiers. Google still uses standard analytics cookies and client/session identifiers and receives normal browser/device and network information; these statistics are not fully anonymous. Advertising signals are disabled in this configuration.

We store only a versioned allowed/denied choice in local storage, not a new visitor identifier. Reloading respects it; clearing site storage resets it. Analytics cookies created while you allowed statistics may remain after withdrawal. Requests already dispatched before withdrawal cannot be recalled. When statistics are withdrawn or a page is left, the statistics runtime may still try to flush queued events; a browser policy applied only to that runtime blocks new network sends before it is removed. This does not alter the converter's network access. If storage or the tag is unavailable, conversion still works and statistics may be unavailable. How Google uses information.

Future third-party advertising

We plan to display third-party advertisements in a future version. No advertising provider has been integrated into this version. Depending on the provider and configuration, advertisements may use cookies or similar technologies and process technical or advertising-related data. Before ads are enabled, this policy will need to identify the provider, actual data practices, and available privacy choices. This policy does not mean that advertising is already running or that you have consented to it.

Contact and policy changes

The intended privacy contact is contact@mp3tomidiflow.com. Email routing has not yet been confirmed, so this address is not currently a verified working contact channel. Do not send private recordings or sensitive information to it. See the contact page for details.

This policy should be reviewed when hosting, advertising, analytics, or file handling changes. The description above is limited to the current version.