Privacy policy.
The current policy is: nothing is collected.
The short version
Silo Skills 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, transmitted, or shared by Silo Skills about you, your Mac, or your files. What it does save stays on your Mac: snapshot copies of your agent files, a manifest of those copies, your folder-access bookmark and its app settings. Where each one lives is set out under On-device data below.
It has no network access at all
This is stronger than a promise not to transmit. Silo Skills ships with three sandbox entitlements and none of them is a networking entitlement:
com.apple.security.app-sandbox: required for Mac App Store distribution.com.apple.security.files.user-selected.read-write: read and write the folder you pick yourself.com.apple.security.files.bookmarks.app-scope: remember that choice across launches, so you are not asked again.
Without com.apple.security.network.client the App Sandbox refuses outbound connections, and without com.apple.security.network.server it cannot listen for inbound ones. There is no local runtime, no loopback service, and no bundled server. The app is a single native process that reads and writes files.
What it reads, and only when you say so
Until you grant access, Silo Skills shows a small built-in sample fleet. The sample is held in memory, nothing in it can be changed, and it never touches your files.
To see your own agents, you choose your home folder once through the standard macOS open panel. Any other folder is refused, because coding agents keep their configuration directly inside the home folder. macOS then hands the app a security-scoped bookmark for that folder. Inside it, Silo Skills reads only the folders and settings files where coding agents keep skills, rules, slash commands, plugins and Model Context Protocol server configurations, in order to list and compare them. It never opens your projects' source code. Reading happens on every scan; writing and deleting happen only when you start them, and editing or deleting an asset writes a snapshot of it first.
On-device data it creates
Snapshots are copies of the files a change replaced or deleted, kept with a list of where each one came from, in a folder in your home: ~/.silo-skills/backups. Reveal in Finder opens it, and Snapshots & Safety deletes any snapshot you no longer want.
The home-folder bookmark and a few preferences (the appearance setting, and which version last showed the rating request) live in the app sandbox at ~/Library/Containers/com.silosystems.siloskills/Data/. The list of assets is rebuilt from the agent folders on every scan and is not saved. All of it is yours; there is no copy anywhere else, because there is nowhere else. Removing the app leaves ~/.silo-skills in place, so delete that folder yourself if you want the snapshots gone.
Outbound traffic you initiate
There is none from the app. Three things can touch the network on your behalf and none of them involves Silo Skills sending anything:
- App Store updates. When Apple ships an update, the App Store delivers it. That traffic is between your Mac and Apple.
- Rating requests. After several completed changes in one session, the app may ask macOS to show Apple's standard rating request, at most once per version. The request and any rating you leave are handled by macOS and the App Store; the app learns neither.
- Links you click. A link opens in your default browser, which is a separate application.
Third-party components
Silo Skills uses Apple system frameworks only. There are no third-party SDKs, no analytics libraries, no crash reporters, and no bundled models.
Children's privacy
Silo Skills is rated 4+. Because no personal data is collected from any user, no special treatment is required for users under 13. The same policy applies regardless of age: nothing collected.
Changes
If we ever materially change how Silo Skills 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