Privacy policy
The short version
Search My Church lets a church put its sermons and teaching materials in one library. People can then ask questions and get answers that point to the exact sermon and moment.
We keep what the service needs to run: sign-in details, the church's content, and the questions people ask.
If a church connects its YouTube channel, we get read-only access to its videos and playlists. We use that access only to build that church's library.
We don't sell your data. We don't show ads.
To ask a question about your data, or to ask us to delete it, email support@mosierdata.com.
Who we are
Search My Church (also known as Berean Library) is run by Mosier Information Services, Inc., doing business as MosierData. In this policy, "we", "us" and "MosierData" mean that company.
211 E. Main Street, Suite 213, Lakeland, FL 33801, United States.
Questions about this policy: support@mosierdata.com.
Who uses the service
Churches are our customers. A church's staff add the church's sermons, notes, website pages and other material, and manage its library.
Members and visitors use the church's chat page, or a chat window placed on the church's own website, to ask questions about the church's teaching.
For a church's library and its questions, the church decides what goes in and who can see it. We handle that information to run the service for the church.
What we keep
Your account (church staff and signed-in members)
- Your email address and your name.
- How you sign in. You can use Google, a link we email you, or a passkey. If you use Google, we get a stable ID that is yours alone at Google, and an email address Google says is verified. We ask Google for nothing else at sign-in. For a passkey, we keep the public part of the key. We never see a password, because there is none.
- Which church you belong to and your role there.
- A sign-in cookie, so you stay signed in. See "Cookies" below.
The church's library
- Sermon transcripts, sermon notes, website pages and other material the church adds or connects.
- Facts about the church that staff confirm, such as service times.
- Summaries, Bible-verse references and study guides that our system writes from that material. Staff can edit, hide or remove them.
Questions and answers
When someone asks a question, we store the question, the answer we gave, the sources the answer pointed to, and how the answer turned out. We also keep a random session ID, the IP address and browser details that came with the request, and the country that address maps to. We use this to run the service, to keep it safe, and to show the church what people ask. A church's staff can see that church's questions in the back office.
Please don't put sensitive personal details in a question. The service is for questions about a church's teaching.
Feedback and email
If you send feedback, we keep it. If a church invites you to join, we keep your email address to send the invitation.
Activity records
We keep a record of important actions, such as sign-ins, changes to a church's settings, and times when MosierData staff open a church's back office to help. Each record shows who acted and when.
Connecting a YouTube channel
A church can connect its YouTube channel so we can build its library from its videos. The person who connects it signs in with Google and approves access. Here is exactly what that means.
- What we ask for. Read-only access to the channel (the YouTube
youtube.readonlyscope). We can see the channel's ID and name, its playlists, and the list of videos in them. We cannot change, upload, delete or comment on anything. - What we do with it. We show the church its playlists so it can choose which to import. For the videos the church chooses, we fetch the public video and its audio, and make a transcript. Sermon text goes into that church's library only.
- What we keep. The connection details (the channel, who approved it, and when) and the access tokens Google gives us. The tokens are encrypted on our server. We use them only to read that church's channel.
- Who sees it. The church's staff, through the church's library. We don't sell or rent it. We pass it to the services listed below only to run the library (for example, transcription).
- Ending the connection. The person who connected it can remove our access at any time at myaccount.google.com/permissions. A church can also email us and we will disconnect it. After that we can no longer read the channel. Transcripts already in the library stay until the church asks us to delete them.
Limited Use. Search My Church's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use YouTube data only to provide and improve the features the church asked for, in that church's library. We don't use it for ads. We don't sell it. We don't allow people to read it, except where you give permission, where it is needed for security or support, or where the law requires it.
Use of YouTube through Search My Church is also subject to the YouTube Terms of Service and the Google Privacy Policy.
How AI is used
- Answers. When someone asks a question, we search the church's library for the matching passages. We send the question and those passages to an AI language model, which writes the answer. The model we use for this is OpenAI's.
- Search. To make the library searchable by meaning, we send pieces of sermon text to OpenAI to turn them into number lists ("embeddings"). The question goes the same way.
- Summaries and guides. We use the same model to write sermon summaries, verse references and study guides from the church's material.
- Transcripts. For audio that has no usable captions, a transcription service turns the speech into text.
We don't send your name or email address to the AI model. We use these companies' paid services for business customers. We do not opt in to any program that lets them use this data to train their models. They handle what they receive under their own terms.
The answers can be wrong. See our terms.
Who processes your data
These companies help us run the service. Each gets only what its job needs.
| Service | What it does | What it sees |
|---|---|---|
| DigitalOcean | Hosts our server | Everything the service keeps, on our server |
| Neon | Hosts our database | Everything the service keeps |
| Cloudflare | Delivers the website and API, protects them from abuse, and runs a bot check on sign-in | Requests to the service, including IP addresses |
| OpenAI | Writes answers and summaries, and makes search embeddings | Questions and passages of the church's material |
| AssemblyAI | Turns audio into text, when a video has no usable captions | The audio of videos a church chose to import |
| Apify | Fetches public video information and audio for videos a church chose | Public video addresses |
| Sign-in, and (with a church's approval) read-only YouTube access | That you signed in; the YouTube data described above | |
| SendGrid | Sends sign-in links and invitations | Your email address and the email's content |
| Sentry | Tells us when the service crashes | Error details, with personal content removed where we can |
We don't sell personal information, and we don't share it for advertising.
Cookies
We use a sign-in cookie so you stay signed in, and a small cookie that remembers which church you are working in. The bot check on sign-in may set its own cookie. We don't use advertising or tracking cookies.
How long we keep it
We keep a church's library, and the questions asked of it, while the church uses the service. A church can ask us to delete any of it. We keep activity records so we can investigate problems and show who did what.
When you ask us to delete something, we delete it from the live service. Copies in backups age out on our host's normal schedule.
Your choices
- See, correct or delete your information. Email support@mosierdata.com. We reply within a few business days. For a church's library or its questions, we may need to check with the church too.
- Church staff can edit, hide or remove items in the church's library in the back office.
- Remove YouTube access at any time, as described above.
- Sign-in. You can sign out on any device from your account page.
Children
Search My Church is not meant for children under 13, and we don't knowingly make accounts for them. If you think a child under 13 has an account, email us and we will delete it.
Security
- All traffic uses HTTPS.
- Each church's library is kept separate from other churches', and the server checks who you are and what you may see on every request.
- Staff accounts that can reach across churches need a second sign-in step.
- We encrypt the YouTube access tokens we store.
- If a breach affects your personal information, we will tell you as the law requires.
Changes to this policy
We will update this page when the service changes, and change the effective date at the top. If a change affects how we use information you have already given us, we will tell you before it takes effect.
Contact
Mosier Information Services, Inc., doing business as MosierData
211 E. Main Street, Suite 213, Lakeland, FL 33801, United States
support@mosierdata.com