LEGAL

Privacy Policy

Last updated October 24, 2026

Kairo is built for churches, and churches trust it with their services and sermons. This policy explains, plainly, what Kairo collects, why, who helps us process it and the choices you have. It works alongside our Terms of Service.

Who we are

Kairo Presenter (“Kairo”) is provided by Joshua Alexander, based in Nigeria, who is the data controller for the personal data described here. Contact us about privacy at hello@kairopresenter.com. This policy covers the Kairo desktop app, your Kairo account and the website at kairopresenter.com, and is written with the Nigeria Data Protection Act 2023 in mind.

The short version

We collect what Kairo needs to run your account, your church and its services — nothing is sold or used for ads.
Live audio goes to the transcription service your church connects (Deepgram); Kairo doesn't keep recordings.
Sermon transcripts are uploaded to your church's account, encrypted, and kept until an admin deletes them.
Crash reports and usage statistics help us fix and improve Kairo. Both can be turned off in Settings → Privacy.
You can download or delete your data from the dashboard at any time, or ask us to see, correct or delete it.

What we collect

Your account

Your name, email address and password. Passwords are stored only as a secure hash (Argon2id), never in a readable form.
If you sign in with Google: your Google account's email, name and profile picture.
Whether your email is verified, when you last signed in, and the church you belong to.

Your church

Your church's name, time zone and service times.
Who belongs to it and their roles (owner, admin, operator, viewer).

Signed-in computers

For each sign-in: the computer's name and hostname, operating system and version, processor type, app version, IP address and browser or app identifier. This keeps your account secure and lets you see where you're signed in.

Sermons and transcripts

When you're signed in with a verified email, each service's record is uploaded to your church when the service ends: its title, speaker, start and end times, the transcript (with word timings) and the Scripture references Kairo detected.
A summary (recap) may be generated from the transcript and stored alongside it.

Service keys

The keys your church adds for outside services (such as Deepgram, Anthropic, DeepSeek, API.Bible, Brave Search and Google Translate) are stored, encrypted, so they're available on your church's other computers.

Crash reports

If Kairo crashes, a report is sent when you're signed in: what crashed and why, your operating system, app version, memory and graphics status, recent errors, and the last lines of the app's log. We replace your home folder with “~”, but the log can still mention the names of songs or files you used.
Crash reports are on by default. Turn them off in Settings → Privacy → Send crash reports.

Usage statistics

Daily counts of how features are used (for example services started, minutes listened, verses shown), counts of error types, and your system setup — operating system, language, processor count, memory, the number of screens and NDI outputs, and a few settings such as theme and default Bible translation. No transcripts, lyrics or slide content.
Usage statistics are on by default. Turn them off in Settings → Privacy → Share usage statistics.
When you're signed in to the web dashboard, we also record which dashboard pages are opened.

Downloads

When you download Kairo from the website, we record the platform, version, the page you downloaded from and your country. Not your IP address or who you are.

Live audio and AI features

These features run through outside services using keys your church adds, so each provider also handles the data under its own privacy terms:

Live transcription: while Kairo is listening, the microphone audio is streamed to Deepgram, which returns the text. Kairo doesn't store the audio.
Scripture detection, sermon recaps and highlights: parts of the transcript, or all of it, with the sermon's title, speaker and date, are sent to Anthropic or DeepSeek, whichever your church uses.
Bible passages: passage requests for licensed translations go to API.Bible with your church's key. The built-in translations (KJV, BBE and BSB) need no outside service.
Finding and translating lyrics: song searches go to search services (DuckDuckGo, Mojeek, Brave Search, LRCLIB) and lyric websites; lyrics may be sent to DeepSeek or Google Translate to review or translate them.

Kairo doesn't use your content to train AI models, and we don't ask these providers to.

Why we use it

To provide Kairo — run your account and church, sync between computers, transcribe and detect Scripture, and make recaps. This is needed to deliver the service you asked for.
To keep it secure and working — protect accounts, investigate crashes and fix bugs. This is in our legitimate interest and yours.
To improve it — understand which features are used, using statistics you can switch off.
To contact you — verification codes, password resets and important service messages.
Where you've agreed — for example a parent or guardian's consent for someone under 18. You can withdraw consent at any time.

Cookies

We don't use advertising or third-party analytics cookies. The website uses only what it needs to work:

pa_refresh — keeps you signed in (up to 60 days).
pa_google_state — protects Google sign-in, during sign-in only.
sidebar_state — remembers whether the dashboard sidebar is open (7 days).

Your browser's local storage also remembers your dashboard theme and a few session details.

How long we keep it

Account and church details — while your account is open.
Sign-in sessions — up to 60 days after your last activity.
Sermons and transcripts — until a church admin deletes them, or the account is closed.
Crash reports — 90 days.
Usage statistics — about 13 months.
Download records — kept without anything that identifies you.

Security

Data travels over encrypted connections (HTTPS). Passwords are hashed with Argon2id; service keys and sermon transcripts are encrypted at rest with AES-256-GCM. Only a small number of authorised staff can access crash reports and usage statistics, to support and improve Kairo. No system is perfectly secure; if a breach affects your data, we'll tell you and the regulator as the law requires.

International transfers

Our providers run servers outside Nigeria, including in the United States and Europe, and DeepSeek in China if your church uses it. When data leaves Nigeria we rely on our providers' security commitments and contractual protections, as the Nigeria Data Protection Act allows.

Your rights

You can ask us to:

tell you what personal data we hold about you and give you a copy;
correct anything that's wrong;
delete your data and close your account;
send your data to you in a portable format;
stop or limit using it, including withdrawing consent you've given.

You can do the two most common ones yourself: in the dashboard, under Account → Your data, Download my data gives you a copy of everything we hold about you as a JSON file, and Delete account erases your account — along with any church only you use, including its sermons — straight away.

For anything else, or if you'd rather not use the dashboard, email hello@kairopresenter.com and we'll respond within 30 days. You can also switch off crash reports and usage statistics yourself in Settings → Privacy. If you're unhappy with how we handle your data, you can complain to the Nigeria Data Protection Commission.

Children

Anyone can use Kairo, but someone under 18 needs a parent or guardian's consent to create an account. If you believe a child has an account without that consent, contact us and we'll remove it.

Changes to this policy

We'll update this policy when Kairo changes how it handles data, and change the date at the top. For significant changes we'll let you know in the app or by email.

Contact

Questions or requests about your data: hello@kairopresenter.com.