Trusted by churches. Loved by families.

Built to support safer children's ministry.

ChapelCheck helps churches protect children with secure check-in workflows, guardian records, controlled pickup visibility, and clear attendance data.

It supports your church policies and trained adults. It should sit beside supervision, background-checked leadership, and local safety procedures, not replace them.

Safety support without a complicated morning

The process stays simple enough for volunteers and structured enough for leaders to review attendance, pickup, and guardian details later.

Authorized guardians

Each child can be connected to approved pickup adults, relationship details, private secret keys, and optional ID last-four support.

Daily church codes

Church admins can use separate registration, check-in, and checkout codes when a ministry morning needs more structure.

Signed checkout receipts

Receipts are designed for staff validation while avoiding guardian secret keys, emergency contacts, and unnecessary child information.

Validation before trust

A receipt is only helpful when staff can verify that it matches the completed checkout record.

1

Signed receipt

Checkout creates a signed, expiring receipt token tied to the church and attendance logs.

2

QR validation

Staff can scan the receipt and check the signature before trusting the checkout state.

3

Record match

The receipt must match completed checkout logs before it appears as validated.

4

Privacy-aware

The QR code should not contain guardian secret keys, emergency contacts, or unnecessary child details.

Security workflow FAQ

Is ChapelCheck a replacement for church safety policy?

No. ChapelCheck supports church child safety workflows, but churches still need trained adults, local procedures, and appropriate supervision.

What information should checkout receipts avoid?

Receipts should not expose guardian secret keys, emergency contacts, full guardian contact details, or unnecessary child information.

How does receipt validation work?

A receipt is only treated as validated when its signed token matches completed checkout logs in ChapelCheck.