TuneMIDI Privacy Policy

How TuneMIDI handles audio, accounts, payments, private downloads, cookies and retention, and how to request access, correction or deletion.

Last updated: November 20, 2026.

This policy describes how TuneMIDI at tunemidi.com handles recordings, accounts, payments and service activity. It applies to our website and conversion service. For privacy questions or requests, contact cuishunbiao@gmail.com. See our Terms of use for conversion and purchase conditions.

Information you provide

When you register or sign in, we process your email address, account identifier and authentication information. Email and password registration uses a stored password hash rather than a readable password. If Google sign-in is available and you choose it, we receive the profile information needed to create or authenticate your account.

When you convert a recording, we process the uploaded file or submitted microphone recording, the selected time range, task settings and generated exports. Recordings may contain personal information, including identifiable voices. Only submit material you are entitled to process, and avoid sensitive or confidential recordings.

When you contact support, we receive your message, email address and any identifiers or attachments you choose to send. Please provide only the information needed to investigate your question.

How audio conversion works

Uploaded source files and generated exports are stored in private Cloudflare R2 storage. Our preprocessing service prepares your selected passage and sends that clip to Mirelo for note detection. We retrieve the result and make the export available through a private download response. We do not publish your uploads in the public examples gallery.

Mirelo processes clips under its own Privacy policy and API terms. Its rules for retention and training depend on the applicable API account arrangement. We do not promise that clips sent to Mirelo are excluded from training. Our file expiry does not determine retention in a provider's separate systems. Contact us before submitting material that requires specific confidentiality or training restrictions.

Why we use account and activity data

We use account and conversion records to authenticate you, deliver results, show recent history, allocate the free conversion and maintain your credit balance. The free allowance is attached to a verified account. Abuse checks also process hashed network, device and browser signals. These hashes reduce direct exposure of the underlying signals but are not a guarantee of anonymity.

Operational events record stages, results and durations so we can diagnose errors, measure reliability and protect the service. Application logs are designed to exclude audio, original filenames, raw device signals, passwords, secret keys and full payment links. Our hosting infrastructure also processes connection information required to serve requests and maintain security.

Payments and service providers

Waffo and its payment partners handle the payment information entered during checkout. TuneMIDI keeps the order identifiers, purchase details, payment status and credit ledger entries needed to deliver purchases and reconcile payments. Do not send card numbers or security codes to our support address. Waffo explains its own handling of payment data in its Privacy policy.

Cloudflare provides hosting, database, file storage and related infrastructure. Google processes authentication when you choose Google sign-in. Email delivery and support communications involve the providers used for those functions. Providers may process information in countries other than your own under their applicable terms and safeguards. Links to social sharing services take you to services whose own privacy policies apply.

Cookies and browser storage

We use cookies and browser storage for account sessions, security and the state needed to operate the converter. Device identifiers may also support abuse checks. You can remove cookies and stored site data in your browser settings, but doing so may sign you out or reset preferences. Browser permission is required to access your microphone; you can revoke that permission through browser settings.

All pages load Google Tag Manager to manage website tags. When configured, public pages also use Google Analytics or Microsoft Clarity to understand page visits and interactions. These tools may process browser and device information and use their own cookies or identifiers. Account, administration and billing return screens do not load those public-page analytics tools. The site also requests web fonts from Google Fonts, which receives connection information needed to serve those files.

Retention and security

TuneMIDI download access to source files and exports ends after 24 hours. Cleanup jobs delete expired stored objects; deletion may follow the expiry time when cleanup runs. Task status can remain after a file is removed. The account history displays the most recent 20 conversions, which is a display limit rather than a promise that older database records are deleted.

We retain account data while needed to provide your account, and retain financial, credit and audit records where necessary for reconciliation, disputes, security or legal obligations. These records have a different lifecycle from temporary audio files. Access controls and private storage help protect information, but no online system can guarantee absolute security.

Your choices and requests

Email cuishunbiao@gmail.com to ask about access, correction, deletion or account closure. Depending on your location and the applicable law, you may also have rights to receive a copy of your information, object to processing, restrict processing or complain to a data protection authority. We may need to verify account ownership before acting on a request.

Deletion of an account or recording does not necessarily remove records that must be retained for financial, security or legal reasons. We will explain relevant limits when responding. If you have a request about a clip already sent to a provider, include its job identifier so we can investigate the appropriate next step. We update this page when our processing practices change; the date above shows the latest revision.