Privacy policy.

The short version

Silo Bench does not send Silo Systems your examples, outputs, scores, reviews or your API keys. No analytics, telemetry, advertising IDs or crash reports are sent to Silo. Inputs you send through an optional connection go directly to the service you configured, and an app you connect receives only what is described under “Apps you connect” below; other network traffic is disclosed below.

Every project starts offline. An offline project makes no model requests: importing outputs, scoring, comparing and reviewing all happen on your Mac, and scoring runs in a separate process that has no network access. If you turn on connected mode for a project, confirm its notice and add a connection, Silo Bench sends the inputs you selected for a run to that service, under your own account and key, as described below. Silo does not provide cloud processing for your content, and there is no Silo Bench account.

What the app never sends

Silo does not receive the content you work with in Silo Bench, your model requests or replies, or your API keys. Requests through a connection go from your Mac to the service you configured, never through Silo. That service receives what you send and ordinary request metadata, such as your IP address, under its own policies. If you contact support by email, we receive your email address and whatever you choose to send.

Apps you connect

App connections let an app or agent on your Mac that speaks the Model Context Protocol (MCP) take a project's evaluations. They are off by default and grant nothing until you turn them on under Connections, and a project shares nothing while it is offline. Turn app connections off, or switch the project back to offline, to stop further access; this does not retract what was already shared.

Five tools are available: list_evaluations, start_run, next_case, submit_output and run_results. They work only on the project open in the app, and only while that project is in connected mode. Replies include the project name, evaluation names and sizes, each case's prompt, and the computed scores for runs the client started. Prompts can be sensitive. Expected answers, reference files and attached input files are excluded. This automation is not read-only: a client can add a run that holds its own answers, which the app stores and scores on your Mac. It cannot change or delete evaluations, other runs, connections or settings, and nothing a client sends is run.

The app you connect receives those replies and may process or forward them to its own provider under that provider's privacy and retention policies. A connection on the same Mac does not guarantee that the app's own processing stays on your Mac. No network port is opened, and Silo does not receive this information.

Outbound network traffic

The connections associated with Silo Bench are described below. At launch, Silo Bench asks Apple's StoreKit to confirm your App Store purchase. Separately, Apple's operating system and App Store may contact Apple automatically, for example to deliver updates.

1. Optional connections you configure. This is off unless you turn on connected mode for a project in Connections, confirm the notice, and add a connection. Each project decides separately, and you can switch it back to offline at any time. When it is on, a run sends the inputs you selected (prompts, references included in prompts, and other request inputs) to the model provider or endpoint you configured, using your own account and key. Before a run, each connection must pass a capability check, which sends one small test request of Silo Bench's own to that service. Your key is stored only in the system Keychain on your Mac, and Silo never receives it. The service receives the inputs and ordinary web-request metadata, including your source IP address, and handles both under its own privacy policy and data-retention practices. A connection may point at a model server on your own Mac; such a server can itself forward requests elsewhere, which is up to how you set it up. The traffic never goes through Silo, and Silo Bench keeps working offline with connected mode off.
2. App Store updates. When Apple ships a Silo Bench update, the App Store delivers it. This traffic is between your device and Apple's servers. Silo Bench is not involved.
3. Links you click. If you click an external link inside the app, your default browser handles the request. Silo Bench is not involved.

Permissions we request, and why

• Files and folders you choose. Copy selected examples and outputs into project storage and export reports.

Silo Bench does not request protected resources beyond those listed above. System permission controls remain in effect at all times.

On-device data you create

Your projects, evaluations, outputs, scores and reviews live inside Silo Bench's macOS app container on your Mac. 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. Removing the Silo Bench 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

The scorer uses open-source libraries bundled with the app (JiWER, mir_eval, NumPy, SciPy and trimesh). They run on your Mac, inside the scoring process that has no network access. A service you connect receives the inputs sent to it and ordinary request metadata, including your IP address, and handles them under its own privacy policy and retention practices.

Children's privacy

Connections and app connections are optional and off by default. A service or app you connect receives what you send and applies its own data practices and age requirements.

Changes

If we materially change how Silo Bench handles data, we will update this policy and the release notes, and require explicit in-app consent before any new collection begins. A service you connect controls its own privacy policy and retention practices.

Contact

Questions about this policy: admin@ohmslaw.net