Privacy

People who listen

Anyone can listen to and search a church's archive without signing in. When a sermon is played we add one to that day's count for that sermon. The count does not say who played it, and we do not store the listener's internet address.

A church's pages and the archive inside its website set no cookies. The player remembers where you stopped in a sermon on your own device; that stays in your browser and is never sent to us.

Church staff

People who manage a church's archive sign in with their email address. We keep their name, email, which church they belong to and what they changed, so a church can see who published or edited a sermon. Signing in uses one cookie, on the sign-in site only.

To slow down anyone guessing at sign-in links, we keep a scrambled form (a one-way hash) of the email address and internet address used to ask for one, for one day.

Services we use

• Cloudflare hosts the site, stores recordings, and checks the sign-in and signup forms for bots.
• Cloudflare Workers AI writes out the words of each recording, and drafts the title, passage and outline a church may accept.
• ElevenLabs writes out a recording instead when Workers AI is busy, and only when we have turned on that backup.
• Our processing server, rented from Hostinger, makes the copy of each recording that listeners hear.
• Brevo sends sign-in and notification emails.

Deleting

A church can delete any sermon, and can close its archive. When an archive is closed we delete everything that belongs to it: the recordings, the written-out sermons, the details the church entered, its play counts and its staff accounts. Someone who also serves another church on AmenPreacher keeps their sign-in for that church. We keep nothing but a one-line note that an archive was closed and when, which names no church and no person. The only other copies left are in our automatic database backups and our working logs, and those are gone within 30 days.

Questions

Write to hello@amenpreacher.com.