Church data should not wander.

Public website

The central website may store administrator accounts, support requests, download activity, training progress if that feature is enabled later, and the minimum technical logs needed to keep the service reliable. A final production privacy policy should name the actual analytics, payment, email, and hosting providers in use.

Self-hosted suite

The installed suite runs on infrastructure chosen by each church. The church is responsible for user access, backups, retention, server security, lawful data handling, and responding to requests concerning its ministry records.

Support requests

Support requests should never include student names, medical details, care notes, passwords, database exports, or other private ministry content. Technical logs should be reviewed and redacted before they are submitted.

Optional telemetry

Telemetry is intended to report limited technical facts, not ministry activity. Read the dedicated telemetry page for the planned fields and exclusions.

Read the telemetry model