Access follows the person and the church
Staff permissions control which tools and records a person can read or change. Church-scoped access checks keep one church’s data separate from another’s. Review roles regularly, especially for giving, care, counseling and administration.
Directory records and sign-in are separate
A person can be part of your church directory without an app account. App membership and staff access have their own approval and permission controls. Knowing a record URL does not grant access.
Payments go through the payment provider
Online giving uses Stripe. Subscription billing and church giving are separate flows. Review your church’s provider connection and account access with the people responsible for finance.
Keep exports and conversations in the right hands
Authorized staff can use supported exports and reports. Exported files need the same care as the original records. Private support conversations use staff authentication or the private link emailed to a public requester.
Public discovery contains public information
Marketing pages, public learning articles and demonstration screenshots are separate from church records. Search and AI reference files contain reviewed public product information. Demo screenshots use the fictional Christ Church tenant.
Ask about a specific requirement
Contact support with your organization’s security, retention or procurement requirements so the team can answer the exact question. The privacy policy and terms explain the published data and service commitments.
By Moriah LLC, makers of ChurchFoundry · Reviewed