Privacy Policy
Effective November 16, 2026
Hear Church translates a meeting live so people can listen on their phones in their own language. This policy explains what happens to your information when you listen on hearchurch.com, visit our pages about Hear Church or use the Hear Church Mac app. Questions go to support@hearchurch.com.
The short version
- The sound of the meeting stays on the Mac running it. Only the text of what was said is sent out for translation.
- Our server passes captions and translated voice to listeners while the meeting is live and doesn't save them. For congregations on credits, the text sent for translation also passes through our server on its way to the translation service, and isn't saved there either.
- Card payments are handled by Stripe. We never see or store your card number.
- Listeners don't need an account.
- There are no ads, and we don't sell your information. We do track visits to our website with Cloudflare and Google Search Console, to see how people find it and help it rank in search. Our pages about Hear Church also have their own analytics, including session replay. The pages for finding a congregation and listening to a meeting don't load them. We also count app downloads as daily totals, with nothing about who downloaded.
If you listen
- Finding a congregation. When you open the finder, your phone asks whether to share your location. If you allow it, your phone sends your location, rounded to about 100 meters, to our server. It is used to answer that one request. We don't store it or write it to our logs. If you search by name instead, the search text is used the same way.
- Listening. Captions and translated voice are held in memory only while the meeting is live. They are not saved on our server. Your phone remembers your language choice in its own storage.
- You're not identified. We don't ask for your name or email. Anyone with a congregation's link can listen, and meetings are not protected by a password.
If you run the Mac app
What our server keeps about a congregation:
- Its name, church, unit type, stake or group, address, building location, city, meeting times and time zone. Most of this appears publicly so listeners can find it.
- The contact email you sign up with. It isn't shown publicly.
- The name of each connected Mac, when it was last seen, and scrambled (hashed) versions of its access token, your connect code and any one-time setup code.
- A record of each meeting: which languages it used, which Mac started it, and when it started and ended. Not what was said.
- For billing: whether the congregation pays with credits or its own API key, how many seconds of speech each meeting had in each language someone was listening to, and each credit purchase (amount, the hours it bought, date and Stripe's payment ID). Not what was said.
We keep this until you ask us to delete it.
Diagnostic logs: unless you turn it off, the Mac app sends us a diagnostic log so our support team can see what went wrong without asking you. It is technical only: errors, timings, microphone level, languages, delays, app and system versions, and which speech model is in use. Words are removed before anything leaves the Mac, so it never contains anything that was said, recognized, translated or spoken. You choose this during setup and can turn it off anytime in the app's Settings, under General. "Send logs to support" in the same place sends the last 7 days once, with a note if you add one. We keep diagnostic logs for 30 days.
What happens on your Mac:
- Speech is turned into text on the Mac itself. Audio from the microphone is not uploaded anywhere.
- The app saves a log of each meeting on that Mac, including the transcript and its translations. It stays on the Mac and is not sent to us. You can delete it from the app's folder in Application Support/Hear Church.
- If you turn on recording, the translated voice is saved on that Mac too.
- The Mac's access token, and your Anthropic API key if your congregation uses its own, are stored in the Mac's Keychain.
If you visit our pages about Hear Church
Our pages about Hear Church, such as the home page, the how-it-works page and the blog, run analytics on our own server, to show how people find them and whether they help people get the app. The pages for finding a congregation and listening to a meeting don't load them.
- What it records. The page address and the site you came from, how far you scroll, what you click and the words on it, and up to 120 characters of any text you copy.
- Session replay. About one visit in four is recorded once you first interact with the page, so we can play back what the page showed and what you did on it, such as moving the pointer and clicking. Anything typed into a field is masked. Replays are deleted after 30 days.
- Your device and location. Your browser and device details, and your approximate location (country, region and city) worked out from your IP address. We don't store your IP address. We turn it into a one-way code that changes every day, so one person counts as one visitor that day and we can't connect visits across days.
- How long we keep it. Apart from replays, these visit records have no set deletion date.
- Cookies and opting out. We don't use cookies. A random ID in your browser tab ties one visit's pages together and goes away when you close the tab. A second note in the same tab records whether the visit is in the replay sample, and it goes away too. If your browser sends Do Not Track or Global Privacy Control, nothing is recorded.
Who else handles information
- Anthropic receives the text of what is said in the meeting so Claude can translate it. For congregations on credits, the text goes from the Mac through our server to Anthropic under our account. For congregations using their own API key, the Mac sends it straight to Anthropic with that key, and your use of the key is governed by your agreement with Anthropic. See Anthropic's privacy policy.
- Stripe processes credit purchases. The card details and anything else you enter on Stripe's checkout page go to Stripe, not to us; see Stripe's privacy policy. Of what Stripe sends us about a payment, we keep only the amount, its payment ID and which congregation it was for.
- Cloudflare runs the network in front of hearchurch.com and stores app downloads. All website traffic, including IP addresses and the rounded location above, passes through it, and it may keep short-term logs.
- OpenStreetMap Nominatim or Mapbox receive the address or building location you enter at sign-up, to place it on the map.
- Apple receives the address you type in the Mac app during setup, or the Mac's location if you use it, to place the building on the map.
- Hugging Face hosts the speech and voice models. The app downloads them from there, so Hugging Face sees your Mac's IP address.
- Email providers handle messages you send to our support address.
We don't share your information with anyone else unless the law requires it.
Children and sensitive meetings
Hear Church isn't aimed at children and doesn't knowingly collect information from them, but children may speak in or listen to a meeting. What is said in a meeting can be personal or religious in nature. Whoever runs the meeting decides whether to translate it, should get approval from their bishop, pastor or other leader first, and should turn translation off for anything that should stay private.
Your choices
Email support@hearchurch.com to see, correct or delete what we hold about your congregation or to remove it from the finder. Depending on where you live, you may have other privacy rights, and we will honor them. If you're asking about a congregation, we may need to confirm you speak for it.
Security
Connections to hearchurch.com are encrypted. No system is perfectly secure, so please keep your connect code private and make a new one if it gets out.
Changes
If this policy changes, we'll post the new version here with a new date. If a change is significant, we'll also try to tell congregations directly.