Privacy policy.

The short version

Silo Clone 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, stored, transmitted, or shared by Silo Clone about you, your device, or your content.

Everything Silo Clone does runs on the Mac where you use it: separating a voice from backing music, levelling it, transcribing the reference, building the voice, and speaking typed text in it. There is no cloud inference, no server component, and no Silo Clone account.

Voices and recordings stay here

The audio you import, the isolated vocals the app separates from it, the reference clips you trim, the voices you create, and every take you generate are written to disk on your Mac. Silo Clone has no mechanism to send them anywhere. A take leaves the app only when you share it from its share button, to a destination you pick. A voice leaves the app only when you choose Export Voice and pick where the file is saved.

What we don't have, and therefore never see

Because Silo Clone 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 audio, your voices, your transcripts, or anything derived from them; session timing, feature usage, or behavioural data; crash reports. The app does not phone home, ever.

Outbound traffic you initiate

The only outbound network traffic, all user-initiated, and none of it to Silo Clone:

1. Engine downloads. Silo Clone downloads its voice engine from Hugging Face and its vocal isolation model from GitHub, about 3.3 GB in total, only when you press Download Engines in the window or Download All in Settings. Both downloads are anonymous: no token, account, or registration is required. Once the files are on disk, building voices and speaking with them works fully offline.
2. A media link you paste. If you paste a direct audio or video file URL, the app fetches that file so it can be imported. It goes only to the address you typed. Streaming playlists are refused before anything is fetched, and a link that does not turn out to be playable audio or video is discarded. The app does not download from third-party media services.
3. Speech recognition assets from Apple. The first time you press Auto-transcribe in a language your Mac does not yet have an on-device speech model for, macOS may install that model from Apple. That exchange is between your Mac and Apple, and your audio is not part of it.
4. App Store updates. When Apple ships a Silo Clone update, the App Store delivers it. That traffic is between your device and Apple. Silo Clone is not involved.
5. Links you click. If you click an external link inside the app, your default browser handles the request. Silo Clone is not involved.

Permissions we request, and why

• Microphone. Only to record a reference when you press Start Recording. Nothing is captured otherwise, and recordings stay on your Mac.
• Speech recognition. To transcribe a reference on-device, so High fidelity mode knows what was said. Apple's on-device speech models are used; audio is not sent to a server for this.
• Files you select. To import the audio or video you choose, to save exported voices and takes where you ask, and to use an engine download location you pick in Settings.

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

On-device data you create

Sources, isolated vocals, voices, and generated takes live inside the app's container at ~/Library/Containers/com.silosystems.siloclone/Data/Library/Application Support/SiloClone/. Engine files live there too unless you choose another folder in Settings. Files you import are read only for the workflow you started, and exports live wherever you save them. They are yours; we have no access to them. Deleting a voice in the Voice Library removes the voice, its trimmed reference and every take from your Mac. The recording or import it was built from, and any isolated vocal made from it, stay in the Studio until you delete them there. Removing the app bundle may leave sandbox data in place, so delete voices and their source recordings in-app first, and remove the models folder shown in Settings if you want the engine files gone too.

Voice files you export

Silo Clone has no shared container and no connection to any other app. When you choose Export Voice, it writes a .silovoice file to the location you pick. That file holds the voice's reference recording and its transcript, the voice's name and when it was made, where the reference came from (the file name, the link you pasted, or that it was recorded in the app), and your consent attestation. Silo Read, Silo Cast and Silo Fable can open it to speak in that voice. Where the file goes after you save it is up to you; Silo Clone does not send it anywhere.

Consent and provenance

Silo Clone requires you to affirm, at first launch and again for every voice you create, that the voice is your own or that you have explicit permission to clone it. That attestation is recorded alongside the voice on your Mac and written into every voice file you export. This record exists for your accountability, not ours: it is never transmitted to us or to anyone else.

Third-party components

Silo Clone uses the system frameworks, local model assets, and open-source components listed below. None receive any data about you from Silo Clone:

• Qwen3-TTS (mlx-community, Apache-2.0): runs locally on-device.
• HTDemucs v4 (facebookresearch/demucs, MIT): converted to Core ML, runs locally on-device.
• MLX and mlx-swift: local inference on Apple silicon.
• ZIPFoundation (MIT): unpacks a downloaded model archive.
• Apple Speech, AVFoundation, Core ML, Core Audio: system frameworks, used on-device.

Children

Silo Clone is not directed at children and collects nothing from anyone, including children.

Changes

If this policy ever changes, the effective date at the top changes with it. A change that introduced any data collection would also require a new App Privacy declaration on the App Store, which is visible to you before you update.

Contact

Questions about this policy: admin@ohmslaw.net.