← Church Slides

Privacy

Last updated 21 October 2026

Church Slides is made by Martin Main, an individual developer in Nova Scotia, Canada. This page explains what the app and this website send, where it goes, and how to turn it off. Martin is responsible for privacy here; questions, or a request to see or delete your data: martinmain93@gmail.com.

Who is responsible for what

For error reports, feedback, usage statistics and download counts, we decide what is collected and why, so we are responsible for them. Everything else (your library, setlists, settings, the app’s log, and any recordings) is held only on your church’s computers. Your church is responsible for that, and we don’t receive it, apart from the log extract in an error report.

What the app sends

Error reports

When something goes wrong, the app sends a technical report so it can be fixed: the error, the app’s version, the computer’s model, system version and chip, and the end of the app’s log. The log can include song titles, lyrics and audio device names. Before a report leaves your computer, the app is designed to remove anything said into the microphone, your user name, the computer’s name, and people’s names in device names (such as “Sarah’s AirPods”). Reports carry a random install number that doesn’t say who you are, plus a contact only if you type one in.

The app asks when you first open it, with error reports ticked; you can untick it then, or turn it off any time in Settings → Privacy → Send error reports. Nothing is sent before you’ve answered.

Usage statistics

Only if you say yes when the app asks. For each service: how long it ran, how many songs it had, how long the AI was on, how many slide changes were made by the AI and how many by hand, and which screen layout was used. Once a day: how many songs are in the library and whether the AI could start. Never song titles, lyrics, setlist names, or anything typed or said.

With usage statistics on, the app’s update checks (when it opens, then once a day) also send a random install number, the app’s version, and the computer’s system version and chip, so we know how many installs are in use and which systems need supporting. Our server notes the country a request comes from, but doesn’t keep your IP address. With it off, update checks still happen but aren’t counted.

The install number isn’t your name or your church’s, but because it stays the same it is still treated as personal data, and everything on this page applies to it.

Off unless you agree. Change it any time: Settings → Privacy → Share usage statistics.

Feedback

When you use Send feedback, we get your message, the email or church name you give (if any), the install number, the app version and system details. For a problem report you can also attach the app’s recent log, cleaned as described under error reports. Feedback is also delivered to the developer’s email so we can reply.

Service recordings

The app can save a recording of each service (the audio, a transcript of what the AI heard, and when each slide changed) to help tune the AI. It is off unless someone turns it on in Settings → Developer tools, and the app explains what it captures before it starts. While it’s on, the operator screen shows Recording. Recordings stay on your computer, are never sent to us, and are deleted after 30 days unless you choose otherwise or approve one in Developer tools to keep.

A recording picks up everything the microphone hears, which can include prayers, announcements, visitors and children. If your church records, it is responsible for telling the people present (for example on the service sheet or a notice at the door) and for following the recording and privacy laws where you are.

The app turns speech into text to follow the songs. It doesn’t identify who is speaking or create voiceprints.

Features that go online because you choose them

These go to other companies, not to us, and each is used only if you set it up. Where your church uses them, your church is that company’s customer and is responsible for telling the people present if live audio leaves the building.

This website and downloads

The download buttons pass through our server, which counts each download: which installer, the country it came from, whether it was a Mac or Windows browser, and the site that linked to us. It doesn’t keep IP addresses. The installers and updates themselves come from GitHub, which sees your internet address as any website does. The site sets no cookies and runs no analytics scripts. Our host, Netlify, keeps standard web server logs.

Where it goes, and for how long

This means some data is stored outside Canada, where it can be accessed by courts and authorities under that country’s laws.

Only people working on Church Slides have access to this data. Sentry, Google and Cloudflare store it for us under their data processing terms and don’t use it for themselves. It’s used to fix problems and decide what to build next, and never for anything else.

Your choices and rights

Each kind of automatic sending has its own switch in Settings → Privacy, and changes take effect straight away. Error reports are on unless you turn them off, after the app has told you about them; usage statistics are sent only if you say yes. You can change either at any time. Feedback is sent because you choose to send it. Download counts hold nothing that identifies you.

You can ask to see or delete what we hold about your install: use Ask for my data to be deleted at the bottom of Settings → Privacy, or email us your install number (shown in the same place). We’ll delete what we can find linked to that number and reply within 30 days. Standard server logs kept by our hosts can’t be searched by install number.

If you’re not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada, or in Quebec, the Commission d’accès à l’information. If you’re in the UK or EU, you can also complain to your data protection authority.

Children

Church Slides is made for church teams, not for children, and we don’t knowingly collect anything from children.

Changes

If this changes, we’ll update this page and the date at the top. We’ll mention significant changes in the changelog.