The short version
Ohms Score collects no data. None.
No analytics. No telemetry. No account. No personal data. No usage metrics. No error beacons. No advertising IDs. No fingerprinting. No crash reports. No data of any kind is collected, stored, transmitted, or shared by Ohms Score about you, your device, or your content.
Everything Ohms Score does runs entirely on your Mac, using its native app and locally stored model assets. There is no cloud component or remote service, and no Ohms Score account.
What we don't have, and therefore never see
Because Ohms Score has no server-side component, none of the following exists anywhere in our infrastructure (which consists of: nothing): your name, email, phone, or address; your IP address, device identifier, or any hardware fingerprint; your content and anything derived from it; session timing, feature usage, or behavioural data; crash reports. The app does not phone home, ever.
Outbound traffic you initiate
The only outbound network traffic, all user-initiated, and none of it to Ohms Score:
- App Store updates.When Apple ships a Ohms Score update, the App Store delivers it. This traffic is between your device and Apple's servers. Ohms Score is not involved.
- Links you click. If you click an external link inside the app, your default browser handles the request. Ohms Score is not involved.
Permissions we request, and why
- Files you choose. Read the audio files you open, and write only the MIDI files, chord charts, and stems you export, via the system file picker. Nothing else on disk is touched.
Ohms Score does not request protected resources beyond those listed above. System permission controls remain in effect at all times.
On-device data you create
Your content and everything derived from it live inside the macOS app container at ~/Library/Containers/com.silosystems.ohmsscore/Data/Library/Application Support/OhmsScore/. Any file you explicitly choose for an import or export remains under your control at the selected location. They are yours; we do not have access to them. Removing the Ohms Score app bundle may leave its macOS sandbox data in place; use any in-app delete or purge controls first, then macOS storage controls for remaining container data. Files in user-selected locations remain until you explicitly delete them.
Third-party components
Ohms Score uses the system frameworks, local model assets, or open-source components listed below. None receive any data about you from Ohms Score:
- Spleeter 4-stems on Core ML — bundled, on-device vocals/drums/bass/other separation feeding the transcription pipeline (no download) — runs locally on-device.
- Spotify basic-pitch note engine on Core ML — bundled, Apache-2.0 polyphonic note detection run per melodic stem — runs locally on-device.
- In-house vDSP analysis — STFT -> chromagram -> chord templates -> Viterbi chords, spectral-flux tempo/beat grid, Krumhansl-Schmuckler key, onset-based kick/snare/hi-hat drum detection — runs locally on-device.
- Spleeter 4-stems separation model (bundled in the app, MIT-licensed, runs on-device) (Bundled (no download)) — bundled — runs locally on-device, no download.
- basic-pitch note-detection model (bundled in the app, Apache-2.0, runs on-device) (Bundled (no download)) — bundled — runs locally on-device, no download.
Children's privacy
Ohms Score is rated 4+. Because no personal data is collected from any user, no special treatment is required for users under 13. Same policy applies regardless of age: nothing collected.
Changes
If we ever materially change how Ohms Score handles data, we will publish an updated version of this page, announce the change prominently in the release notes, and require explicit consent in-app before any new collection begins. The current policy is: nothing is collected.
Contact
Questions about this policy: admin@ohmslaw.net