Security & data care

Sensitive ministry information
deserves intentional care.

Stoplight is being shaped around a simple responsibility: information entrusted for ministry should support care without becoming casual, overly broad, or disconnected from its pastoral purpose.

Our current approach

This page describes the principles guiding Stoplight’s development. Detailed technical controls, service commitments, and customer agreements will be documented as the product and hosting environment are finalized.

01

Purposeful separation

Stoplight is designed as a pastoral relationship system, separate from financial records, so care decisions remain centered on people rather than contributions.

02

Appropriate access

We are designing access around ministry roles and responsibilities, with the goal that people see only the information needed for their work.

03

Confidential context

Care notes and sensitive interactions require special handling. Product decisions will favor clear visibility, deliberate sharing, and responsible boundaries.

04

Human accountability

Signals and reminders support attention; they do not make pastoral judgments or replace the responsibility of ministry leaders.

05

Reliable stewardship

As Stoplight moves toward broader availability, Spritz will document its approach to authentication, encryption, backups, retention, incident response, and service providers.

06

Clear communication

Churches should understand where their information lives, how it is used, and what choices they have. We will make those answers available before production use.

Have a security question?

Bring it into the conversation early.

Tell us what your church or organization requires for privacy, access, governance, or technology review.

Talk with Spritz