Stoneglow Digital
How we use AI
Updated 29 August 2026
A note on transparency
AI is now part of how most studios work. We think clients deserve to know exactly how, and where the lines are drawn. This page sets out our position clearly so there is no guesswork.
Where we use AI
We use AI as a tool to support the work, not to replace it. Research and discovery: synthesising market context, summarising long documents, and accelerating early-stage strategic thinking. First-pass drafts: generating initial copy structures and content outlines that our team then rewrites, refines, and approves before anything reaches you. Code acceleration: using AI-assisted coding tools to write boilerplate, scaffold components, and catch errors faster, with every line reviewed and tested by our developers before it ships. Image generation for placeholders and concepts: used for exploration and mockups, never for final production assets without clear disclosure. Internal operations: meeting notes, project documentation, and administrative work.
Where we do not use AI
Some things are too important to delegate to a machine. We do not use AI for final copy on your website without human rewriting and approval. We do not use it for strategic decisions about your brand, audience, or positioning. Client communication stays human: when we email you, a person wrote it. We never generate fake testimonials, fabricated case study outcomes, or invented credentials. And it does not replace the judgement of our designers, developers, and strategists.
What stays human
The work that determines whether your website actually performs is human work. Strategy. Design decisions. Editorial judgement on your copy. Architecture choices. Performance engineering. The craft that earns the price tag is made by people, not prompts.
Our commitment to you
We disclose AI use openly: if you ask whether something was AI-assisted, we tell you. We review and own every output: if AI helped produce it and we shipped it, we stand behind it as our work. We refuse AI training crawlers: our robots.txt blocks GPTBot, ClaudeBot, CCBot, Google-Extended and others outright, so the work we publish for you does not quietly become training data. Answer engines that cite their sources are still welcome, because those send people back to you. We update this page as the tools and our use of them evolve.
Why this matters
The premium end of web development is going to split into two camps over the next few years. Studios that use AI thoughtfully to do better work faster, and studios that use AI to do cheaper work cheaper. We are firmly in the first camp. This policy is how we hold ourselves to it. Questions about how we use AI on your project? Ask any time.