Privacy policy.

The short version

Silo Meet 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. Silo Systems receives nothing from Silo Meet about you, your device, or your meetings.

By default, everything Silo Meet does runs on your device: Apple Speech for transcription, Apple Intelligence for written summaries where it is available, and a rule-based engine everywhere else. On a Mac you can also choose one of two optional speech models, downloaded once with your consent and then run entirely on the device. Silo Systems operates no server, hosted model, or Silo Meet account. The one way meeting content can leave your device is the optional Bring Your Own Key mode described below. It exists only in the Mac app, stays off until you turn it on, and sends data only to a provider you choose and pay for directly. The iPhone and iPad app has no cloud option and makes no network connections at all.

What we don't have, and therefore never see

Because Silo Meet 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 meetings and anything derived from them; session timing, feature usage, or behavioural data; crash reports. The app never contacts Silo Systems.

Meeting recording (explicit, never ambient)

Silo Meet records a meeting only when you start a session and stops when you end it. There is no ambient, continuous, or background capture. Importing a recording works the same way: Silo Meet reads only the file you pick.

• On the device. Capture and transcription always run on your device, and the audio is never sent anywhere. Summaries, decisions, action items, and chat answers also run on the device, unless on a Mac you have turned on the Bring Your Own Key mode described below.
• You start and stop it. A session begins when you start recording and ends when you stop or discard it. The app does not listen outside a session you started.
• Cited to the transcript. Each decision, action item, and recipe value links to the transcript line it came from, and a deterministic check drops any that the cited line does not back up.
• Stored locally. Transcripts and summaries live inside the app's sandboxed container on your device. Silo Meet does not sync or back them up to any server.
• Yours to delete. Erase any meeting, or all of them, at any time from inside the app.

If you never start a session or import a file, nothing is captured.

Outbound traffic you initiate

All outbound network traffic is started by you, and none of it goes to Silo Systems:

1. App Store updates. When a Silo Meet update ships, the App Store delivers it. That traffic is between your device and Apple's servers.
2. Links you click. If you open an external link from the app, your default browser handles the request.
3. Optional speech model download (Mac). If you choose a local speech model instead of Apple Speech, Silo Meet downloads it once from a pinned, checksum-verified revision on Hugging Face, after showing you its source, size, and license and asking for consent. The default model is about 1.02 GB; the higher-accuracy model is about 2.47 GB. No audio, transcript, or identifier is sent with the request, and a downloaded model can be removed in Settings. If you keep Apple Speech, no download happens.
4. Bring Your Own Key requests (Mac). Only if you turn it on, as described in the next section.

Optional Bring Your Own Key (Mac, off by default)

This is the one path by which meeting content can leave your Mac, and it stays closed until you open it. Silo Meet for iPhone and iPad has no cloud setting and no key entry. If you turn on cloud inference in Settings, confirm its consent notice, and supply your own API key (OpenAI, Anthropic, Google Gemini, or OpenRouter), two kinds of request go over the internet to the provider you selected, under your own account: for each meeting summarized while the mode is on, its transcript lines with speaker labels (up to about 24,000 characters) and its title; and for each question you ask in chat, the question and up to twelve matching transcript excerpts. Audio is never sent, and transcription always stays on the Mac. What you send is then subject to that provider's privacy policy and data-retention practices, not ours.

Silo Meet shows a cloud badge whenever a provider is active, and you can return to on-device processing at any time. Nothing is ever sent to Silo Systems. We never see your meetings 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 Meet at Ollama running on the same Mac, in which case the content stays on the Mac.

Permissions we request, and why

• Microphone. Record the meeting audio so it can be transcribed on the device.
• Speech Recognition. Transcribe recorded audio on the device with Apple Speech. Not needed if you use a downloaded speech model on a Mac.
• Screen & System Audio Recording (Mac). (optional) Capture the call audio playing through your Mac so the other side of a remote call is transcribed alongside your microphone. Silo Meet keeps the audio only; no screen images are stored or sent.
• Calendars. (optional) Only if you turn on "Name meetings from my calendar" in Settings: read the event happening when recording starts and use its title for the meeting. Nothing else from your calendar is kept, and it never leaves the device.

If you turn on Name meetings from my calendar in Settings, Silo Meet also asks for Calendar access. It then reads, on your device, the events from one hour before to one hour after the time you started recording, and uses the title of the event in progress to name the meeting. On the Mac, if you have also turned on the optional Bring Your Own Key mode described above, that meeting title is sent with the transcript to the provider you configured. Silo Meet does not request Camera, Contacts, Location, or Full Disk Access. If you grant nothing, it can read nothing.

On-device data you create

Your meetings and everything derived from them live in Silo Meet's operating-system-protected app container. On a Mac, that container is under ~/Library/Containers/com.silosystems.silomeet/Data/Library/Application Support/SiloMeet/; iPhone and iPad use the private app container managed by iOS or iPadOS. Files go elsewhere only when you export them. They are yours, and we do not have access to them.

While a recording is being finalized, Silo Meet may stage a recovery copy inside the app container. After a successful save it deletes that copy, or shows an explicit cleanup action if deletion fails. If finalization fails, you choose Retry or Discard; the app never uploads or silently abandons it.

Components that process your meeting

On the device, Silo Meet uses these components. None of them sends your meeting to Silo Systems:

• Apple Speech: on-device transcription.
• Apple Intelligence: on-device summaries on macOS 26, iOS 26, and iPadOS 26 where it is available.
• Rule-based engine: runs on the device when Apple Intelligence is unavailable.
• Optional downloaded speech model (Mac): runs on the device after the consented download above.

Children's privacy

Silo Meet is rated 4+. Because the app sends Silo Systems no personal data about any user, no special treatment is required for users under 13. The same policy applies regardless of age: the app sends us nothing.

Changes

If we ever materially change how Silo Meet handles data, we will publish an updated version of this page, announce the change prominently in the release notes, and require explicit consent in the app before any new collection begins. The current policy is: nothing reaches Silo Systems.

Contact

Questions about this policy: admin@ohmslaw.net