Plain promises about your sermons.
Church leaders tell us their biggest worries about AI are privacy and integrity. So here is exactly what Amenflow does with your sermons. We checked every line against our own code on 18 October 2026.
Questions about your church's data, or want something deleted? Email hello@amenflow.com.
We never write sermons.
Amenflow only starts from a sermon your pastor has already preached or written. There is no “write my sermon” feature, and the “Ask about this sermon” chat is set to decline requests to write one. Two features come close, so we'll be plain about them. The Series plan suggests titles, passages and one-line ideas for a possible follow-up series, and Illustrations offers clearly labeled ideas and related passages. Neither one drafts a sermon. If they don't fit your convictions, ignore them.
Your church owns its content.
Your recordings, transcripts and everything Amenflow makes from them belong to your church (see our Terms). You can edit, export (PDF, Word, email HTML, ZIP) or delete any of it at any time. Deleting a sermon removes its recording, transcript, clips, generated content and edit history right away. Deleting your account also removes your style card. Database backups roll off within 14 days.
We don't sell your data.
We don't sell or rent your content or your people's information. We pass it only to the services listed below, only to run Amenflow. We don't use it for advertising, we don't publish it, and amenflow.com has no ad-tracking pixels.
We don't train AI on your sermons.
Amenflow has no model-training step at all. Your sermons are used only to make your own content. Cloudflare, which runs our AI models, says in its Workers AI data policy that it doesn't use customer content to train models, doesn't keep inputs or outputs after a standard request is answered, and doesn't make them available to other customers. We call Workers AI directly, with no extra logging or storage turned on.
A person stays in charge.
Everything Amenflow makes is a draft for your team to review. Key quotes are taken word for word from the transcript of your recording. You can edit any piece before it goes anywhere, and Amenflow never posts or emails anything to your church for you.
Exactly where your sermon goes
| Step | Where it happens | Who can see the content |
|---|---|---|
| Delivery | Cloudflare's network (HTTPS) carries every visit and upload to our server | Cloudflare, only to deliver it |
| Storage | Our own application server: recordings, transcripts, generated content, your edits and your style card | Your account, and us only for support you ask for |
| Transcription | Cloudflare Workers AI, running Whisper large-v3-turbo (an open model) | Cloudflare, only while it processes the request |
| Writing your content | Cloudflare Workers AI, running Gemma (an open model) | Cloudflare, only while it processes the request |
| Backup when Workers AI is busy | Open-source models (faster-whisper and Qwen 2.5) on our own application server | No other company |
| Style Memory suggestions | Our server compares your edit with the original text. No AI call | No other company |
| Billing | Stripe: your card and billing details. Never your sermons | Stripe |
| Account emails | Not sent through any outside email provider yet. We'll name the provider here before that changes | No one yet |
About our backup. Cloudflare gives us a daily amount of AI processing. If it runs out or is down, the same work runs on open-source models on our own server instead. Your sermon doesn't go to any other company. Whisper (made by OpenAI) and Gemma (made by Google) are open models that Cloudflare runs itself, so OpenAI and Google never receive your content.
What else is in our code. Our software can also connect to other AI services that use the OpenAI-style interface. That connection is switched off and has no account key. We won't turn it on without first updating this page and telling our customers.
For the full legal detail, see our Privacy Policy. Questions? hello@amenflow.com.
Free AI use policy for church boards
Only about 5% of churches have written AI guidelines (Barna, 2026). Copy this template, fill in the brackets, and bring it to your next board meeting. It's free to use and change. You don't need to use Amenflow or credit us.
[CHURCH NAME] POLICY ON THE USE OF ARTIFICIAL INTELLIGENCE (AI) Adopted by [the board / council / session / elders] on [DATE]. To be reviewed every 12 months. Policy owner: [NAME, ROLE] 1. WHY WE HAVE THIS POLICY AI tools can save our staff and volunteers time. They can also make mistakes, sound like no one in particular, and put private information at risk. This policy explains how we use AI faithfully, honestly and carefully. 2. WHAT AI WILL NOT DO HERE - AI will not write our sermons. Preaching is the work of our pastors, done in prayer and study. - AI will not write pastoral prayers, counsel, or personal messages that are presented as coming from a pastor. - AI will not invent stories, testimonies, quotes or statistics that we present as true. 3. WHERE AI MAY HELP After a sermon has been preached (or written by our pastor), staff and volunteers may use approved AI tools to help with: - transcripts and video captions - summaries, recap emails and newsletter drafts - small group questions, devotionals and children's lesson drafts based on the sermon - social media posts and short video clips - first drafts of translations - scheduling and other admin tasks 4. A PERSON REVIEWS EVERYTHING Every AI-assisted piece is reviewed and approved by a named person before it is shared. The reviewer checks: - Scripture references against a Bible, and quotes against the recording - names, dates, places and spellings - that it is faithful to what was actually preached and to what we believe - that it sounds like our church Translations are checked by a fluent speaker before they are published where possible. 5. WE ARE HONEST ABOUT IT We will tell our congregation in plain words how we use AI (for example, a short note on our website). We will never present AI-written text as someone's personal testimony. 6. WE PROTECT PEOPLE'S PRIVACY We do not put any of the following into AI tools: - prayer requests, pastoral care or counseling notes - members' personal details (addresses, phone numbers, health, family matters) - children's names, photos or information - giving records, or anything shared in confidence We get permission before recording or uploading anyone other than the preacher (for example, a testimony or an interview). 7. WE ONLY USE APPROVED TOOLS We only use AI tools whose terms say that: - our content stays ours - our content is not sold and not used to train AI models - we can delete our content at any time Approved tools: [LIST TOOLS]. New tools are approved by [ROLE] before use. 8. COPYRIGHT We respect copyright. We do not use AI to reproduce song lyrics, long Bible passages beyond what the translation's license allows, or other people's images or writing. 9. QUESTIONS AND CONCERNS Anyone with a question or concern about how we use AI can contact [NAME, EMAIL]. This policy is reviewed every 12 months by [ROLE / COMMITTEE]. --- Free template from amenflow.com/pledge/. You can use and change it freely; no credit needed.