Your church's data, handled with care.

SundayBridge is multi-tenant: every church is its own account, and one church's people, giving, and care records are not visible to another. When you sign in, you see your church and only your church.

The public demo runs on a self-contained sample church. It's read-only — the app blocks every change a demo visitor tries to make — and it's walled off from any real church's account. Someone poking at the demo can never reach your data, and can never alter the sample in a way that affects anyone else.

We'd rather tell you where we are than imply more. Right now SundayBridge uses a single login per church — there is not yet role-based access control or separate staff accounts, so access to giving and pastoral care within your church isn't partitioned by role. If your church needs to limit who sees giving or care notes, plan around that for now. Granular staff roles are on the roadmap.

There is also no data export yet, so keeping your own periodic backup of critical records outside the app is a reasonable precaution until export ships.

SundayBridge is hosted on Amazon Web Services. Traffic between your browser and the app is encrypted in transit with TLS. The database is backed up regularly, so a bad day doesn't mean a lost congregation.

Giving is kept alongside — not merged into — the pastoral picture, so generosity doesn't quietly become a scoreboard. Pastoral care lives in its own cases area with its own history. These are design choices about dignity, not just storage. The principles behind them are in tracking giving in a way that respects the giver.

The people, giving, and records you enter belong to your church, not to us. We don't sell your data or share it with advertisers. You can ask us to delete your account and its data. For the full details, see our privacy policy and terms.

If you find a security issue, tell us directly at security@sundaybridge.com. For anything else, support@sundaybridge.com reaches us. We'd rather hear it from you than not.