Privacy

Privacy policy

Last updated: 10 October 2026.

What we collect

On the hosted service we store the account details you provide (name, email, a hashed password) and the content you create: presentations, slides, songs, service plans and uploaded media. Server logs record request method, path, status and timing for operational purposes.

What we do not do

• We do not sell or rent your data.
• We do not use your lyrics, media or account content to train AI models.
• We do not read your presentations.
• We do not require an account with us to self-host the software.
• A self-hosted instance sends nothing to us at all.

AI disclosure

Parts of the software itself were produced with AI-assisted development and reviewed by a human before release. That applies to source code and interface copy only. AI is not used to generate, process or store the worship content you enter. If you later choose a feature that generates text for you, it will be clearly labelled and optional.

Where your data lives

On the hosted service, data is stored on the servers running app.simpleworshippresenter.com. When you self-host, your data lives entirely on the machine you control — database and uploaded files are stored in a single directory you configure and back up.

Retention and deletion

You can delete your account from Settings. That permanently removes your presentations, songs, service plans, media and files, and releases the storage they occupied. Backups may retain data for a limited period before they rotate.

Security

Passwords are hashed with bcrypt and never stored in plain text. Sessions use signed, HttpOnly cookies. Every protected request is authorised server-side and scoped to your account. Rate limits are applied to sign-in endpoints. We recommend HTTPS for every deployment.

Your rights

You can request a copy of your data or its deletion by contacting the site owner. Churches using a self-hosted instance should contact their own administrator.

Contact

Simple Worship Presenter is created and maintained by Alexander Wasson at alexanderwasson.dev.