Data and privacy
A church hands Munday the most sensitive record it keeps: who is struggling, who asked for prayer, what was said in a room with the door closed. The posture below is a design commitment, not a setting.
This page as markdown: /llm/data-and-privacy.md
The commitments
- Confidential means confidential.
- A prayer request marked confidential is visible to the people it was entrusted to, not to everyone with a login. Munday does not have a mode where the whole staff can read everything.
- Dawn sees what your team already has.
- The AI layer reads the record your church keeps in Munday. It is not given access your team does not already have, and confidentiality carries into it.
- Nothing leaves without a rule you set.
- Every connection out of Munday, to Slack, to a giving platform, to an AI your team uses, moves what a rule you wrote says it moves. There is no default that ships data somewhere you did not choose.
- Any connection is revocable in one click.
- Turning a connection off is a single action, and it takes effect immediately.
- Nobody is scored.
- Munday holds no engagement score, no ranking, no attendance grade. Cards move because a person moved them, and "not yet" is an answer we keep.
- The record is yours.
- What your church puts into Munday belongs to your church, and leaves with you if you go.
Ask us directly
Specifics your IT or board will want, and that we answer directly in a demo rather than in a generality here: where data is stored and in what region, how long it is retained, which sub-processors are involved, what our agreements with model providers say about training, and how access is scoped for staff and volunteers.
Those answers belong in a conversation with your board or IT rather than in a paragraph here, and we give them straight. Book a demo and tell us your size, your current stack, and what's most pressing. We shape a plan from there.
This page states design commitments. It is not a legal agreement, and it does not replace the terms you would sign.