Last updated: July 2026
CongregateHQ is a church management platform operated by Lagniappe Web Solutions, a service of JADDAR ENTERPRISES LLC. We help churches and religious organizations manage members, communicate by text and email, collect online giving, run events and registrations, coordinate volunteers, build forms, and offer members a self-service portal. This policy explains what information we handle and how.
For most information in the platform, your church is the “controller” of the data and CongregateHQ is the “processor.” Your church decides what member and congregant information to collect and how it is used; we store and process it to provide the service. Your church is responsible for having the appropriate consent and legal basis to collect and use that information, including for minors.
When you create a church account we collect your name, church name, email address, phone number, and subscription billing details. Card details are collected and processed by our third-party payment processor and are never stored on our servers.
Churches add information about their members and contacts — names, phone numbers, email and mailing addresses, family and group relationships, notes, custom fields, attendance, and check-in records. This is used to provide the features the church has enabled and is never sold or shared with outside parties for their own marketing.
When a church uses online giving, we record donation transactions — donor name, amount, date, fund, and whether the gift is recurring — so churches can track and receipt their giving. Payment card details are handled by our third-party payment processor; we store the transaction record (who gave, how much, and when) but not full card numbers.
When someone registers for an event, we collect the information the church’s registration form requests (such as name, contact details, and custom questions) and, for paid events, the registration payment and amount (processed by our third-party payment processor). Forms may include additional details the church chooses to collect, such as emergency contacts or dietary and allergy information.
We process the content and delivery records of the text messages and emails a church sends through the platform, along with opt-in and opt-out (STOP) status, so we can deliver messages, track delivery, and honor unsubscribe requests.
We store volunteer profiles, assignments, and the access a church grants each volunteer, as well as any submissions made through forms the church builds.
Congregants may have portal logins to view their own information and giving history; we store the credentials and activity needed to provide that access.
We keep standard log and security data (such as IP address, browser type, and session activity) and use strictly necessary cookies to keep you signed in and protect your account.
All card payments — church subscriptions, online giving, and paid event registrations — are processed by our third-party payment processor. We do not receive or store full card numbers. We do store the resulting transaction records (amount, date, fund or event, and the associated person) so churches can manage their finances. Each church is responsible for the financial oversight, refunds, and tax receipting of the giving and payments it receives.
CongregateHQ is built to support compliance with the TCPA (Telephone Consumer Protection Act), carrier messaging guidelines, and the CAN-SPAM Act. Message recipients may opt out at any time by replying STOP, QUIT, UNSUBSCRIBE, CANCEL, or END, and we automatically maintain a Do-Not-Contact list. Each church is responsible for obtaining consent from the people it contacts.
Churches may collect information about minors (for example, through children’s check-in or youth event registration) and other sensitive details (such as allergies or emergency contacts). Your church is responsible for obtaining any required parental consent and for handling this information appropriately. We process it only to provide the features your church uses and apply the same security protections described below.
We use TLS 1.3 in transit and AES-256 at rest, require authenticated access to every administrative function, and restrict access to member and financial data to authorized users of each church. We keep security logs and offer optional two-factor authentication and automatic session timeouts.
You may delete your account at any time from your admin dashboard. Upon deletion, church and member data is permanently removed within 30 days. Message delivery logs are retained for up to 90 days for compliance, and certain financial transaction records may be retained longer where required for accounting, tax, or legal reasons.
Your church’s data belongs to your church. We do not sell it. Members and congregants with questions about their information should contact their church, which controls that data; we assist churches in responding to access, correction, and deletion requests.
We rely on a small number of trusted third-party providers to deliver the service — including a payment and giving processor, a text-message (SMS) delivery provider, an email delivery provider, and a hosting provider. Each processes data only as needed to provide its service and under its own privacy policy.
We may update this policy as the platform evolves. Material changes will be reflected by the “last updated” date above, and we will notify active churches of significant changes.
Privacy questions: contactus@congregatehq.com