Church Response

Privacy Policy

Effective October 1, 2026 · Version 2026-10-01

This policy explains what information Church Response collects, how it is used, who it is shared with, and the choices you have. Church Response is provided by Risk Strategy Group, LLC, doing business as Church Response ("RSG," "we," "us"). It covers the Church Response phone app and the website at churchresponse.com.

In plain terms: your church puts its safety team's information into Church Response, and the church controls it. We use it only to run the service. We do not sell it, we do not use it for advertising, and we do not track you across other websites.

1. Your church controls its records

Church Response is used by churches and ministries to run their safety teams. The church decides who is on its team, what is entered, and who can see it. For most questions about your information, such as correcting or removing it, start with your church's safety team lead or administrator. We will also help if you contact us.

2. What we collect

Account information: your name, email address, phone number if given, and a password. Passwords are stored in scrambled (hashed) form. We cannot see them.

Team records your church enters: your name, contact details, role, teams, whether you serve on an armed team, notes, training dates and records, files uploaded as proof of training, policy sign-offs, and documents your church writes or uploads.

Schedule information: the posts and services you are scheduled for, your answers, days you mark as away, sub requests, and shifts you sign up for.

Duty and phone app information: when you go on and off duty, the post and radio you check out, alerts you send or answer, team chat messages, and incident reports and their additions.

Location: while you are on duty, the app shares your phone's current location with your church team. When you go off duty, that live location is removed. When you send an alert, the location attached to that alert is saved as part of the alert record so the church has an accurate account of what happened.

Device information: if you allow notifications, a notification token for your phone and whether it is an iPhone or Android, so we can send alerts and reminders to it.

Demo requests: if you ask for a demo on our website, the name, church, email, phone, and location you type in.

Records of agreements: when you agree to these terms or to the resource library notice, we record your name, the date, and the version you agreed to.

Technical logs: our hosting providers keep standard logs, such as IP address, browser type, and the time of a request, to keep the service running and secure.

We do not collect Social Security numbers, payment card numbers, or dates of birth through Church Response at this time.

3. How we use it

  • to run the service: sign-in, schedules, reminders, alerts, the duty log, training records, and documents;
  • to send the emails and phone notifications the service depends on, such as invites, schedule requests, reminders, and alerts;
  • to keep the service secure, including a history of changes that cannot be edited;
  • to give support your church asks for; and
  • to meet legal obligations.

We do not sell personal information. We do not use it for advertising. We do not use it to build profiles of you for any other purpose.

4. Who can see it

Your church: what you can see and what others see about you is set by your church. For example, team members see who is serving with them, church leads see training status and the duty log, and documents are shown only to the roles the church chooses.

RSG: our staff do not read a church's records except to give support the church asks for, to keep the service secure, to investigate misuse, or when the law requires it.

Service providers who run parts of Church Response for us, only as needed to provide it:

  • Supabase (database, sign-in, and file storage);
  • Vercel (website and server hosting);
  • Resend (sending email);
  • Expo (delivering phone notifications through Apple and Google);
  • Anthropic (only when a church lead uses "Draft With AI" to write a document; the answers typed into that form are sent to create the draft); and
  • Cloudflare (website address and email forwarding).

Legal reasons: we may share information if the law requires it, such as a valid subpoena or court order, or when needed to protect someone's safety or our legal rights.

Business transfer: if RSG is merged, sold, or reorganized, information may transfer to the new owner under this policy.

5. Cookies

The website uses cookies only to keep you signed in and to remember small settings. We do not use advertising cookies or outside tracking tools.

6. How long we keep it

We keep a church's records while the church uses Church Response, because they are the church's safety record. When a church stops using the service, its administrator may request an export within 30 days. After that, we may delete its records, except where the law requires us to keep them. Backups are replaced on a rolling basis and may hold copies for a limited time after deletion.

The history of changes is kept for as long as the church's records are kept, and entries cannot be edited.

7. Security

Information is encrypted while it travels between your device and our servers. Access is limited by church and by role, private files are opened only through short-lived links, and changes are recorded. No system is perfectly secure, and we cannot guarantee that information will never be accessed without permission. If we learn of a breach that affects your information, we will notify your church and, where the law requires, you.

8. Children

Church Response is for adults who serve on church safety teams. It is not meant for children, and we do not knowingly collect information from children under 13 through accounts. Incident reports written by a church may mention a minor. The church is responsible for how it records and protects that information.

9. Your choices

  • You can turn off phone notifications and location permission in your phone's settings. Some features, such as live location on duty, will not work without them.
  • You can ask your church to correct or remove your information, or to remove your access.
  • You can contact us at help@churchresponse.com to ask what information we hold about you, or to ask us to correct or delete it. Some records may be kept where your church or the law requires it, such as an incident report or the history of changes.

10. Changes to this policy

We may update this policy. When we make a material change, we will ask you to agree again in the app or on the website, and the date at the top will change.

Contact

Risk Strategy Group, LLC

doing business as Church Response

550 S Harbin Dr #123

Stephenville, TX 76401

help@churchresponse.com