Strumetra Studio
Your practice data stays on your device.
Strumetra Studio processes practice data locally in the web app, iPhone app, iPad app, and Mac App Store app. None of these versions requires an account or includes advertising, analytics, behavioral tracking, crash uploads, in-app purchases, or another payment flow.
Scores are parsed on your device and are not uploaded. The web, iPhone, and iPad apps read only a file you choose; the Mac App Store app receives read-only access only after you choose a file.
The native permission prompt may appear during first-run audio-device initialization, before you select a feature. Microphone audio is processed only while the audio-device list is refreshed or while the optional audio trigger is running; it stays local and is not recorded or transmitted.
Bluetooth scanning and connection begin only after you choose to connect an LED fretboard. LED commands are sent only to the directly connected hardware.
Installed apps keep their bundled app resources locally. The current web build also caches its bundled acoustic drum WAVs. User-selected scores are never added to an offline cache.
Data handled on your device
- Score files. In the web, iPhone, and iPad apps, a score selected through the file picker is read locally. The web app also accepts drag and drop. In the Mac App Store app, the sandbox opens only a file you explicitly choose and uses Apple security-scoped, user-selected read-only access. Strumetra Studio does not edit, overwrite, or delete the original score.
- Recent Files and bookmarks. The Mac App Store app may save the selected file's display name, path, and security-scoped bookmark in its sandboxed local app data. The bookmark lets the app request read-only access to that same file again from Recent Files; it is not sent to the developer.
- Practice settings. Tempo, display, audio-device preferences, chord progressions, drum settings, and lighting choices may be saved in browser site data or in the native app's local data.
- Bluetooth data. After you choose to connect an LED fretboard and a device, the app reads connection and battery status and sends fretboard-light commands only to that directly connected hardware. This data stays in the current local connection and is not sent to the developer.
- Microphone input. Microphone audio is processed only while the audio-device list is refreshed or while the optional audio trigger is running. A refresh opens a temporary system-default input stream only long enough to reveal device names and then closes it; the audio trigger analyzes sound attacks. Audio stays on the device and is not recorded, uploaded, transmitted, or played through the speakers.
- Audio-device names and permission. A browser, iPhone, or macOS may show the native microphone permission prompt during first-run audio-device initialization, before you select a feature. The permission prompt does not start continuous microphone processing. Device names are used only to show and remember your local selection.
- MIDI input. MIDI access is requested only after you select Connect MIDI Input in the Drum Trainer, always without SysEx. Incoming pad and e-drum notes are matched against the practice chart locally to show timing feedback; they stay on the device and are not recorded, uploaded, or transmitted. The iPhone and iPad apps use CoreMIDI after that same Connect action for class-compliant USB MIDI devices, already-available sources, and a local destination named Strumetra Studio that another app on the same device can send to. Bluetooth MIDI pairing uses the system picker and starts only after you select Bluetooth MIDI.
Network requests
The web app downloads its own code, music font, sound font, and bundled CC0 acoustic drum one-shots from the site hosting this page. Remote score links are disabled; scores can be opened only through the local file picker or drag and drop.
The iPhone app, iPad app, and submitted Mac App Store version 1.23.0 contain their application code, fonts, and sound font inside the installed app and generate Drum Machine sounds locally. The submitted Mac version does not contain the acoustic drum sample bank used by the current web build. Neither native app has an application server for scores, settings, audio analysis, or Bluetooth data.
None of these versions sets tracking cookies or sends analytics or crash reports. Like most websites, the web hosting provider may process standard access and security logs such as IP address, request time, and browser information. The hosting provider is responsible for its own logging and retention practices.
Offline storage and deletion
The service worker precaches the versioned application shell, legal pages, icons, Bravura font files, the bundled SONiVOX sound font, and the bundled acoustic drum WAV files. It does not add files you open to its cache. Old application-shell caches are deleted when a new version activates.
Web users can remove saved preferences and offline app resources by clearing site data for strumetra.app in the browser. This does not delete score files stored elsewhere on the device.
On iPhone, preferences remain in Strumetra Studio's local app data. Removing the app removes that local data but does not edit or delete the original score you selected.
In the Mac App Store app, preferences and Recent Files bookmarks remain inside the app's sandboxed local data. If a Recent File is unavailable, the app removes that entry after an unsuccessful reopen. Removing the Strumetra Studio local data container resets all saved preferences and Recent Files bookmarks without deleting the original score files; the support page provides the reset steps.
Permissions
Bluetooth and microphone access are optional. Bluetooth scanning and connection start only after you choose to connect an LED fretboard. The native microphone permission prompt may appear while the app initializes its audio-device list on first run; microphone audio is processed only while that list is refreshed or while the optional audio trigger is running. MIDI access is also optional, is requested only after you select Connect MIDI Input in the Drum Trainer, and never includes SysEx. On iPhone and iPad, that Connect action uses CoreMIDI for class-compliant USB MIDI, already-available sources, and the local Strumetra Studio destination; Bluetooth MIDI pairing uses the system picker and starts only after you select Bluetooth MIDI. Denying a permission leaves score viewing, chord practice, metronome, and drum-machine features available, except for the feature that requires that permission. Browser, iPhone, iPad, or macOS settings can revoke permission later.
MuseScore project files
MSCZ and MSCX projects are read locally by Strumetra Studio's built-in importer in the direct desktop, web, iPhone, and Mac App Store editions. The app does not launch MuseScore, start an external conversion process, or upload the selected project.
Children and sensitive information
The app is a music-practice utility and does not ask users to submit personal profiles or sensitive information. It is not designed to collect personal information from children.
Changes and questions
Material changes will be published on this page with a revised effective date. For privacy or support questions, contact support@strumetra.app. The support page provides compatibility details and diagnostic steps that do not require sharing a score or audio recording.