Trust
What we protect, and what we won’t claim.
Four commitments that are actually built, and a plain list of the things this page is not going to tell you.
Continuity
Your congregation shouldn’t lose Sunday’s information because a card expired.
If a payment fails, there’s a grace period. If that runs out, your staff may lose access to the admin — but your public bulletin site keeps serving. Service times, upcoming events, and every bulletin you have already published stay online.
- Public site continues regardless of billing state
- Only staff access to the admin is paused
- Restoring payment restores admin access
Separation
One church’s information never reaches another.
Every church on the platform is a separate tenant. Posts, events, staff, media, and ministry data are scoped to the church that owns them, and that scoping is enforced in the data layer rather than hidden in the interface.
- Posts, events, media, forms, and ministries are per-church
- Staff accounts only see churches they belong to
- Automation runs per church, on that church’s own schedule and timezone
Billing
Card details never touch this product.
Payment runs through Stripe’s own hosted checkout and billing portal. Card entry, storage, and management all happen on Stripe’s pages, so there is no card data in this system to protect in the first place.
- Stripe-hosted checkout and customer portal
- No card numbers stored or transmitted by us
- 14-day trial with no card required to start
Human oversight
Nothing publishes that a person didn’t approve.
AI writes a first draft. Moving that draft to published requires a person with the right role in your church to approve it. There is no configuration that lets generated content publish unreviewed.
- Approval is a required workflow state, not a setting
- Review comments and version history are retained
- An emergency pause stops all automation immediately
What we don’t claim
No badges we haven’t earned.
This product is new. It has no security certifications, and saying otherwise would be the least trustworthy thing on this page.
We do not hold SOC 2, ISO 27001, or HIPAA attestation. We don’t describe anything here as “bank-grade” or “military-grade,” because those phrases mean nothing. We have no customer counts, uptime figures, or testimonials to show you, because we haven’t earned those yet either. When any of that changes, it will appear here with a date on it.
Questions we haven’t answered?
Write to hello@example.com and ask. We’d rather tell you what isn’t built than have you find out later.
No card required.