Local MIDI files
When you open a .mid or .midi file in the online MIDI editor, supported editing, playback and conversion work happens in your browser. Miditor does not automatically transmit the contents of that local file to our servers.
Privacy / Plain language
Privacy Policy
Miditor is designed around a simple privacy principle: a MIDI file you open for editing should stay on your device unless you deliberately choose a separate sharing feature.
Last updated:
01 — Overview
What this policy covers
This Privacy Policy explains what information Miditor processes when you use miditor.com, the browser-based MIDI editor, player, converter, and public song pages. It distinguishes files handled locally on your device from information that may reach our hosting or supporting services.
By using Miditor, you acknowledge the practices described here. If you do not agree, you may stop using the website and clear its site data from your browser. For the rules governing use of the service, read our Terms of Service.
02 — Data
Information Miditor handles
Browser storage
Miditor may use browser storage, caches and similar on-device technology to remember preferences, improve loading, support offline behavior and retain recovery data. This information remains associated with your browser until you clear it.
Public cloud songs
The public cloud song library contains material that was deliberately published. Public song titles, musical data and related metadata may be read, played, downloaded and shared by visitors.
Technical request data
Hosting, security, font, analytics or advertising providers may receive ordinary request information such as an IP address, browser type, device type, referring page, requested URL and approximate time. Providers process that data under their own terms and retention practices.
03 — Use
Why information is used
Information may be used to deliver requested pages, protect the service from abuse, diagnose failures, understand aggregate usage and improve Miditor. We do not claim ownership of MIDI files you open locally. We do not sell the contents of those local files because Miditor does not receive them through the normal editor workflow.
If advertising or analytics is enabled, cookies or comparable identifiers may be used to measure traffic, limit fraud or personalize experiences where permitted. Your browser may provide controls to block or delete these technologies. Blocking them may affect optional features but should not prevent basic local MIDI editing.
04 — Choices
Your choices and requests
You can avoid publishing songs, clear site data, disable optional browser permissions and use private browsing controls. Requests concerning information held by a third-party provider may also need to be directed to that provider.
Privacy rules vary by location. If you want to ask what information may be associated with a specific interaction, request correction or deletion, or raise a privacy concern, use the options on our Contact Miditor page. We may need enough context to locate the relevant record and verify that a request is legitimate.
We may update this policy when the product, providers or legal requirements change. The date at the top identifies the latest version. Material changes will be reflected on this page.
Quick answers
Frequently asked questions
Does Miditor upload the MIDI files I open?
No. Files opened in the editor are parsed, played and edited in your browser. They are not uploaded to Miditor unless a separate feature clearly asks you to publish or share something.
Can I clear data stored by Miditor?
Yes. You can remove Miditor site data through your browser settings. Clearing it may remove preferences, cached resources and locally saved recovery data.
Does this policy cover public cloud songs?
Yes. Public songs are intentionally published content and are separate from MIDI files you open locally in the editor.