Safeguarding
Child safety built into the architecture.
Free for up to 50 active members. No credit card required.
PHILOSOPHY
Architecture, not policy
Most church software treats safeguarding as a content moderation problem — scan messages after they are sent, flag suspicious words, hope a human reviews them in time. That approach fails because it depends on perfect policy compliance from every user, every time.
Kinship takes a fundamentally different approach. Sixteen structural mechanisms interlock to make unsafe communication architecturally impossible — not just against policy, but against the physics of the system. An adult without a relationship edge to a minor cannot send a message. Not because a rule says so, but because the permission matrix has no path for that message to travel.
This is the difference between a "no swimming" sign and draining the pool. Structural safety does not depend on compliance. It works even when humans forget, rush, or deliberately try to circumvent it.
"Content moderation asks: did something bad happen? Structural safety asks: is something bad even possible? We build for the second question."
Prevention, detection, and response layers work together so that no single point of failure can compromise child safety. Every mechanism is logged, every override is audited, and every escalation has an SLA.
DEFENSE IN DEPTH
Three layers of protection
No single mechanism is enough. Kinship layers prevention, detection, and response so that each layer catches what the one before it might miss. If prevention fails, detection catches it. If detection is slow, response escalates automatically.
Prevention
The permission matrix engine stops unsafe messages before they are ever sent. Relationship edges must exist between an adult and a minor for any communication to be possible. Image sending is blocked in adult-minor one-to-one conversations. COPPA compliance is enforced with hardcoded age thresholds — not configurable, not overridable. Age-out transitions are handled automatically by the birthday scanner.
Detection
Every adult-minor conversation has an accountability partner observing in real time. Cross-ministry partner assignment prevents collusion. Urgent keyword detection scans messages and triggers parallel notification to the church owner. Pool health is monitored continuously, with automatic fallback through three tiers if the pool becomes thin.
Response
The flag lifecycle state machine ensures every concern moves from open to resolution. A 15-minute acknowledgment SLA means no flag sits unread. Auto-escalation notifies the church owner if a coordinator misses the deadline. Resolution requires notes and creates an immutable audit entry. Messaging suspensions can be applied instantly.
COMPREHENSIVE
Sixteen mechanisms. No gaps.
Every mechanism is structural — built into the system architecture, not bolted on as a policy. Together they form an interlocking safety net where no single point of failure can compromise child protection.
Named, accountable coordinators who receive all escalations and manage the flag queue
Relationship-edge resolver with canSendMessage, hasRelationshipEdge, and classifyMember functions
Group leader, serving team, care case assignee, and campus staff — the only paths for adult-minor messaging
Full pool, degraded mode, and congregation opt-in fallback ensure every conversation has an observer
Anti-collusion measure: accountability partners are always from a different ministry than the adult
Versioned, digitally signed agreements with immutable logging of every signature event
Open → dismissed | unlocked → resolved, with mandatory notes and full audit trail on every transition
Auto-escalation to the church owner if a safety coordinator does not acknowledge a flag within 15 minutes
Real-time scanning with parallel notification to the church owner — no waiting for coordinator review
Under-13 consent requirements enforced with a hardcoded age threshold that cannot be configured or overridden
Birthday scanner automatically injects or removes safeguarding protections as members cross age thresholds
Structured consent collection and tracking for minor participation in messaging and community features
Parents can view their minor children's conversations and receive digest notifications of messaging activity
Granular controls to enable, disable, or restrict messaging capabilities on a per-member basis
25+ action types in an INSERT-only log — no updates, no deletes, no exceptions, permanently retained
Instant suspension of messaging privileges with automatic notification and audit trail entry
GET STARTED
Protect your congregation with Kinship
Sixteen structural safeguarding mechanisms — permission matrix, accountability pools, flag lifecycle with SLAs, COPPA compliance, and an immutable audit trail — included in every Kinship plan. Child safety should never be a premium add-on.
No credit card required. No annual contract. Cancel any time.