The short version
Silo Key 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 Silo Key about you, your device, or your content.
Everything Silo Key does runs entirely on the Apple device where you use it, using its native app and the on-device frameworks listed below. There is no cloud component or remote service, and no Silo Key account.
What we don't have, and therefore never see
Because Silo Key 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 Silo Key:
- App Store updates.When Apple ships a Silo Key update, the App Store delivers it. This traffic is between your device and Apple's servers. Silo Key is not involved.
- Links you click. If you click an external link inside the app, your default browser handles the request. Silo Key is not involved.
Permissions we request, and why
- Audio library folders. Read audio files to analyze musical key and write ID3 metadata tags.
Silo Key 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 declared on-device data location ~/Library/Containers/com.silosystems.silokey/Data/Library/Application Support/SiloKey/ and the app sandbox used by each platform. Files you explicitly choose to import are read only for that user-initiated workflow, and durable exports live in the folder or Files location you explicitly choose. They are yours; we do not have access to them. On iPhone or iPad, deleting Silo Key (rather than offloading it) removes its app-sandbox data; on Mac, removing the app bundle may leave sandbox data in place, so use any in-app delete or purge controls first, then macOS storage controls. Durable exports in user-selected locations remain until you delete them explicitly.
Third-party components
Silo Key uses the system frameworks, local model assets, or open-source components listed below. None receive any data about you from Silo Key:
- silo-audio-mir — runs locally on-device.
Children's privacy
Silo Key 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 Silo Key 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/silo-key/issues.