Score Sketch — Privacy Policy
Last updated: 2026-10-17
This privacy policy applies to the mobile app "Score Sketch" for Android:
- Google Play: package com.simonj.notation, developer "Global Utility App Maker"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name: Global Utility App Maker).
Contact: wkdrb2100@gmail.com
OVERVIEW
Score Sketch does not require an account, and we do not sell personal information. You write music notation, play it back with a synthesized piano-style tone, and export scores as MusicXML, MIDI or PNG files. Your scores are kept in the app's storage on your device. The app also uses Google services and an advertising mediation partner for analytics, crash reporting, remote configuration, and advertising.
INFORMATION STORED ON YOUR DEVICE
For each score the app keeps its title and composer, tempo, staff layout, measures (notes, rests, key and time signatures), a revision number, creation and update times, and its undo and redo history (up to 200 steps), so notes you change or delete can remain in this history until it is replaced. The app keeps a list of IDs of deleted scores so that restoring an older backup does not bring them back; this list is kept without a limit. There is no fixed limit on the number of scores. If a saved score cannot be read, the app leaves it untouched and shows how many could not be read.
The app may also store basic operating information such as your note-name system and tap-audition setting, a count of app sessions and whether a review request was made, cached advertising settings and a cached More Apps list. Playback audio and short note tones are generated on your device and kept in the app's cache.
The developer does not run a server that receives your scores. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore, but it does not upload your scores or score titles. When you open the developer's other apps in Settings, app icons are loaded from the web addresses in that list.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches, screen views and app sessions; creating a score (layout, time signature and a key range); placing notes (duration and whether it is a chord), undo and redo (a depth range), transposition (interval and respelling), automatic re-barring; playback start, stop and preparation time (ranges); changes to layout, input method, time and key signature, note names and tap audition; export and backup results (format and a file-size range) and shares; cancelled steps; save errors; review requests; ad revenue events (ad format, value, currency and precision); app version, device type, and app-instance identifiers. These events do not include score titles or note content.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob. A banner may appear at the bottom of the Manuscripts list, and an ad may appear in the exit dialog. Full-screen ads may appear when the app opens or returns to the foreground, and occasionally after you finish an export or a backup (never after your first one in a session). The app does not start a full-screen ad while a score is open in the editor. AdMob may also request ads from the InMobi mediation network. Google and InMobi may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location even though the app has no location permission.
PERMISSIONS AND ADVERTISING CHOICES
The app does not request camera, microphone, location, contacts, photos and videos, music and audio files, Bluetooth, health data, or notification permissions. It uses internet access and the Android advertising ID permission for the services above, and vibration for short haptic feedback. When you tap "Restore from backup", the Android file picker opens and only the file you choose is given to the app; the picker may leave a temporary copy in the app's cache.
When the app starts, Google's consent message (UMP) is checked first. Where consent is required (for example in the EEA and UK), personalized advertising stays off unless your choice allows it, and if the consent result does not allow ad requests, or the consent check has not completed, the app does not request ads. If the consent message cannot be loaded, the app still requests non-personalized ads, personalized advertising stays off, and "Advertising privacy choices" is not shown until the app is started again. Where Google requires it, the Settings sheet shows "Advertising privacy choices", which reopens the consent message so you can change your advertising choice. The app works whatever you choose.
STORAGE AND YOUR CONTROL
You can undo and redo edits in the editor, and delete a score from the Manuscripts list (after a confirmation). Deleting a score removes its saved file, including its undo history, and its playback audio in the app's cache; its ID stays in the deleted-ID list. "Undo" in the message that follows brings the score back as a copy with a new ID. You can also clear the app's data in Android settings or delete the app. Local data may be included in a Google or device backup depending on your backup settings; uninstalling normally removes the active copy but may not remove an older backup.
Exported MusicXML, MIDI and PNG files and "Back up library" files (your readable scores with their undo history, and the deleted-ID list) are written to the app's cache, and "Share" sends them through the system share sheet to a destination you choose. When the app starts, it removes these cache files once they are more than 24 hours old; files whose age it cannot check may be kept. The app does not delete copies you shared elsewhere. Restoring a backup adds scores or replaces them with newer versions from the file, and removes scores that the backup's deleted-ID list covers.
Because we do not receive your scores, we cannot delete them for you; the controls above remove them from the app. For questions about data processed by Google or InMobi, or to ask us for help with a privacy request, contact us at the address below.
Data processed by third parties is retained according to their service settings and policies. We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy.
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
- InMobi Privacy Policy: https://www.inmobi.com/privacy-policy
SECURITY
Your scores and cache files are kept in the app's private storage on your device, which the operating system protects from other apps; they are not separately encrypted by the app, so protect your device with a screen lock. Apart from the limited analytics events described above, the app does not upload your saved data. Communication between the app and Google services and the ad mediation partner uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app collects to what is described in this policy.
IMPORTANT NOTICE
Playback uses a synthesized tone, not a recorded instrument, and exported files may look or sound different in other notation programs; check them before you rely on them. Only write out and share music you have the right to use.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Kyu-Hee Jang (Google Play developer: Global Utility App Maker)
Email: wkdrb2100@gmail.com