Privacy Policy
This page explains what data Kerygma collects, why, and what we do with it. Plain English first, lawyerly details after.
The short version
- The desktop app processes audio locally on your computer. We do not receive or store your sermon recordings.
- The cloud transcription feature (Pro and Plus) sends audio to Deepgram for real-time transcription. Deepgram is our processor; their privacy policy applies to that data while it transits their system.
- The website stores the account and billing information needed to provide subscriptions and gifts. We do not sell or share your data with advertisers.
- Payments go directly to Stripe or Bachs, depending on your billing market. We never see your card number.
1. Data we collect
We collect the minimum data needed to operate Kerygma:
- Account email. Used to authenticate you across the website and desktop app, and to send transactional emails (sign-in links, payment receipts, password reset).
- Subscription state. Your current tier (Free / Pro / Plus), billing provider customer ID, and renewal/cancellation status.
- Gift details. When someone buys a gift, we store the sender and recipient names and email addresses, the selected plan and duration, an optional personal message, payment reference, and claim status. We use these only to fulfil, support, and account for the gift.
- Aggregate usage counters. If you use the cloud transcription feature, we count minutes consumed for quota enforcement. We do not store the audio itself or what was transcribed.
- Server logs. Standard request logs (IP, timestamp, path) retained for 30 days for security and abuse prevention.
2. Data we do NOT collect
- Sermon audio recordings.
- Transcribed text content from your services.
- Lists of which verses you displayed.
- Anything from the Free tier — it runs entirely on your machine.
3. Third-party processors
- Secured Backend — hosts our database and authentication.
- Stripe — processes payments. You enter card details on Stripe’s domain; we receive a customer ID and subscription metadata, never the card number itself.
- Bachs — processes Nigerian-market subscriptions. You enter payment details on Bachs’ hosted checkout; we receive a customer ID and subscription metadata, never the card number itself.
- Deepgram — provides cloud streaming transcription for Pro / Plus tiers. Audio is processed in real time and not stored beyond the transcription window.
- PXXL.APP — host this website. Thanks to Pxxl
4. Cookies
We use one strictly-necessary cookie group: Supabase auth session cookies. These keep you signed in across page loads. We do not use analytics or advertising cookies on this site at this time.
5. Your rights
You can request a copy of your data, request deletion of your account, or correct any inaccuracies by emailing support@kerygma.dev. We respond within 7 working days.
If you are in the UK or EU, you have rights under GDPR including access, rectification, erasure, restriction, portability, and objection. The lawful basis for processing your account data is contract performance (you’ve signed up for a service). Marketing emails, if any, will require explicit consent.
6. Data retention
- Account email + subscription state: until you delete your account.
- Gift purchase and redemption records: retained as needed for customer support, fraud prevention, and financial record-keeping. Personal gift messages may be removed earlier on request where we have no legal need to retain them.
- Provider billing records: retained per Stripe’s or Bachs’ own policy and applicable financial-record rules.
- Server logs: 30 days.
- Cloud transcription audio: not stored. Processed in real time and discarded.
7. Children
Kerygma is not directed at children under 13. We do not knowingly collect data from anyone under 13.
8. Changes to this policy
We’ll post material changes on this page and update the “Last updated” date. If a change materially affects how we handle your data, we’ll email account holders before it takes effect.
9. Contact
Email support@kerygma.dev with privacy questions, complaints, or data requests. See also our Terms of Service and Refund Policy.
