01
Reporting & moderation
Every surface that carries user content also carries a way to report it. Posts, comments, songs, news articles, and profiles can all be reported from the place you encounter them — there is no separate form to hunt for, and no requirement to leave the screen you are on.
Reports land in a triage queue with an explicit lifecycle: pending, reviewed, actioned, or dismissed. Nothing sits in an undefined state, and every report reaches a decision. Alongside reporting, worshippers can block posts, comments, songs, churches, and news outright, so an individual can shape their own experience without waiting on a moderator.
- Report and block across posts, comments, songs, news, and profiles
- Triage queue with pending, reviewed, actioned, and dismissed states
- Age-appropriate gating on sensitive features
- Churches receive content-violation warnings in their activity inbox
02
Child safety
Child-safety reports are not treated as ordinary reports. They are fast-tracked out of the general queue, they alert the safety team directly, and they are handled against a priority service level rather than in submission order.
Our child sexual abuse and exploitation (CSAE) standards are published as dedicated public pages, so the policy is legible to anyone — worshippers, churches, and app-store reviewers alike — without needing to ask us for it.
03
Account enforcement
When a decision goes against an account, the platform can ban or unban it with a recorded reason, and remove the offending content independently of the account action. Bans are detected in real time by the app, so an enforced account does not keep operating until its next launch.
Enforcement is paired with the ability for any person to permanently delete their own account on request. Deletion is permanent, not a soft hide.
- Ban and unban with recorded reasons
- Content removal separate from account action
- Real-time ban detection in the app
- Permanent account deletion on request
- Admin MFA, login monitoring, and audit logging
04
Privacy architecture
The clearest test of a privacy claim is what happens when a feature would be easier to build without it. Broadcast targeting is that test. A church can send a push notification to men only, women only, or a specific age range — and to do it, the church never receives the underlying follower data.
Targeting resolves on our servers. The church composes a message, picks an audience, and sees a reach number. It does not see which followers matched, their ages, or their genders. The same principle governs public creator pages, which render only whitelisted, escaped fields rather than whatever happens to be on the record.
05
Payments
Both the Christian store and prayer sessions check out through Razorpay. Payments are verified and idempotent, so a retried or duplicated request cannot result in a double charge.
Prayer sessions can be bought individually or as a prepaid ministries pass held in a credits wallet. If a minister goes offline before a session happens, credits are protected — you are not charged for a session you did not receive.
- Razorpay checkout for the store and prayer sessions
- Credits wallet and prepaid ministries passes
- Coupons: percentage or fixed, with limits and expiry
- Idempotent, verified payments
- Credits protected if a minister goes offline
06
Reliability & reach
Notifications work across platforms, including VoIP push so an incoming prayer call rings like a call rather than arriving as a banner. Deep links and shareable web profiles open the right screen in the app rather than dumping you on a home tab.
Content and Bible audio are cached, so a patchy connection degrades the experience instead of ending it.
- Cross-platform push, with VoIP push for incoming prayer calls
- Deep links that open the right screen in the app
- Offline resilience with cached content and Bible audio