Authorized guardians
Each child can be connected to approved pickup adults, relationship details, private secret keys, and optional ID last-four support.
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.
The process stays simple enough for volunteers and structured enough for leaders to review attendance, pickup, and guardian details later.
Each child can be connected to approved pickup adults, relationship details, private secret keys, and optional ID last-four support.
Church admins can use separate registration, check-in, and checkout codes when a ministry morning needs more structure.
Receipts are designed for staff validation while avoiding guardian secret keys, emergency contacts, and unnecessary child information.
A receipt is only helpful when staff can verify that it matches the completed checkout record.
Checkout creates a signed, expiring receipt token tied to the church and attendance logs.
Staff can scan the receipt and check the signature before trusting the checkout state.
The receipt must match completed checkout logs before it appears as validated.
The QR code should not contain guardian secret keys, emergency contacts, or unnecessary child details.
No. ChapelCheck supports church child safety workflows, but churches still need trained adults, local procedures, and appropriate supervision.
Receipts should not expose guardian secret keys, emergency contacts, full guardian contact details, or unnecessary child information.
A receipt is only treated as validated when its signed token matches completed checkout logs in ChapelCheck.