Privacy policy.

The short version

Silo Systems / Ohm collects no data about you. There is no OhmsPolyglot account, no analytics, no telemetry, no crash reporting to us, and no Ohm server. Your string catalogs never reach us.

Opening, editing, checking, importing and exporting never use the network. They work on the files you choose, on this Mac.

This is not a Silo “nothing leaves the device” app. Translate Missing is optional. When you run it and confirm the count it shows, the entries it will fill are sent from your Mac to the endpoint you set in Settings: the provider whose API key you pasted, over HTTPS, or a model server on this Mac over loopback. Silo Systems is not a party to that request, operates no proxy, and receives no copy. What a provider does with the text is governed by its privacy policy.

What we don't have, and therefore never see

Because OhmsPolyglot has no server-side component, none of the following exists in our infrastructure: your name or email; your IP address or device identifier; your catalogs, translations, glossaries, or export files; usage or behavioural data. The app does not phone home.

What reaches the endpoint you configure

Nothing is sent until you run Translate Missing and confirm the number of entries and the destination it shows you. Then, for each entry it fills, the request carries:

1. The key name, its source text and its developer comment for each entry being filled. A string whose first translation fails the app's check is sent once more.
2. Your glossary terms, so names you listed in Settings are kept verbatim.
3. The target language, the app's instructions for keeping placeholders intact, and the model name.
4. Your API key for that provider, to authenticate the request. A model server on this Mac uses no key.
5. Ordinary request details: your Mac's IP address and the app's name. Requests to a routing provider can also carry attribution headers naming OhmsPolyglot and ohmslaw.net.

Beyond fixed request settings and what any HTTPS connection reveals, nothing else is sent. It goes directly from your Mac to the endpoint you configured, and each provider row in Settings names the host its requests go to. A model server on this Mac is reached at 127.0.0.1:11434 and that traffic never leaves the machine. With no API key saved, translation can only reach that local server; if none is running, the run stops and nothing is sent. Find Local Models in Settings asks the same loopback server for its list of installed models and nothing else.

A provider that has been retired is no longer offered. If a key for one remains from an earlier version, Settings shows it only so you can delete it.

Where your keys live

API keys are stored in the macOS Keychain, scoped to com.silosystems.ohmspolyglot. They are never written to catalogs, exports, or preferences, and they are never transmitted to Silo Systems. Deleting a key in Settings removes its Keychain item.

Other outbound traffic you initiate

1. App Store updates. Apple delivers them. OhmsPolyglot is not involved.
2. Links you click. Your default browser handles the request.

Permissions we request, and why

• Files you choose. Read and write .xcstrings catalogs, legacy .strings and .stringsdict files, and export files only through the system open and save panels. An app-scoped bookmark lets the app reopen the last catalog you chose. Nothing else on disk is touched.
• Outgoing network. Used solely to reach the endpoint you configure for Translate, or the model server on loopback. The app accepts no incoming connections.

On-device data you create

The app's preferences, inside the sandbox container for com.silosystems.ohmspolyglot, hold your glossary terms, the chosen translation provider and any model names you typed, each catalog's language choices (keyed by file path), a bookmark to the last catalog you opened, and two counters that decide when to show Apple's rating prompt. Catalogs remain where you opened them. Removing the app may leave its sandbox container; use macOS storage controls to clear it.

Children's privacy

Silo Systems collects no personal data from any user. Connecting a third-party AI provider is an adult decision governed by that provider's own terms and minimum-age rules.

Changes

If we ever materially change how OhmsPolyglot handles data, we will publish an updated version of this page. The current policy is: Silo Systems collects nothing; translation entries go only to the endpoint you configure.

Contact

Questions about this policy: admin@ohmslaw.net