Clip privacy policy
The short version: your sermon stays on your device. Clip transcribes, edits and exports everything locally, and the only thing that can leave your machine is the transcript text — and only for two optional features you switch on yourself.
What runs on your device
Clip is a browser app. When you drop in a sermon video or audio file, everything — reading the media, transcribing it with Whisper, scoring and suggesting clips, cutting, rendering, and exporting — happens inside your browser, on your own machine. Audio and video files are never uploaded.
The Whisper model weights are fetched once from the Hugging Face model hub (with a jsDelivr fallback for the runtime library) and then cached by your browser. This is a download to your device — no file or transcript goes the other way.
What leaves your device
Only text, only for two optional features, and only when you turn them on:
- Content (collateral writing). When you generate content, your transcript is sent to a private language-model endpoint owned by the author (josiaho.com) and written as blog posts, devotionals, social posts, a podcast description and a summary email. Only the transcript is sent — never the audio.
- Cloud clip suggestions. If the optional cloud suggester is enabled, the transcript (never the audio) is sent to a Cloudflare-hosted worker where a language model suggests passages that stand on their own. This is quota-limited and always falls back to the local suggester. This feature is currently not enabled in the app.
Never sent: audio, video, stills, or anything else — no matter what is enabled.
What is stored locally
- localStorage — your settings, the correction glossary, caption style, and the recent-projects list.
- IndexedDB — cached audio for projects you reopen ("Open recent"), so you can pick up where you left off. Removing a project also removes its cached audio.
Everything stored is tied to this browser on this device. Clear your site data (or use the clear options in the app) and it is gone. There are no accounts, no profiles, and nothing is synced anywhere.
Cookies and analytics
Clip uses no analytics and no advertising, and sets no tracking cookies. The app itself is served over HTTPS; site visits may be measured in aggregate by the host (Cloudflare Pages) for operational purposes only.
Data protection
- Your media never leaves your machine — it simply cannot be seen by us.
- Transcripts sent to the content endpoint or the suggester are used solely to produce the piece you asked for and are not retained.
- There is nothing to sell: no accounts, no profiles, no behavioural data.
Contact
Clip is made and operated by Josiah Oslund. Questions about this policy, your data, or anything else: me@josiaho.com.
If you want your own never-leaves-your-device copy of this policy for church bulletins, email me — it is part of the stance: nothing about your congregation's sermons should be anyone else's data.