Leveraging AI While Keeping Client Data Private
No one likes busy work, yet it consumes most of our week: follow-up emails, vendor lists, consultation notes, timelines, to-do lists. AI is good at drafting all of it. What stops most planners is the client details. Is it safe to hand an AI a couple's budget, their family situation, and their vendor contracts?
That depends on one thing: where the AI runs.
Where AI runs
Every AI tool runs in one of two places.
On your computer. The program and the model live on your laptop. A recording you drop in is transcribed by your own machine, and the notes are saved in files you control. Nothing has to leave for it to work.
On someone else's computer. Chat apps, browser tools, and cloud note-takers send what you give them to the company's servers. The answer comes back to you, and what you sent is kept under that company's storage rules and terms, which it can change.
Neither one is inherently wrong. You already send client details to other companies every day, through your email, your CRM, and your bank. The point is to choose on purpose instead of by default.
What to keep on your computer
Keep the raw material on your computer: consultation recordings, transcripts, budgets, and the notes where a couple tells you which relatives can't sit together. Send a cloud tool only what you'd be fine putting in an email to a vendor.
That still leaves plenty for the cloud. A chat assistant can translate your standard vendor instructions into Spanish for a venue's staff, turn a venue's rules into a load-in checklist, or build a reusable timeline template, all without seeing a client's private details.
Let AI draft, then check it
AI does get things wrong sometimes, and smaller local models miss more than the big cloud ones. So don't let any AI write straight into your records. Let it draft, then check what it drafted.
That's how consultations work in Trellis Fieldbook. You drop in the recording, and transcription and extraction run on your computer. Fieldbook shows you what it found: the wedding date, the venue, the vendors, and the to-dos. Nothing goes into the wedding record until you confirm it.
When a job needs a bigger model, you can bring one in. Fieldbook has a local connection that apps like Claude Desktop can use to read and update your records when you ask it to. Only what that request needs goes to that app, and everything else stays on your computer.
Your five-minute audit
List every AI tool that touches client details. For each one, answer five questions.
- Where does it run: on my computer, or on the company's servers?
- Does it still work with the Wi-Fi off? If not, it's sending what you give it somewhere.
- Where are my recordings and notes stored, and for how long?
- Who can read them: just me, my team, or the company too?
- Does it learn from what I send, and can I turn that off?
If you can't answer the third or fourth question, start with that tool.
And before you record any consultation, ask the couple. One sentence at the start does it: "Mind if I record this so I can listen to you instead of taking notes?"
Keep the fun part
Knowing where your AI runs is what makes it safe to use. A tool that works on your own computer also doesn't need a monthly fee to keep working, and Fieldbook is a one-time purchase. That's a post of its own.
Use the AI for the busy work. Keep the raw material on your computer, check what it drafts, and spend the time you get back on the part of the job you love: the couples and the day itself.