Privacy & scope
Clarity about what MinistryBeacon is—and where it stops.
MinistryBeacon helps churches and small nonprofits build practical cybersecurity readiness through educational guidance. This page explains the kinds of information the service may receive, what it is used for, and what should stay out of the workspace.
The purpose
Practical readiness for the people doing the work.
MinistryBeacon turns everyday knowledge about people, systems, and processes into a shared readiness picture. The workspace can help a ministry team understand its current readiness score, choose useful next actions, prepare handovers, and keep educational policies and checklists moving.
The goal is a calmer, more informed conversation about cybersecurity readiness—not a demand to hand over the keys to the services your organization uses.
What may be in the workspace
Context that helps your team decide what to do next.
Account and contact details
If you create an account or contact us, the service may receive the account, contact, and session information needed to sign in, keep a session working, and respond to you.
Organization and readiness information
Workspace use may include organization details, assessment answers and results, readiness scores, and the dates associated with that work.
Planning and technology context
You may add technology inventory metadata, policy and checklist content, action items, and handover notes so your team can keep its plan current.
Technical and session context
Requests and sessions can include technical context needed to serve the workspace, maintain account access, limit abuse, and investigate service issues. The exact handling can depend on the hosting and account configuration in use.
We use this information to provide the assessment and workspace experience, show readiness and planning context, generate the reports or guidance you request, and support the service. This page does not promise a particular retention or deletion timeline.
Keep secrets out
Readiness context is not a credential vault.
Do not enter operational passwords, API keys, recovery codes, authentication tokens, MFA seeds, payment details, or other service credentials into assessment answers, inventory fields, policies, checklists, or action notes.
Use your approved secure process instead.
MinistryBeacon can help identify that a team needs an access review or a handover; it is not the place to paste the secret that would grant that access.
The right kind of help
Useful guidance, with honest boundaries.
MinistryBeacon provides educational guidance. It is not legal advice, an audit, audit certification, penetration testing, cyber-insurance approval, or a guarantee against incidents. A readiness score is a planning signal based on the information your team provides; it is not a legal or compliance determination.
Your organization remains in charge.
Review recommendations with the people responsible for your organization, its systems, its policies, and its legal or insurance decisions.
Questions about the scope?
Tell us what needs to be clearer.
For questions about these product practices or how to use the workspace, contact the MinistryBeacon team at hello@ministrybeacon.org.
This page describes the product's current practices and boundaries in plain language. It is not legal advice or a substitute for advice specific to your organization.