People and roles
Ask which roles can view, change, export, or remove each kind of record, and how those permissions are reviewed over time.
Data stewardship
Ask clear questions before trusting any church platform
Church records carry people's stories. This page outlines the areas we recommend reviewing with Relius or any provider. Contact us for current technical details and plan-specific commitments before making a security or compliance decision.
Review areas
Build a security conversation around your church
Needs vary by team, plan, and the information you choose to store. Use these prompts during evaluation and ask Relius for written confirmation of the details that matter to you.
Sensitive information
Review how pastoral notes, care requests, giving records, and family information are separated and shared.
Activity and accountability
Confirm what administrative activity is recorded, who can review it, and how long that history is available.
Authentication and sessions
Discuss sign-in safeguards, session handling, password expectations, and the options available for your selected plan.
Export, deletion, and recovery
Ask for the current process, format, timing, and limits for data exports, deletion requests, backups, and recovery.
Service operations
Request current details about hosting, encryption, monitoring, incident response, service providers, and availability commitments.
Before migration
Agree on stewardship, not just software
Product controls are only one part of protecting people. Document who owns each decision, what your church will store, and how staff access changes when roles change.
- 1
Which records does our church consider especially sensitive?
- 2
Who needs access today, and who should approve future access?
- 3
What information would we need during an incident or staff transition?
- 4
What export and retention expectations should be documented before migration?
Get the details your review requires
Tell us about your church, plan, and review requirements. We'll share the current information available for your evaluation rather than asking you to rely on a generic promise.
Start a security conversation