How your data is walled off.
Your church's sermons sit behind real database walls, not just app-level checks. Narrow scope. Encryption. A human you can write to.
Per-church walls at the database
Per-church row-level security walls your data at the database layer, not just the app. One church can never see another's data, and it is enforced by the database itself, not only by application code.
That means isolation is not a hope of careful programming. It is a rule the database applies on every query.
Encrypted transport and storage
Encrypted in transit and at rest. Sermon notes, preferences, and account data move over encrypted connections and sit encrypted where they are stored. Private to your church.
We never touch giving or membership
We never touch giving platforms, member records, or banking. We do not ask for those credentials and we have nowhere to put them.
We never ask for your church's banking, donor, member, or financial systems credentials. We don't connect to them. We only need the pastor's email, the sermon topic, and your tradition. The narrower the scope, the safer the trust.
Narrow scope is the point
Worship Automator is for slides, images, and verses. That is the whole surface. The less of your church we hold, the less there is to protect, and the clearer the trust. We are a tool, not a stakeholder in your ministry.
A human answers
Questions about security go to hello@worshipautomator.com. A real person, often the pastor, replies. Usually the same day.