AI Policy

AI comes with severe costs. It uses energy and water, and it is already reshaping what work looks like, including creative and technical work like mine. I don't think ignoring AI makes it go away. I also don't think using it casually or without clear boundaries is the answer.

So, I'm very intentional about where AI shows up in my work.

Where I use AI

Claude helps me draft, organize, and refine website copy. I write based on your materials, goals, audience, and strategy. Claude may help me move faster through early drafts, but I review, edit, and approve every word before it ends up on your site.
Claude helps me troubleshoot WordPress issues. I may use it to debug plugin conflicts, code issues, configuration problems, or other technical challenges that come up during a website project.
Wispr Flow helps me dictate some of my own writing and communication. I use AI voice-to-text to move faster when drafting notes, emails, or internal documentation.
Notion's AI meeting note taker records and transcribes some client calls. I use it to write call recaps, track decisions, and remember what we agreed to.

What I do not use AI for

Designing your website
Creating your graphics or visual identity
Making strategy decisions for your website or organization
Giving final approval to website copy
Replacing human responses to care plan support tickets
Creating AI-generated imagery for your project

All design is manually created. I use real photography, licensed stock imagery, or graphics I create without AI, unless we discuss another approach together.

If you bring AI-generated work to me

Some clients come to me with a logo, brand identity, mockup, image, chart, graphic, or Lovable app that was already made with AI. Here's how I handle that:

AI-generated logos or brand identities: we'll talk through it before I build anything with it. Sometimes it may be fine to use, other times I may flag concerns about originality, quality, accessibility, or long-term usability.
AI-generated mockups or wireframes: I treat them as inspiration, not as files I implement directly. I still design and build your site myself.
AI-generated images, charts, or graphics: we'll decide case by case whether they're appropriate for your site. My default is to use real photography, client-provided visuals, or licensed stock.

AI on your website

Some website features may use AI, depending on the tools you choose. For example, if your site includes multilingual functionality, translations may run through Google Translate or TranslatePress with DeepL integration. These tools use AI or machine translation to automatically translate your site for visitors. If we use tools like this on your site, I'll make sure you understand what they do and where they show up.

Meeting transcriptions and notes

I record and transcribe some client calls using Notion's AI note taker so I can stay focused on the conversation instead of trying to take perfect notes. Transcripts stay in my private Notion workspace and are used only to write call recaps and remind me what we agreed to. I'll let you know when a call is being recorded or transcribed. If you'd rather a specific call not be recorded, tell me and I'll turn it off.

Your information stays private

I don't enter passwords, financial details, private member or donor data, personnel details, confidential internal strategy, or other sensitive information into AI tools. My Claude account is set so conversations are not used to train Anthropic's models. When I use AI for technical troubleshooting, I may describe the issue generally, share a small code snippet, or ask for help interpreting an error. I do not share sensitive credentials or private organizational data.

If you'd rather limit AI use

If your organization has specific concerns about AI, I'm happy to talk through them before we begin. I can often adjust how AI is used in the project, especially around copywriting, meeting notes, and client-facing materials.

The one exception is technical troubleshooting. I default to Ecosia rather than Google for search, and only turn to AI-assisted debugging, using Claude, when I can't find the answer that way. It's one of my debugging tools for WordPress, plugin, and code issues, and I can't offer a blanket 'no AI at all' commitment for technical work as a result.

Last updated: August 2026