Privacy policy.

The short version

Silo Cast collects no data. None.

No analytics. No telemetry. No account. No usage metrics. No error beacons. No advertising IDs. No fingerprinting. No crash reports. Silo Systems receives nothing from Silo Cast about you, your device, or your recordings.

Multi-input recording, mixdown, transcription, transcript review, cuts and renders, punch-in playback, audiogram clips, episode-pack drafting and the publish folder run on your Mac by default. Silo Systems operates no server, hosted inference service, or Silo Cast account. The one path by which your content can leave your Mac is the optional Bring Your Own Key cloud writer described below, which is off until you enable it and sends data only to a provider you choose and pay for directly.

What we don't have, and therefore never see

Because Silo Cast has no server-side component, the following do not exist anywhere in our infrastructure (and our infrastructure consists of: nothing):

• Your name, email, phone, or address.
• Your IP address, device identifier, MAC address, or any other hardware fingerprint.
• The audio you record, the tracks Silo Cast produces, the transcripts, edit lists and episode packs it creates, the clips it renders, the voices you open from Silo Clone, or any file you export.
• The contents of your Documents, Downloads, Desktop, or any other folder.
• Session timing, feature usage, button clicks, or any other behavioural data.
• Crash reports. Silo Cast does not implement a crash-reporting SDK.

We never see any of this because none of it is ever sent to us. The app contacts no Silo Systems server.

Outbound traffic you initiate

A small number of classes of outbound network traffic can originate from your Mac while Silo Cast is running. None of them go to Silo Systems. All of them are user-initiated:

1. Mac App Store updates. When Apple ships a Silo Cast update, the Mac App Store delivers it. This traffic is between your Mac and Apple's servers, governed by Apple's privacy policy. Silo Cast is not involved.
2. Links you click. If you click an external link inside the app (for example, opening this privacy policy), your default browser handles the request. Silo Cast is not involved.
3. Optional local speech model download. If you choose the local transcription engine, Silo Cast downloads the Qwen3-ASR 0.6B model once (about 1 GB, Apache-2.0) from a pinned, checksum-verified Hugging Face revision, after showing you the source, size, and license and asking for consent. No audio, transcript, or identifier is sent with the request, and the model can be removed in Settings at any time. If you keep the built-in Apple engine, this download never happens.
4. Optional punch-in voice model download. If you want to speak replacement lines in a voice from Silo Clone, Silo Cast downloads the PocketTTS CoreML model (407,972,690 bytes, CC-BY-4.0) from a pinned, checksum-verified Hugging Face revision, only after you approve its source, license, attribution and size. No audio, transcript, voice, or identifier is sent with the request, and the model can be removed in Settings. If you never use punch-in, this download never happens.
5. The cloud writer, if you turn it on. Described in full in the next section.
6. Optional Bring Your Own Key requests. Only if you turn on Cloud inference in Settings, add your own API key, and confirm its consent dialog, each Episode Pack you generate (titles, show notes, and social posts) sends the episode title (your session name) and the full transcript text, with speaker labels, directly from your Mac to the provider you configured. Audio is never sent, and transcription stays on your Mac. Details are in the next section.

Optional Bring Your Own Key (off by default)

This is the one path by which your content can leave your Mac, and it stays closed until you open it. If you enable cloud inference in Settings and supply your own API key (OpenAI, Anthropic, Google Gemini, or OpenRouter), Silo Cast uses that provider only to draft episode packs: titles, show notes and social posts. For each pack you generate, it sends the episode title and the transcript text with its speaker labels over the internet to the provider you selected, under your own account. Your audio, voices, edit lists and exports are never sent, and transcription always stays on your Mac. What you send is then subject to that provider's privacy policy and data-retention practices, not ours.

Turning it on requires an explicit in-app confirmation, the episode-pack panel names the active cloud provider, a pack the provider wrote is labelled as cloud-written, and you can return to on-device drafting at any time. Nothing is ever sent to Silo Systems. We never see your content or your key, and we run no server, proxy, or relay in this path; traffic goes directly from your Mac to the provider you configured. Your key is stored only in the macOS Keychain on this Mac, never in a file, a database, or a log. You can also point Silo Cast at Ollama running on your own Mac, in which case the draft request goes only to that local server and stays on your Mac.

Permissions we request, and why

• Microphone. macOS gates all audio-input capture behind the Microphone permission. Silo Cast uses it to record your hosts and guests through the input devices you select, each on its own track. The audio stays on your Mac.
• Speech Recognition, only if you choose Apple Speech. Silo Cast asks Apple's engine to transcribe your recordings with on-device recognition required. The optional local engine does not use this permission.
• Files and folders you choose. Silo Cast reads or writes only what you pick in a macOS open or save panel: a .silovoice file from Silo Clone, episode artwork, or the folder an export goes to.
• Speech Recognition. If you transcribe with the built-in Apple engine, macOS asks for this permission. Silo Cast requires on-device recognition, so your recordings are transcribed on your Mac and are not sent to Apple or anyone else.

Silo Cast does not ask for Screen Recording, Camera, Contacts, Location, or Full Disk Access, and it has no system-audio capture of its own.

Personal voices from Silo Clone

Silo Cast does not record reference audio or create voices. You can open a .silovoice file that Silo Clone exported. Silo Cast reads only the file you choose, refuses one saved without Silo Clone's rights confirmation, converts up to fifteen seconds of its reference to a standard clip, and stores that clip in the app container. Deleting the voice in Settings removes Silo Cast's copy. Speaking in the voice happens on your Mac, and replacement takes carry no watermark.

On-device data you create

Your recordings live under ~/Library/Containers/com.silosystems.silocast/Data/Documents/SiloCastRecordings/. The library, transcripts, edit lists, episode packs, accepted punch-in takes, the optional speech model and your local preferences live under ~/Library/Containers/com.silosystems.silocast/Data/Library/Application Support/SiloCast/, and the optional voice model and voices you opened from Silo Clone under ~/Library/Containers/com.silosystems.silocast/Data/Library/Application Support/PersonalVoice/ (plus any folder you explicitly choose to export to). They are yours. We do not have access to them. Deleting Silo Cast removes the app; your work remains under its container until you delete it manually.

Children's privacy

Silo Cast collects no personal data from anyone, so nothing needs to be handled differently for users under 13. The same policy applies at every age: nothing collected.

Third-party services

Silo Cast uses these Apple frameworks on-device. They do not receive your episode from Silo Cast as a hosted service:

• Apple Speech: on-device transcription.
• Apple Foundation Models: on-device episode-pack drafting where Apple Intelligence is available.
• Core Audio and AVFoundation: local recording, mixing, previews and renders.

Changes

If we ever materially change how Silo Cast handles data, for example if a future version of the app ever begins to collect anything at all, 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 date at the top of this document reflects the current policy.

The current policy is: Silo Systems collects nothing.

Contact

Questions about this policy: admin@ohmslaw.net