AutoSermon
FeaturesPricingDocsChangelogDownload
Sign inGet started

Privacy

What AutoSermon does with your information, in the order it actually happens: on your computer first, then in your account, then with the companies that process payments and speech.

Last updated 3 October 2026

Who we are

AutoSermon is an independent product rather than a registered company. Everything to do with privacy — questions, requests, complaints — goes to [email protected], and that address reaches a person, not a queue. If you need the name and address of the controller for a formal request, ask there and it will be given to you.

Most of your work never leaves your computer

The desktop app is local-first. Your service library, slides, themes, layouts, imported media, sermon transcripts and recordings are stored in AutoSermon’s folder on the machine you installed it on. They are not uploaded, not backed up to us, and not readable by us.

API keys you paste for your own model providers, and your stream key, are stored on the same machine and encrypted with your operating system’s keychain. Where the OS offers no keychain, the app stores them unencrypted and warns you in its log rather than implying a protection it cannot provide.

The daily check-in

Once a day, an installed copy of AutoSermon tells us it is in use, whether or not anyone has signed in. That is how we know how many churches use it. The check-in holds exactly this:

  • A random id the app made on its first run. It is the same installation id a signed-in computer is listed by, and it is not made from anything about you or the machine.
  • The app version, the operating system and processor type, and whether it was installed from our website or the Microsoft Store.
  • Whether someone is signed in on it, but not who.
  • The country the check-in came from, worked out from the connection when it arrives. The IP address is not stored.

Nothing from your library, services, transcripts, recordings or settings is included. Turn it off in Settings → Account → Anonymous check-in.

What your account holds

Signing in creates an account so plans, allowances and devices can be tracked across the computers your church uses. That account holds:

  • Your email address, name and profile image, as given to our authentication provider.
  • Your church’s workspace name, and which people belong to it and in what role.
  • Your plan, its status, whether it bills monthly or yearly, and the identifiers Stripe uses for the subscription.
  • One record per signed-in computer: an installation id the app generates on first run, a device name, the platform and app version, and when it was last seen. This is what enforces the device limit on your plan.
  • Usage counts — the AI credits each AutoSermon Cloud request used, and seconds of cloud transcription once it is available — with the computer and the model they were spent on, so an allowance can be measured. The text, images and answers of those requests are not stored, and neither is anything transcribed.
  • For each Bible translation your church buys: the amount, currency, date and status of the purchase, Stripe’s identifiers and fee for it, who started it, and which of your computers have downloaded the translation. This is what enforces the translation’s licence and what the royalty owed to its publisher is worked out from.

Sermon audio, and when it leaves the room

This is the part worth reading closely, because it is your choice and the app does not make it for you.

In local transcription mode the speech model runs on your own computer and no audio is sent anywhere. In remote mode another AutoSermon computer on your own network does the listening and sends this one its transcript. In cloud mode the audio is sent to the speech provider you selected — OpenAI, Groq or Google Gemini, with your own key — and is processed there under that company’s terms. If local transcription cannot start and you have set up a cloud provider, the app switches to it and says so on screen.

The same applies to the AI features. Scripture search, sermon notes, slide generation, reading an order of service and the assistant send the text they are working on to the AI provider in use: AutoSermon Cloud, or your own OpenAI, Anthropic, Google Gemini or Groq key, or a model running locally through Ollama, which sends nothing outward at all. Your own provider is always used before AutoSermon Cloud unless you choose Cloud, and a signed-out app never uses Cloud.

When you stream, the program — the cameras, the sound and the lyrics or scripture over them — is sent to YouTube, or to the server you entered, and is handled there under that service’s terms. When an ATEM switcher sends the stream, the switcher sends it. Automatic camera switching set to Online sends a still of every camera to the AI provider in use every few seconds; set to Offline, the cameras are looked at only on your computer.

With AutoSermon Cloud, each request — the text, and the picture when an order of service is read from a photo or the cameras are looked at for switching — goes to our gateway at autosermon.app and from there to DigitalOcean’s serverless inference service, which runs the model on DigitalOcean’s own servers and sends back the answer. The model is Z.ai’s GLM-5.3 Flash, which DigitalOcean runs itself, so the request goes to no other company. We keep a count of the credits each request used, not the text, images or answers.

Payments

Payments are handled entirely by Stripe. Card numbers are never sent to AutoSermon, never pass through our servers, and are never stored by us. We keep only the identifiers Stripe gives us for your customer record, your subscription and any Bible translation you buy — with, for a translation, the amount, Stripe’s fee and a link to Stripe’s receipt — so we know which plan you are on and what your church owns.

What we do not do

Apart from the daily check-in above, there is no analytics in AutoSermon. Nothing records what you do in the app, and there are no crash reports, no session recording, no advertising identifiers and no third-party trackers in the desktop app. Nothing is sold or shared for marketing, by us or by anyone.

The app once offered switches for crash and usage reporting. Nothing was ever sent, so the switches were removed rather than left implying that something was.

Why we are allowed to hold it

Under the UK and EU GDPR, we rely on the following bases. Performing our contract with you: your account, your plan, your devices and the allowance counts, without which the service cannot be provided. Our legitimate interests: keeping accounts secure, preventing abuse of allowances, answering your emails, and counting the copies of AutoSermon in use through the daily check-in, which you can turn off. Your consent: where you choose to send audio, text or camera stills to a cloud provider, or to stream, which you give by selecting that mode or provider, by going live, or by signing in and using an AI feature with no provider of your own, and can withdraw by selecting another or ending the stream.

How long it is kept

Account, workspace and subscription records are kept while your account exists, and are deleted when you delete it. Usage events are kept while they are needed to calculate an allowance period and for a reasonable interval afterwards for billing questions. Device records are removed when you sign the device out or delete the account. A copy’s check-in record is deleted two years after its last check-in. Records of Bible translation purchases are financial records: they are kept after an account is deleted, for as long as tax and the publishers’ licences require.

What sits on your own computer is yours to keep or delete. Uninstalling AutoSermon does not remove your library; the app has a setting that shows you exactly where it lives so you can remove it yourself.

Where it is processed

Our providers — the authentication service, Stripe, DigitalOcean (which hosts the site and runs AutoSermon Cloud’s AI), whichever speech or model provider you choose, and the service you stream to — may process data outside the UK and the EEA, including in the United States. They do so under the transfer safeguards each of them publishes. If this matters to your church, local transcription mode, a locally-run model and offline camera switching keep everything but the stream itself inside your building.

Your rights

You can ask for a copy of what we hold, ask us to correct it, ask us to delete it, ask us to restrict or stop a particular use, or object to it. Write to [email protected] and we will answer. You also have the right to complain to your data protection authority — in the UK that is the Information Commissioner’s Office — and you are welcome to do that without asking us first.

Changes

If this notice changes in a way that affects you, the date below changes with it and the change is described rather than folded in silently. Last updated 3 October 2026.

On 29 September 2026 the list of speech providers was corrected to match the app, remote mode was described correctly, and AutoSermon Cloud was marked as not yet available.

Later on 29 September 2026 AutoSermon Cloud’s AI became available. This notice now says where its requests go (our gateway, then DigitalOcean’s inference service), when the app uses it, and what is kept: a credit count per request, not the text. Cloud transcription is still not available.

On 30 September 2026 this notice added what is kept when a church buys a Bible translation, and how long.

On 1 October 2026 the app began a daily anonymous check-in, so the copies in use can be counted whether or not anyone signs in. The notice now says what it holds, why, how long it is kept and how to turn it off (see The daily check-in).

On 3 October 2026 the app began streaming and switching cameras. This notice now says where a stream goes, that the stream key is kept like an API key, and that automatic switching set to Online sends camera stills to the AI provider in use.

See also Terms.

AutoSermon

Scripture on screen while the sermon is still happening.

v1.0.10
ProductFeaturesPricingDownloadChangelog
ResourcesDocumentationContact
AccountSign inCreate accountWorkspaceTermsPrivacy