The short version
Ohms Explain 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 Explain about you, your device, or your content.
Everything Ohms Explain does runs entirely on your Mac, using its native app and the on-device frameworks listed below. There is no cloud component or remote service, and no Ohms Explain account.
What we don't have, and therefore never see
Because Ohms Explain 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 Explain:
- App Store updates.When Apple ships a Ohms Explain update, the App Store delivers it. This traffic is between your device and Apple's servers. Ohms Explain is not involved.
- Links you click. If you click an external link inside the app, your default browser handles the request. Ohms Explain is not involved.
Permissions we request, and why
- Folders you choose. Standard sandboxed file access; the app reads only what you explicitly select.
Ohms Explain 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.ohmsexplain/Data/Library/Application Support/com.silosystems.ohmsexplain/. Files you explicitly choose to import are read only for that user-initiated workflow. They are yours; we do not have access to them. Removing the Ohms Explain 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 Explain uses the system frameworks, local model assets, or open-source components listed below. None receive any data about you from Ohms Explain:
- apple-vision — runs locally on-device.
- apple-foundation-models — runs locally on-device.
Children's privacy
Ohms Explain 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 Explain 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
For non-private inquiries you can also open an issue at github.com/flowmar47/ohmsexplain/issues.