Security

Your members trust you with their details. We take that seriously.

Here is how ChurchBright protects your church’s data — in plain language.

Encryption

All traffic is served over HTTPS. Payment-gateway secret keys and messaging credentials are encrypted before they are stored.

Two-factor sign-in

Team members can protect their accounts with an authenticator app. We recommend it for every owner, administrator and finance officer.

Role-based access

Ten built-in roles and custom roles decide who can view, edit, export or delete. Branch admins only see their own branch.

Separation between churches

Every record belongs to one church, and every database query is checked automatically to make sure it is limited to the church making the request.

Activity log

Sensitive actions — exports, deletions, role changes, settings — are recorded with who did them and when.

Abuse protection

Sign-in, sign-up and public forms are rate-limited, forms are protected against cross-site request forgery, and spam traps catch bots.

Safer uploads

Uploaded images are re-encoded, which strips hidden data such as GPS location from photos.

Your data, your control

Owners can export all church data as CSV at any time. We never sell personal data.

Payments

Card and bank details are entered on your payment provider’s secure checkout (Paystack, Flutterwave, Stripe or PayPal). ChurchBright never sees or stores full card numbers, and gifts are paid by the provider straight into your church’s account.

Good practice for your team

Give every person their own login and the smallest role they need.
Turn on two-factor sign-in for anyone who can see giving or export data.
Remove access as soon as someone steps down.
Never share payment-gateway secret keys by email or chat.

Reporting a vulnerability

If you believe you have found a security problem, please tell us privately at [security email] so we can fix it before it is shared. We appreciate responsible disclosure.