MasterMusic is a local-first music player: your music library, playback settings and logs are stored on your device in %APPDATA%\MasterMusic. The app never uploads your music files.
Without registering an account, the app creates no personal data on our servers (except trial server verification and update checks, both optional and switchable — see Section 3).
Every network capability is listed individually in the app with its own switch; turning a switch off stops the corresponding network requests. This policy maps one-to-one to those switches.
2. Data We Collect and Store
2.1 On-device data (never uploaded)
Library cache, playlists, playback settings, themes and other local configuration;
Local behavior records (playback/search/playlist/Pomodoro events, used only by the in-app statistics page; the switch defaults to on, data stays on-device, and turning it off stops local recording entirely; membership references in logged-in events are sanitized on-device and never sent out);
Runtime logs (archived daily in the local logs folder, kept for 14 days; account identifiers in logs are sanitized).
2.2 Account information (provided at registration)
E-mail address, password (stored only as a hash on the server), username;
Membership tier and period records, redemption-code records (transaction and entitlement records are retained under fixed rules, even after account deletion — see Section 7).
2.3 Signed-in device information (automatic when signed in)
At registration, at sign-in, and on every launch while signed in, the app automatically reports to the shared server: device name, OS name and version, app version, and hardware overview (CPU model, logical core count, total memory);
The device fingerprint is a derived hash of the OS installation identifier (irreversible); it contains no hardware serial numbers, account names, or raw MAC/IP values;
Purpose: single-device session management (one computer signed in per account at a time) and administrative sign-in records (visible only to administrators, fingerprints shown sanitized);
Server-side sign-in records are kept for 180 days.
3. Outbound Channels and Switches (one-to-one with in-app "Settings → Privacy & Logs")
Switch
Default
What is sent
When off
Local behavior records
On
Nothing leaves the device (on-device only, see 2.1)
No local recording
Automatic update check
On
Current version number sent to the update feed to query and fetch new versions (no library content, no personal data)
All update checks (incl. manual) stop; zero requests
Listening-behavior upload (sign-in required)
Off
Aggregated statistics fields (event type/timestamps/numeric attributes); file paths, track names, search terms etc. are always HMAC-sanitized on-device before upload
Zero requests; events recorded before enabling are never uploaded
Upload lyrics to shared library (sign-in required)
On
Lyrics you curate plus track info (artist/title/album/duration), credited to your username; reviewed before publishing; monthly quota by tier (Bronze 5 / Gold 50 / Platinum unlimited); each upload also requires per-action confirmation
Zero uploads
Shared lyrics lookup (sign-in required)
On
Track artist/title/album/duration sent for lyrics matching
Zero lookups (no requests are made while signed out anyway)
Trial server verification (no sign-in required)
On
A derived hash of the trial device identifier (irreversible) and the trial start time, for trial management and duplicate-trial detection
Local marker only (weaker anti-abuse)
Microsoft in-app purchase entitlement lookup (sign-in required, Store build only)
On
The user ticket issued by the Microsoft Store, sent so the server can query your Microsoft Store entitlements (Gold/Platinum in-app products) on your behalf and merge them with membership benefits; the ticket is forwarded once, never stored, and the server keeps only the entitlement result
In-app purchase entitlements are not merged; membership is judged by server-side grants only
Sign-in-required switches are unavailable while signed out; once signed in, turning a switch off stops that capability immediately.
In the Microsoft Store build, the in-app update chain is fully managed by the Store: the app makes no update requests at all (both automatic and manual checks are short-circuited and the update entry is hidden).
4. Shared Lyrics Library (user-generated content)
Uploaded lyrics are manually reviewed before publishing; rejected content is never visible to other users;
You can delete lyrics you uploaded; on account deletion the system anonymizes the attribution (content is retained for other users);
To report content in the shared library that infringes your rights, contact support@MasterMusic.cn.
5. Trial Data
Trials are counted per device: only a derived hash of the OS installation identifier (irreversible) and the trial start/end times are collected — no hardware serial numbers, account names, or raw MAC/IP values;
One trial per computer: with "trial server verification" on, the server detects duplicate trials by the derived device hash and merges to the earliest start; when off, only the local marker applies;
When the trial ends without registration, the app pauses all features and guides the user through free registration (e-mail + verification code); registration and basic use remain free of charge.
6. Data Location: Store Build vs. Official Build
The Microsoft Store build and the official installer/portable build are functionally identical;
On most modern Windows systems (verified on Windows 11), AppData writes of desktop apps are not redirected: both distribution channels share the same data directory %APPDATA%\MasterMusic — library, settings and sign-in state carry over automatically, and switching channels requires no re-scan or re-login;
On managed environments with "App Virtualization" policies, the system may redirect the Store build's data into a package-private directory — in that case the two channels' data are independent, and uninstalling the Store build removes its data with the package. Check whether your library carries over on first launch of the Store build to determine which case applies to you.
7. Your Controls
All switches in Section 3 can be toggled at any time and take effect immediately;
Local behavior records can be cleared or exported as JSON at any time;
Uploaded server-side behavior data can be deleted with one click in the app;
Account deletion (Settings → Privacy & Logs → Delete Account): the server applies fixed rules — behavior data is deleted, attribution of uploaded lyrics is anonymized (content retained for other users), transaction and entitlement records are retained, all sessions are revoked; the account is then disabled and cannot be restored. Deletion ≠ deactivation: an administrator deactivation keeps data and is reversible; deletion follows the rules above and is irreversible. Your local library and on-device data are unaffected.
8. Policy Changes and Minors
When this policy changes, the "Last updated" date on this page changes accordingly; changes that add or remove outbound channels are announced together with the release notes of the corresponding app version;
This software does not knowingly collect personal information from children under 14; minors should use the app with a guardian who has read this policy.
9. Contact
E-mail: support@MasterMusic.cn (in the app: Settings → About → Developer button opens your mail client).