Effective 15 November 2026. This policy explains what Music Sheet Maker processes when you use its free music tools, save work locally, download a resource or contact the site. Music-file processing happens in your browser. Delivering the website and sending an email still involve the hosting and email services described below. There is no account to create or project-upload service.

What stays in your browser

The music sheet editor and supporting tools run on your device. The current application has no user-account system, project database or server endpoint for uploading music. Selecting a supported file lets the page read it locally; it does not publish the file or add it to a collection managed by Music Sheet Maker.

The application uses browser memory for the tool you have open and browser storage for the specific features described here. Local processing is different from a promise of complete device privacy. Someone with access to your browser profile, downloaded files or shared computer may be able to see work you leave there.

How imported MIDI and MusicXML files are handled

The MIDI converter reads note events and creates its simplified score in the browser. The MusicXML viewer and transposer read notation files locally and render their previews there. These workflows do not send the selected music file to a transcription service, cloud library or remote conversion database.

A selected file is not deleted from your computer by opening or closing a tool. The current preview is a working session, not an online backup. Download any converted or transposed result you want to keep before navigating away. If you later attach that file to an email, the email handling described below applies.

What the editor and note practice save locally

Editor autosave uses the browser-storage key msm-score-v1. It stores the current project, including its title, composer text, notes, rests and score settings. Changes replace this working copy. Starting a new score or opening another project can therefore replace the previous autosave. The site does not maintain a server copy or an account-based version history.

Note-reading practice uses msm-note-progress for correct and answered totals, from which the displayed accuracy is calculated. Reset progress clears that practice record. These local records belong to the current browser and site origin; they are not teacher reports, public profiles or synchronized data across devices.

How to remove browser data and protect a backup

Use your browser settings to remove this website from its stored site data. Clearing the relevant local storage removes the editor autosave and practice totals. Clearing cached images alone may not remove saved project data. Download a project backup first if you want to retain the score; saving and recovery help explains the difference between a working copy and an export.

Private browsing and storage restrictions can prevent saving or discard data when the private session ends. Browser cleanup, storage eviction and a different browser profile can also make a previous local score unavailable. There is no fixed local retention period controlled by the site. The current Firefox instructions linked below explain its site-data controls; other browsers provide their own settings.

Downloaded files and shared computers

PDF, SVG, MusicXML and project downloads are files under your control. Clearing browser site data does not remove them from your downloads folder, backups, cloud-synced folders or any place you have copied them. The same applies to ready-made resources from the printable library. Delete or move those copies using the controls of the device or storage service concerned.

On a school, library or other shared computer, check both local autosave and downloaded files before leaving. Avoid putting private personal information into a score title or composer field when it will be printed or shared. The tools do not need a class list, student email address or personal profile to work.

Website requests, hosting logs and tracking

Loading a page requires requests to the hosting service for pages, scripts, fonts and other assets. The host receives technical request information, which may include an IP address, requested address, time and browser information. Operational or security logs may exist under the hosting provider's practices. Those requests are separate from uploading the music file selected inside a tool.

No advertising, third-party analytics or marketing-tracking scripts are configured in this version. Fonts and application assets are served with the site. We do not state a fixed retention period for hosting logs because this page does not establish the provider's log settings or deletion schedule.

What happens when you email the site

Contact links use mailto:contact@musicsheetmaker.com to open your email application. Sending is your choice; the website does not submit a background contact form. Your email address, message and any attachments you send are handled by the email providers involved and are available for addressing your request. Use the contact guidance to prepare a useful report.

Send only the information needed to explain the question. A small original example is preferable to an entire private collection. We do not promise a fixed email-retention period or automatic deletion date. To ask about a message you sent, identify the approximate date and subject without sending further sensitive material unnecessarily.

Questions and changes to this policy

External references open services with their own privacy practices. The site's editorial policy explains how learning references are used. This policy should be updated when information handling changes, such as introducing an upload feature or analytics. For a privacy question, use the email link below and identify the feature or information you are asking about.