Privacy Policy

1. Who we are and what this covers

SermonKeep for Churches is operated by Khawnan Management Solutions LLC, a Delaware limited liability company ("we," "us," or "our"). This policy covers the web application at app.sermonkeep.com and its pages on sermonkeep.com (together, the "Service"). The SermonKeep iPhone app has its own privacy policy. Your use of the Service is also governed by our Terms of Service.

The Service is used by churches. For the sermons and material a church puts into its workspace, we process that content on the church's behalf and according to its instructions; the church decides what to upload, who can see it and when to delete it. For account, billing and usage information, we decide how it is used, as described here.

2. Information we collect

Information you give us

• Account details: your name and email address, and a password (stored by our authentication provider in hashed form, never in plain text). If you sign in with Google, we receive your name and email address from Google.
• Workspace details: your church's name and the answers you give when setting up, such as your role, how often you preach and what you want to use the Service for.
• Team details: the members of your workspace, their roles, and invites, including any email address an admin adds to an invite.
• Sermon content: the audio and video files you upload, YouTube links you paste, and sermon details such as title, preacher, date, series and main passage. If a sermon contains personal information, such as a name mentioned from the pulpit or a voice in the recording, it is part of this content.
• Content the Service creates: transcripts, your edits, review suggestions and your decisions on them, scripture references and generated material.
• Billing details: handled by Stripe. We receive your plan, billing status, invoices, and the card brand, last four digits and expiry date. We never receive your full card number.
• Support requests: what you send us through the Help page or by email.

Information collected automatically

• Usage information: which pages and features you use, actions such as starting an upload or generating material, counts, durations and errors.
• Device and log information: IP address, browser and device type, operating system, referring page, and the date and time of requests.
• Session replays: recordings of how the app's screens are used, with the masking described in section 6.

Information from others

When you link a YouTube video, we read its public details (such as title and length) from YouTube. When you sign in with Google, Google tells us who you are.

3. How we use information

We use information to:

• provide the Service: transcribe sermons, run the review, find scripture references, generate material, search and export;
• create and secure accounts and workspaces, and let admins manage members;
• process payments, track audio usage against your plan and apply fair-use limits;
• send service emails, such as sign-in, password reset, billing and support replies;
• understand how the Service is used, find and fix problems, and improve it;
• prevent abuse, fraud and security incidents; and
• meet legal obligations and enforce our Terms.

We do not sell personal information or sermon content, and we do not use your sermon content to advertise to you or anyone else. Where the law requires a legal basis (for example, in the EU or UK), we rely on performing our contract with you, our legitimate interests in running and improving the Service, compliance with the law, and, where we ask for it, your consent.

4. Automated processing of your sermons

Sermon audio is sent to an automated speech recognition provider to produce the transcript. Transcript text and sermon details are sent to language-model providers to propose corrections, find scripture references and generate material when you ask for it. These steps are automated; no person at SermonKeep listens to your sermons or reads your transcripts, except when you ask us to help with a specific sermon, or when we need to investigate abuse or a technical problem.

Your sermons are not used to train anyone's models. Our speech-recognition provider, AssemblyAI, has our account opted out of its model-improvement program, so it does not use your audio or transcripts to train or benchmark its models. The language-model providers we use through their APIs do not use API data to train their models. We do not use your sermon content to train models of our own.

Nothing in the Service makes decisions about people that have legal or similarly significant effects.

5. Service providers (subprocessors)

These companies process information on our behalf to run the Service. Each receives only what it needs for its task. We may add or replace providers; when we do, we will update this list.

6. Cookies, local storage and analytics

What we store in your browser

• Sign-in session: the app keeps your session in your browser's local storage so you stay signed in. Signing out removes it.
• Analytics: PostHog sets a cookie that is shared across sermonkeep.com and its subdomains, so a visit to our church pages and later use of the app can be recognized as the same person.
• Payments: on billing screens, Stripe may set cookies it needs for fraud prevention.
• Preferences and drafts: small items, such as answers to the setup questions before you create your account, may be kept in local storage.

Session replay

Session replay records how the app's screens are used so we can see where people get stuck. Everything typed into form fields is masked, and so are the transcript, review suggestions and generated material on the sermon page, as are sermon titles, series and preacher names in your library and in the sidebar.

Advertising

We use the Google Ads tag only to measure our own ad campaigns: when you arrive from one of our ads, it stores a click identifier in a cookie on sermonkeep.com, and when an account is created the app tells Google Ads that a sign-up happened, so we know which ads work. It is configured without ad personalization or remarketing: we do not use it to follow you with ads elsewhere, and nothing about your sermons or your account's content is sent to Google. We do not use sermon content for advertising. You can block it with your browser's cookie or tracker settings.

You can block or delete cookies in your browser settings. If you block local storage, you will not be able to stay signed in. We do not currently respond to browser "Do Not Track" signals.

7. How we share information

We share information only:

• within your workspace: members of your church's workspace can see its sermons, transcripts and material, and the list of members;
• with our service providers listed above, to run the Service;
• when the law requires it, or to protect the rights, safety or property of our users, the public or us;
• in a business transfer, such as a merger or sale of assets, in which case this policy will continue to apply to your information; and
• with your consent or at your direction.

8. How long we keep information

• Sermons: transcripts and generated material are kept while your church's workspace exists, including after a subscription ends, so your library stays readable. Audio and video files are kept while the workspace is in use; if a paid subscription ends, or a workspace without one is inactive for 3 months, we may delete its audio and video files 3 months later.
• Deleting a sermon: deletes its audio or video file, its transcript and its generated material from the Service.
• Closing an account or workspace: when an account or workspace is closed, its data is deleted within 30 days. Sermons belong to the workspace, so closing one member's account does not delete the sermons they added.
• Service providers: providers that process sermon content keep it only under their own retention terms. We ask our speech-recognition provider to delete each transcript as soon as we have received it.
• Billing records: kept by us and by Stripe for as long as tax and accounting law requires, even after a workspace is closed.
• Analytics and logs: kept for a limited period and then deleted or aggregated.
• Backups: deleted data may remain in encrypted backups for a short period until they are overwritten.

9. Security

We protect information with measures appropriate to its sensitivity, including:

• encryption in transit (HTTPS) for all connections to the Service and between it and our providers;
• access controls in the database, so each workspace's data can be read only by its own members;
• private file storage, with audio served only through short-lived signed links;
• role-based permissions inside each workspace; and
• restricted access to production systems and keys.

No system is perfectly secure. If we learn of a security breach that affects your information, we will notify you and the authorities as the law requires. Please use a strong, unique password and keep invite links private.

10. International users

We are based in the United States, and the Service is hosted and processed in the United States. Some providers may process data in other countries. If you use the Service from outside the United States, your information will be transferred to and processed in the United States, where data protection laws may differ from those where you live. Where the law requires it, we rely on appropriate safeguards for these transfers, such as the standard contractual clauses offered by our providers.

11. Your rights and choices

Depending on where you live, including under the GDPR, the UK GDPR and U.S. state laws such as the CCPA, you may have the right to:

• access the personal information we hold about you;
• correct information that is wrong or incomplete;
• delete your information;
• export your information in a portable format (you can also export transcripts yourself at any time);
• object to or restrict certain processing, and withdraw consent you have given; and
• opt out of the sale of personal information or its sharing for cross-context behavioral advertising. We do neither today.

To make a request, email hello@khawnan.com from the address on your account. We may need to verify your identity, and we will respond within 30 days or the time the law requires. You can use an authorized agent where the law allows it. We will not treat you differently for exercising your rights. You also have the right to complain to your local data protection authority.

If your information is in sermons a church has uploaded (for example, your voice or your name in a recording), the church controls that content. Please contact the church first; we will help it respond, and you can also write to us.

12. Children

The Service is meant for churches and the adults who work with them. It is not directed at children under 13, and we do not knowingly collect personal information from children under 13 through accounts. If you believe a child under 13 has created an account, write to us and we will delete it.

13. Changes to this policy

We may update this policy as the Service changes or the law requires. We will post the new version on this page with a new "Last updated" date. If a change is material, we will tell workspace admins by email or in the app before it takes effect.

14. Contact us

For any question or request about your privacy, write to us:

Khawnan Management Solutions LLC
Email: hello@khawnan.com