Effective September 25, 2026

Privacy policy

Core editing happens locally. We do not receive the MIDI file you open unless you explicitly save it to Creator Cloud.

How Google uses partner site dataManage personalized ads

Information we process

For local tools, the browser processes MIDI bytes on your device. Product analytics record page and workflow events without filenames, MIDI content, or email addresses.

After your first edit, the browser keeps one IndexedDB recovery copy on this device. A newer draft replaces it, and you can clear it from the editor at any time.

Pageview counts visits independently through click.pageview.click. Google Analytics is loaded only when a public measurement ID is configured and you explicitly allow it; declining does not limit the editor.

For Creator Cloud, we process your email address, session records, saved MIDI projects, version history, entitlement status, and limited service logs needed to operate the account.

If you choose Google sign-in or Google One Tap, Google Identity Services provides a signed identity token. EditMIDI stores the Google account identifier needed to reconnect that identity to your account, but does not retain Google access or refresh tokens. Short-lived challenge cookies and database records prevent forged or replayed responses; after you dismiss One Tap, this browser stores the dismissal time for up to six hours before prompting again.

When you explicitly generate an AI MIDI result, OpenRouter receives the selected note values and your optional musical direction. It does not receive your account email or unselected MIDI events from EditMIDI. Provider routing requires structured output and disables provider data collection where supported.

SeeAPI receives your written musical direction and the generated explanation for content review before delivery. It does not receive MIDI files, selected note values, account email or payment details from EditMIDI. Review outcomes are stored with a content fingerprint so an unchanged result does not need repeated review.

Advertising cookies and your choices

The site loads Google AdSense resources to support advertising. Third-party vendors, including Google, may place or read cookies, use web beacons or IP addresses, and receive browser, device, consent, and ad-delivery signals when an ad request is made.

Google and its advertising partners may use advertising cookies to serve ads based on your visits to EditMIDI and other websites. You can manage or opt out of personalized advertising through Google Ads Settings. Advertising does not receive MIDI filenames or MIDI content from EditMIDI product events.

Service providers and retention

Cloudflare provides hosting and database infrastructure and measures page-performance timings through its Web Analytics beacon without cookies or local storage. ZeptoMail delivers sign-in codes and service email. Our payment service processes checkout and returns entitlement status; EditMIDI does not store full card details.

We retain account and project information while the account is active and as reasonably needed for security, legal, and billing obligations. Ask contact@editmidi.com to access or delete account data.