Privacy policy.
OhmsGrid is a single-user clip launcher for Mac and iPad that works on your device.
This policy describes what data the app handles, where it goes, and what it does not do.
Short version
- Silo Systems receives no data from OhmsGrid.
- No analytics SDK, no telemetry, no advertising identifiers, and no crash reporter that uploads beyond Apple's own opt-in platform diagnostics.
- No account, no sign-in, no cloud sync.
- Clip launching, mixing, arranging, sample analysis, export and clip generation all run on your Mac or iPad.
- OhmsGrid sends no prompts, lyrics, or audio to any AI provider. The only internet traffic the app itself starts is the optional clip-generation download, and only after you approve it.
- Optional Mac automation shares only read-only metadata for saved projects you select with the MCP client you configure. That client may forward it under its own provider's policies; Silo receives nothing.
Data the app handles
| Data | Where it lives | When it is transmitted |
|---|---|---|
| Audio you import | The OhmsGrid app container on your device | Never. Stays on your device. |
| Clips you generate | The OhmsGrid app container on your device | Never. |
| Projects | The app container, plus any project file you export to a location you choose | Project files are not transmitted. If you enable Mac project sharing, read-only metadata for the projects you select can be shared as disclosed below. |
| Sample-folder index (Mac) | The app container; folders you pick stay where they are | Never. |
| Lyrics engine setting (Mac version 1.9.1) | App preferences on your Mac | Never. OhmsGrid has no screen that writes or translates lyrics, so a provider picked there receives no text, prompts, or audio. |
| App preferences | Local app storage inside the app container | Never. |
| An API key you paste into the Cloud Inference (Bring Your Own Key) card in Settings (Mac version 1.9.1) | macOS Keychain; version 1.9.1 also hands it to OhmsGrid's local engine on the same Mac, which keeps it in memory only | Never leaves your Mac. OhmsGrid does not send it to any provider or to Silo, does not write it into project files, and does not log it. |
| Clip-generation model files | App-managed model storage inside the app container, or an external model folder you choose on Mac (read-only) | Downloaded from a pinned public revision only after you approve, checked before first use, then used on your device. |
On Mac the app container is ~/Library/Containers/com.ohmsgrid.app/Data/Library/Application Support/OhmsGrid/. On iPad it is the app's own Library/Application Support/OhmsGrid/ folder. Deleting OhmsGrid from an iPad removes it. On a Mac, removing the app can leave that folder in place, so use the in-app clear controls first, then macOS storage settings.
Local automation you enable
Local automation is available on macOS only. It is off by default and does not grant access until you explicitly enable it in the app, and it must be enabled again after OhmsGrid restarts. You choose between 1 and 50 saved projects to share. App access controls limit which requests the configured MCP client can make and which replies it receives. Disable local automation to stop further access; this does not retract information already shared.
Exactly three read-only tools are available: grid_capabilities, grid_projects_list, and grid_project_summary. Only saved projects you select are shared. Replies include project names and IDs, musical and timestamp metadata, and bounded layout summaries. These details can be sensitive. Audio, prompts, file paths and filenames, waveform data, and custom scene or column labels are excluded. The tools cannot edit projects, generate content, or manage models.
The configured external MCP client receives permitted replies and may process or forward them to its own provider under that provider's privacy and retention policies. A same-device connection to the app does not guarantee that the client's subsequent processing stays on your device. Silo does not receive this shared information.
Network access
OhmsGrid starts one kind of internet request: the model download below. Every other connection it makes stays on your device. Separately, a configured MCP client may forward shared information under its own provider's policies.
- Model downloads. When you approve the optional clip-generation download (about 10.1 GB for the Mac engine or 6.0 GB for the iPad engine), the app fetches the files from a pinned public revision on Hugging Face (
huggingface.coand its disclosed content-delivery hosts). The download is an anonymous HTTPS file transfer with no account, and each file is checked against a checksum pinned in the app before first use. Decline it and everything except clip generation keeps working. - Lyrics engine setting (Mac version 1.9.1). Settings in Mac version 1.9.1 includes a lyrics engine choice and an API key field, but the app has no screen that writes or translates lyrics. Picking a provider there makes no request to it. The key stays in your macOS Keychain and OhmsGrid's local engine on the same Mac, and no lyrics, prompts, audio, or key are sent to any provider. Silo operates no proxy and receives nothing. OhmsGrid does not use Ableton Link or any other local-network discovery.
The app also talks to its own local engine over a loopback connection that never leaves the device: 127.0.0.1 port 8802 on Mac and [::1] on a port chosen at launch on iPad, each protected by a fresh token every launch. It accepts no connections from other devices.
OhmsGrid does not call home, ping a license server, or check for updates. App updates flow through the App Store like any other app.
Microphone
OhmsGrid has no recording feature and never records audio. One Settings control, Reveal device names, may ask for microphone permission because the system shows audio output device names only after that permission is granted. OhmsGrid closes the input as soon as permission is granted and keeps nothing. Deny it and the rest of the app works unchanged.
Apple App Tracking Transparency
OhmsGrid does not engage in tracking as Apple defines it. The PrivacyInfo.xcprivacy manifest declares no tracking, no tracking domains and no collected data types. The required-reason APIs it declares are file timestamps (reason C617.1) and system boot time (reason 35F9.1), both used on the device only.
Children
OhmsGrid does not knowingly collect data about anyone, including children. Optional local automation clients remain subject to their providers' policies, including any age requirements.
Changes to this policy
If we materially change how the app handles data, we will update this page and the release notes, and ask for your consent in the app before any new sharing begins.
Contact
Email admin@ohmslaw.net.