Effective September 13, 2026
Ministry Follow-Up is operated by Compassion Innovations LLC, 7901 4th St N, Suite 300, St. Petersburg, FL 33702. This policy covers the Ministry Follow-Up platform at ministryfollowup.com and the church web addresses served through it. Text-message notifications have their own notice at SMS privacy.
A church that uses Ministry Follow-Up owns the information its congregation gives it: who asked for care, what they said, who responded, and what happened. We hold that information on the church’s behalf and act on its instructions. The church decides who may see it, how long it is kept, and when it is removed. In data-protection language, the church is the controller of that information and we are its processor.
We are the controller of a smaller set: the account and billing information of the people who sign up, pay, and administer the service, and the operational records that keep the platform running.
Account information. The name, work email address, telephone number, church name, and role of each person who is invited into or signs up for the platform. We use it to create accounts, send operational mail such as invitations and password resets, and reach an administrator about their church’s account.
Church care information. Records a church creates or brings in: people in the church’s directory, care requests and the answers given on its forms, assignments, notes, follow-up reports, and the history of what was done. Some of this is sensitive by nature. It is entered by the church, belongs to the church, and is visible only to the people that church has authorized.
Enquiries. What you send us through a request-a-call or enquiry form: your name, email address, telephone number, church name, and anything you choose to write. We use it to reply to you and to arrange a conversation. We do not add enquirers to a marketing mailing list.
Billing information. Payments are taken by Stripe. Card numbers are entered on Stripe’s own pages and never reach our servers or our database. We hold the subscription record: which plan, which billing period, whether it is current, and Stripe’s own identifiers for the customer and subscription.
Operational records. Server logs, delivery records for each notification we send, and records of failures. A visitor’s IP address on our public enquiry forms is stored as a one-way hash rather than as the address itself; it exists so we can tell how many submissions came from one place in a day, and it cannot be turned back into an address.
We do not sell information about any church, any member of a congregation, or any visitor to this site. We do not share it with advertisers, we run no advertising network on our pages, and we do not use a church’s care records to train machine-learning models. We do not read a church’s care records except when that church asks us to help with a specific problem, or where we are compelled by law.
We set a session cookie when somebody signs in, so the platform knows who they are on the next page. We set no advertising cookies and no third-party analytics cookies. A responder opening an assignment through a private link is not asked to sign in and is given no tracking cookie.
We use a small number of service providers to run the platform. Each is bound by its own contract to handle the information only as we instruct.
A church may also connect services of its own, such as Planning Center, its own Microsoft 365 mailbox, or Square. Those connections are made by the church, on the church’s instruction, using the church’s own credentials, and information flows to them only because the church asked for it. Each of those services has its own privacy policy, which governs what it does with what it receives.
We may also disclose information where we are required to by law, or where it is necessary to protect somebody from harm.
A volunteer who receives an assignment opens it through a private link and is shown only that one assignment. They are given no account, no password, and no access to the church directory or to any other care request. The link stops working when the assignment is reassigned, and it expires.
Church care records are kept for as long as the church keeps its account, because a care history that quietly deletes itself is of no use to the church that relies on it. A church may remove records itself at any time through the platform.
When a church closes its account, we delete its records within 30 days of the request, except where we are required to keep something for accounting or legal reasons. Backups are overwritten on their own schedule and a deleted record may persist in one for up to 30 further days. Delivery records for notifications and ordinary server logs are kept for up to 12 months.
If you are a member of a congregation and want to know what a church holds about you, or want it corrected or removed, ask that church: it is their record and they can act on it immediately. If you contact us instead, we will pass your request to the church and tell you we have done so.
If you hold an account with us, write to info@ministryfollowup.com and we will give you a copy of your account information, correct it, or delete it.
How the platform separates one church from another, what is encrypted, and how to report a vulnerability are set out at Security.
Ministry Follow-Up is sold to churches and used by their staff and approved volunteers. We do not knowingly create accounts for anybody under 16. A church’s own records may include minors in its congregation; those records are the church’s, entered under the church’s own policies and its own relationship with those families.
If we change this policy in a way that affects how a church’s information is handled, we will email the administrators of every active church account before it takes effect, and change the date at the top of this page.
Compassion Innovations LLC, 7901 4th St N, Suite 300, St. Petersburg, FL 33702. info@ministryfollowup.com.