Prezans — Privacy
Last updated 4 August 2026
Prezans is presentation software for churches, and a companion app for the people in them. This explains what it stores, what leaves the building, and what we can and cannot see.
The short version. Almost everything stays on your church's own computer. There are no accounts, no advertising, and no analytics or tracking of any kind in the phone app. When a church chooses to publish its songs so members can read them at home, they are encrypted on the church's machine first — we store them, and we cannot read them.
What stays on the church's computer
Songs, services, Bible text, themes, media, recordings and settings live in a file on the machine the church runs Prezans on. They are not sent to us. The desktop app works with the network cable unplugged, and that is deliberate.
What the phone app stores
- A device token, so the church's computer recognises the phone.
- Which church the phone joined.
- Songs, chord charts and rehearsal recordings downloaded from that church.
- The key needed to open them, when the church has published a library.
All of it is on the phone. Deleting the app deletes it. The app has no sign-up, asks for no email address, and contains no analytics, advertising or tracking software.
Why the app asks for local network access
To find the church's presentation computer on the same Wi-Fi and receive the song currently on the screens. It is used for nothing else — no scanning, no other devices, no data leaves the local network because of it.
What prezans.app holds
A church can link its installation to this service. When it does, we hold:
- The church's name, a licence serial, and a key that identifies it.
- Invitations, stored as one-way hashes — we keep no copy of the codes themselves.
- The words currently on the screens, while a service is being followed online (see below).
- If the church turns it on: its songbook and rehearsal recordings, encrypted.
- A record that a device joined, and when it was last seen.
The encrypted part, precisely
A published songbook is sealed with AES-256-GCM using a key generated on the church's own machine, which is never sent to us. The phone receives that key directly from the church. What we store is opaque: somebody reading our database — including us — sees no lyrics, no titles and no recordings. Rehearsal audio is sealed with the same key.
The part that is deliberately public
If a church shares a live link, the words on the screens during that service are readable by anyone with the link, or with the code if the church sets one. That is the point of the feature: a congregation follows along on their phones. Only the text on screen is shared, and only while it is on screen.
Who else is involved
The service runs on Google Cloud (Firebase) in Europe, which stores this data on our behalf and does not use it for anything else. The phone app talks to that service and to the church's own computer. Nothing is sold, and nothing is shared with advertisers — there are none.
Keeping and deleting
- A published songbook is overwritten each time it is published. There is one current copy per church and no history.
- Invitations expire on their own.
- When a church is deleted, its records and its stored files go with it, including the encrypted songbook and recordings.
- A church can unlink at any time from the desktop app, which stops all of it. Its material on its own computer is untouched.
- Deleting the phone app removes everything the phone stored.
Children
The app is for congregations of every age and collects no personal information from anyone, children included. There is no sign-up, no profile and no message.
Changes
If this changes, the date at the top changes with it.
Contact
Questions about this policy, or a request to delete a church's data: steeve.fong@gmail.com.