Your church's information, handled the way you would handle it.

We do not sell it, rent it, trade it, or hand it to advertisers. Not your members, not your donors, not your children. There is no version of this business where a church's roster becomes somebody's mailing list, and we do not use your data to train AI models.

Your church's data belongs to your church. Export all of it whenever you want. Ask us to delete it and we delete it. Neither one waits on your bill.

Five companies operate the parts this runs on, because the software cannot exist without them. Vercel serves the site, Supabase stores the database, Stripe processes payments, Resend delivers email, and Anthropic runs the AI drafts. Each one handles your church's data to run this service and for nothing else. None of them may market to your people or sell on what they hold.

One more party is worth naming, and it is a delivery route rather than a place your data sits. If a leader turns on phone notifications, the alert goes out through whoever makes their browser, Google for Chrome, Apple for Safari, Mozilla for Firefox, because that is the only route a notification has to a phone. We seal the contents before they leave us, and only that leader's own device holds the key, so the browser maker carries an envelope it cannot open.

If that ever changes, it changes here first, in writing, and active churches hear from us before it takes effect.

thechurch.tech is used by churches, about their own members, and that includes children in their children's ministry. Parents and guardians give this information to their church, and the church is the controller of it: the church decides what is collected, who on its team may see it, and when it is removed. thechurch.tech is the processor that stores and serves that data for the church. We do not collect children's information for ourselves, we do not market to children, and we do not use children's data for anything except running the church's own check-in and care tools.

How a child leaves a room is the part that matters most, so here is exactly how it works. A leader releases a child to one named adult who is already on that child's authorized list, and only after verifying that adult in person, either by recognizing them or by checking a photo ID. There is no pickup code, no kiosk, no printed name tag, and no QR code at the door. A restriction a parent has filed stops the release outright, whatever else the screen says. A child on hold is released only by the kids director, never by the volunteer at the door.

Each of those moments is written to a record your church can read back later: the child received into the room, the release and who took them, every refusal and the reason for it, and any exception a leader opened. That record is what a church needs if it is ever asked what happened, and it is why we keep it.

When a leader needs to reach a family about a child, the text goes from that leader's own phone, in their own Messages app, on their own tap. We do not operate a texting number and the product has no way to send a text by itself, which is deliberate and permanent for anything touching kids. What the church keeps is the outcome it needs to be able to prove, that the family was reached and whether the child was coming, not the conversation between them.

The product has no parental-consent screen today, and this page will not describe one that does not exist. Parents hand this information to their church, and the church answers for it.

If you are a parent and want your family's records corrected or removed, ask your church. They control the records and can remove them. If you get stuck, email us and we will help you and your church sort it out.

The leaders your church has authorized, and only within the access your church gives them. A kids check-in volunteer sees the roster for their room; they do not see giving records. Access in the product is permission-based and actions are logged.

Our own team can reach your data only to run the service, fix a problem, and help you. We do not browse church data for any other reason. What we will never do with it is at the top of this page.

The product uses an AI service to draft follow-up messages and morning summaries. Drafts are exactly that: drafts. Nothing is sent to your people unless a human at your church taps send. The data used to prepare a draft is used for that draft and is not used to train any AI model. That promise is made here, on this page. The five things the AI will never do, and the record of what the software logs, are written down in the AI covenant.

Your data is stored in a Postgres database hosted by Supabase in the United States, encrypted in transit. The site and its scheduled jobs run on Vercel. Payments are handled by Stripe; we never see or store your card number.

Your church controls its data. A pastor or admin exports the whole thing from Settings, free, as often as they like: every table your church owns, including the custody records and the check-in history, in one download. Because that file holds your giving and your children, we ask for your second factor before it starts. That is a lock on the door, not a fee, and it is the same whether your bill is paid or not.

You can ask us to delete your church's account and records by emailing us. Families ask their church to remove or correct their records, because the church controls them. When a church leaves, it takes its people with it. Leaving is as easy as joining; that is on purpose.

The public demo is a made-up church with made-up people. Nothing you click in the demo creates, changes, or touches any real person's record. We count anonymous demo events (things like "demo started", tied to a random id, never to a name) so we know whether the demo is working. That is all the demo saves.

Every cookie we set is there to run the product for you. They keep you signed in, carry you through a password reset, remember which church you are working in, remember that you are in the demo, let a signed-in account revisit the sample church without touching its own data, and give a registered family a secure, expiring session for kids check-in plus a hold on their half-finished registration. None of them follow you anywhere else. There are no advertising trackers and no third-party analytics scripts on this site.

If this policy changes in a way that matters, we will update the date at the top and tell active churches by email before it takes effect. Privacy questions go to cody@westtexas.ai.