Skip to main content

ChurchHearth

Effective September 6, 2026

Email practices

How ChurchHearth uses email during the pilot program: operational messages only, sent in the context of an existing church relationship.

This page describes ChurchHearth's current practices during the pilot program.

Operational email during the pilot

During the pilot program, ChurchHearth does not send marketing newsletters, purchased lists, cold outreach, or unrelated third-party promotions. Email is used only for operational messages connected to an existing church relationship or an action initiated through the product.

Email delivery is being introduced carefully for pilot churches. Availability may vary while sending infrastructure is reviewed and enabled church by church.

Messages ChurchHearth may send during the pilot

  • Membership invitations when church staff invite someone to connect with their church in ChurchHearth. The message includes the church name, a single-use invitation link, an invitation code, and an expiry time.
  • Staff operational notices for new care or connection requests when a church has enabled email notifications for those workflows.

Invitation copy tells recipients they can ignore the message if they did not expect it. Invitations do not create recurring marketing subscriptions.

Where recipient addresses come from

Email is sent only when a church staff member creates an invitation for a specific person, or when another workflow in the product requires a transactional notice that the church has chosen to receive by email. Recipients should already have a relationship with the sending church or have requested the communication through that church's normal processes.

We do not use purchased, rented, scraped, or third-party prospect lists.

No marketing lists or cold outreach

ChurchHearth is not a bulk marketing platform. We do not send unrelated promotions, purchased lists, or cold outreach through the product.

Bounces, complaints, and delivery safeguards

ChurchHearth uses provider-level suppression for bounces and complaints and records invitation delivery status on invitation records. Delivery events are monitored so operational issues can be addressed without storing unnecessary message content in routine logs.

Communication preferences

Church staff can configure how certain operational notices are routed inside the product, including whether some alerts are delivered by email. Member-facing church announcements and updates are delivered in the app and through push notifications where enabled—not as marketing email.

Contact

For email practices or compliance questions, contact support@churchhearth.com.