AI Use Policy
I use AI tools to work faster. Here are the written rules that keep your data, your deliverables, and the truth safe while I do.
Last updated: August 11, 2026
A policy that only exists when someone asks is not a policy. This one is public, dated, and binding on every project I take.
Why This Page Exists
I use AI tools in my delivery workflow, and I think anyone hiring me deserves the rules in writing before they ask. Most agencies either hide their AI use or hand their name to it entirely. I do neither: the toolchain is real, it is governed, and this page is the governance.
The Rules
Rule 1: Your data never feeds someone else's machine without your written say-so
Client content, customer data, and personal information do not enter third-party AI systems without the client's prior written approval. Not for drafting, not for analysis, not for convenience. If a task would benefit from it, I ask first and you decide.
Rule 2: No deliverable ships on AI's word
Every deliverable is verified by me against the project's quality gates before it reaches you: code is reviewed and type-checked, rendered output is checked on real screen sizes, copy is edited by hand, accessibility and performance are measured. AI output that has not been verified is a draft, and drafts do not ship.
Rule 3: Accountability never delegates
I am the builder of record on every project. AI compresses the mechanical share of the work; it does not replace judgment, design decisions, or ownership of the result. When you call, the person who answers is the person responsible, and "the tool did it" will never be a sentence you hear from me.
Rule 4: The honesty rules apply to the machines too
My standing rules ban invented statistics, fabricated reviews or testimonials, synthetic clients, and fake case studies. Concept work is labelled as concept work everywhere it appears. AI makes fabrication cheap, which is exactly why the ban applies regardless of what produced it.
Rule 5: Ask me anything
Any client can ask where AI was used in their project and get a plain answer. Generated imagery I use is art-directed and post-processed by me, and I will tell you which images those are if you want to know.
What I Use It For
Acceleration of mechanical work: bulk code transformations, verification sweeps, research synthesis, first drafts that I then edit and often rewrite. The judgment calls, the design direction, the words that carry my name, and everything a client pays for stay human-owned.
What I Will Not Use It For
Processing your customers' personal information without your written approval. Producing "proof" of anything. Replacing the verification steps that make the work trustworthy. Auto-publishing anything client-facing without review. These are not aspirations; they are standing rules the workflow is built around.
AI as a Product Feature
Separate from my own workflow, I also build AI features into client sites where they serve visitors. Those ship with the same governance: guardrails, cost controls, and honest limits stated up front. If a feature cannot be made trustworthy, it does not ship.
I also build sites to be AI-answer ready: structured, schema-rich, and machine-readable, so that when someone asks an AI assistant about your business, your own site is the clearest source available. The honest limit: nobody can promise how a third-party assistant behaves, and I will never pretend otherwise.
Related: Trust & Security, Privacy Policy. Questions? Ask me directly.
