Develop With Faith
July 30, 2026

The AI and Confidentiality Page Every Faith-Based Coach and Counselor Needs

The question started showing up on discovery calls about a year ago, and it has not slowed down. A prospective client, halfway through a warm conversation, quietly asks a version of the same thing. "Before we go further — do you use AI to take notes? Where do those notes go?" For faith-based coaches, counselors, spiritual directors, and consultants, that question is no longer a technical detail. It is the trust conversation. If your website does not already answer it, your discovery calls are answering it for you, one nervous prospect at a time.

We think it belongs on a page, plainly written, linked from your services and your contact form. Not a legal notice. Not a policy PDF. A short paragraph or two, in your own voice, that a first-time visitor can read in under a minute and feel their shoulders drop.

Why a page, and not just a policy

Every service business we work with has a privacy policy. Almost none of them are read. The AI and confidentiality question is different because it is specific, current, and emotionally loaded. Someone considering hiring you as their coach or counselor is not wondering how you handle cookies. They are wondering whether their prayer requests, their marriage, or their financial fears will end up as training data in a model owned by a company they did not choose. That is a real question, and it deserves a real answer in a place they can find it without hunting.

A dedicated page — we tend to name it something like /confidentiality or /how-we-use-ai — solves two problems at once. It gives the anxious client a place to land before they book, and it gives you a link to send in an email when the question comes up directly. Both matter more than a policy buried in the footer.

What the page should actually say

The best versions of this page we have written share the same shape. There is a short opening about why the page exists. There is a plain-language section about what tools you use and what you do not use them for. There is a section about session notes. And there is a closing paragraph that names the values behind the policy without preaching about them.

The tools section is where most drafts get too clever. Do not list every SaaS product in your stack. Name the categories a client cares about — scheduling, video calls, note-taking, email, transcription — and, for each, say whether AI is involved and whether client content ever leaves an encrypted, HIPAA-adjacent environment. If you use a session-notes tool with a business associate agreement, say so. If you never paste session content into a general-purpose chatbot, say that even more clearly. Clients are not asking for a technical diagram. They are asking whether you have thought about it.

The session-notes section is the one clients read twice. Say what you write down, where it lives, how long it stays, and who can see it. Say whether transcripts of your sessions exist and, if they do, for how long. If you occasionally use an AI tool to help you reflect between sessions, describe the guardrails — anonymized, no identifying details, no direct quotes — in the same tone you would use with a supervisor. Precision here reads as care. Vagueness reads as evasion.

The paragraph that does the emotional work

Somewhere near the end, there should be a paragraph that is not really about AI at all. It is about why confidentiality matters to you as a practitioner, and why the arrival of new tools has not changed that commitment. For faith-based providers, this is where the values quietly show up. Not a Bible verse. Not a mission statement. A sentence like, "The trust our clients extend to us is something we consider sacred, and we treat every decision about new technology through that lens first." That paragraph is what a nervous prospect screenshots and sends to their spouse before booking.

If you write for a specific tradition or clientele — a Catholic spiritual director, a Christian marriage counselor, a Jewish executive coach — you can be more specific about the frame. The rule of thumb we use is that the paragraph should read the same way a good pastoral email reads. Warm, not performative. Certain, not defensive.

Update the page when your tools change

The reason clients trust this kind of page is that it feels current, not templated. A dated line at the bottom — "Last reviewed: July 2026" — is worth the small maintenance overhead. When you add a new tool, revisit the page. When a tool you use changes its data policy, revisit the page. It is a fifteen-minute quarterly habit, and it prevents the far more expensive conversation of a longtime client discovering, six months late, that something changed and you did not tell them.

Most faith-based practitioners we work with resist writing this page at first. It feels like it should be someone else's job — a lawyer's, a compliance officer's, a bigger company's. In our experience it is one of the highest-leverage pages a solo practitioner can write, because it does in ninety seconds what a full discovery call has to do slowly. It signals that you are the kind of person who thought about this before you were asked.

If you have been meaning to draft yours and keep pushing it down the list, we help small faith-based practices shape these kinds of pages — plain language, no legalese, and something you can actually update yourself.

← Back to all posts