Privacy Policy
Last updated 24 August 2026.
The short version. Your video file stays on your own machine — when you use the web app, only the audio is sent for transcription, and nothing containing the picture leaves your browser. Your transcript and your editing decisions are stored so you can come back to them. To do the work, that text is sent to AI providers, named below. We never publish your content, never sell it, and never use it to train anyone’s models. You can delete all of it, at any time.
1. Who is responsible
SermonSignal is the data controller for the information described here. Registered name and address to be confirmed before public launch. Privacy contact: [email protected].
2. What happens to a sermon recording
This is the part most people want to know, so it is spelled out step by step.
- The video file itself is not uploaded. In the web app the recording is read inside your browser. It is never sent to our servers.
- Only audio is sent, and only to transcribe it. Your browser extracts a low-bitrate, audio-only copy — the picture is stripped out before anything is sent, and the software checks that the copy contains no video track before it leaves. That audio goes to our transcription provider.
- The transcript comes back and is stored against your account, so you do not pay to transcribe the same sermon twice.
- The transcript text is what the AI reads. Choosing the moments, writing captions and planning the edit all work on text, not on your video.
- Your finished clips are rendered in your browser and saved on your own device. We store the decisions that make up a clip — which passages, what timings — as a backup so your work is not lost if your browser data is cleared. That backup contains no video.
If you use the desktop application, the whole editing process happens on your own computer; transcription and AI requests are still relayed through our service so they can be billed, and the same providers apply.
3. What we collect
- Account — your email address, and an encrypted password if you set one.
- Content — sermon transcripts, project and clip data, and titles you give things.
- Billing — your plan, credit balance and transaction history. We never see or store your card details; those go directly to Stripe.
- Usage — records of jobs run and credits spent, which is how billing and refunds are calculated.
- Technical logs — error and diagnostic records, kept briefly, used to fix faults.
4. Who we share it with, and why
These are processors acting on our instructions. They receive only what they need to do their part.
- Supabase — accounts, authentication and database storage.
- Railway — hosting for the service.
- Stripe — payments, subscriptions and invoices.
- AssemblyAI — speech-to-text. Receives the audio-only copy described in section 2.
- AI model providers — receive transcript text in order to select moments and write captions. Depending on the quality setting you choose, this may be DeepSeek, Z.ai, Moonshot (Kimi), Anthropic, or OpenRouter acting as a router to another model.
- Cloudflare — serves this marketing website and provides privacy-preserving analytics that set no cookies.
Some of these providers operate outside the UK and EEA. Transfers rely on the appropriate safeguards, such as the UK International Data Transfer Addendum or EU Standard Contractual Clauses.
We do not sell your data, and we do not give anyone permission to train models on your content. If you need a guarantee on that point stronger than a provider’s standard terms, contact us before uploading anything sensitive — the quality setting you pick determines which provider sees the text, and we can tell you exactly which.
5. Why we are allowed to process it
- To perform our contract with you — running your account, transcribing, generating clips, taking payment.
- Legitimate interests — keeping the service secure, preventing abuse, and fixing faults.
- Legal obligation — keeping financial records.
6. How long we keep it
- Content — until you delete it, or until your account is closed, whichever is first.
- Account records — deleted within 30 days of your account being closed.
- Billing records — kept for six years, because tax law requires it.
- Technical logs — kept for a short period and then discarded.
7. Your rights
Under UK and EU data protection law you can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, or to receive it in a portable form. Write to [email protected] and we will respond within one month.
Most of it you can do yourself: delete a project in the app, or close your account to remove everything.
If you are unhappy with how we have handled your data you can complain to the UK Information Commissioner’s Office at ico.org.uk, or to your local supervisory authority.
8. Cookies
This marketing website sets no cookies and uses analytics that do not track individuals, which is why you are not being asked to dismiss a banner.
The application sets one thing in your browser: the session token that keeps you signed in. It is required for the app to work and is not used for advertising or tracking.
9. Children
The service is for organisations and is not directed at children. We do not knowingly collect data from anyone under 16. Note that a sermon recording may contain images or voices of children — you are responsible for having permission to process it.
10. Changes
We will post any changes here and, where they are significant, email you before they take effect.