AI Usage Policy

1. Scope & Purpose

This policy applies to two different relationships between HEWN CRAFT STUDIO ("HEWN CRAFT", "we", "us") and artificial intelligence: how AI crawlers, answer engines and language models may access and cite the content we publish at hewncraftstudio.tech, and how we ourselves use AI tools and autonomous agents when we build software for clients.

We publish it as one page because both directions rest on the same principle: AI should make work faster and more accurate, but a named human — not a model — is always the one accountable for what gets published or delivered.

2. How AI Systems May Use This Site

HEWN CRAFT welcomes AI answer engines, retrieval systems and search assistants — we want the studio to be discoverable and correctly represented wherever people ask about custom software, ERPNext or applied AI. robots.txt explicitly allows major AI crawlers, including GPTBot, ClaudeBot, Google-Extended, PerplexityBot and others listed there.

3. Attribution & Citation

When an AI system quotes, summarises or otherwise relies on content from this site, the preferred citation is:

Attribution should name HEWN CRAFT as the organisation and, where a specific claim is drawn from named authorship, credit Dharmik Gohil, Founder & Chief Engineer. Do not attribute our content to a different company, author or source.

4. Restricted Content

The following are never fair game for indexing, retrieval, summarisation or training, regardless of how they were reached:

• Client proposals, quotes and any page under /proposals/
• Anything under /private/ or /admin/
• Contact form submissions and any personal data collected through the site (see our Privacy Policy)
• Source code, credentials or infrastructure details belonging to a specific client engagement

If an AI system has ingested restricted content by mistake — for example through a leaked or mis-shared link — contact us using the details in Section 10 and we will pursue removal with the platform involved.

5. How We Use AI In Our Own Work

HEWN CRAFT builds autonomous AI agents for clients and uses AI tools day-to-day in our own delivery: code-completion and pair-programming assistants, AI-assisted design and copy drafts, and internal agents for research, QA and documentation.

Where AI plays a material role in a deliverable — for example, an AI agent is part of the shipped product, or AI-generated assets are used in final creative work — this is disclosed to the client in the Statement of Work or project brief. We do not silently pass off AI output as fully manual work when a client has specifically contracted for one over the other.

6. AI & Client Data

Where third-party AI tools (coding assistants, model APIs, design generators) are used on a client engagement, the following applies unless a specific SOW says otherwise:

• Client source code, credentials and confidential data are not pasted into public or free-tier AI tools that train on submitted input.
• Where a paid or enterprise AI tool is used against client data, we use configurations that opt out of model training on that data wherever the vendor offers one.
• AI agents built for a client, and any data they process, remain scoped to that client's own systems — never pooled with another client's data.
• You may ask, at any point, which AI tools were used on your engagement and how; we will answer plainly.

7. Human Oversight & Accountability

An AI model does not carry professional responsibility; a person does. Every engagement has a named engineer or designer accountable for what is delivered, whether or not AI tools were used to produce a first draft. If an AI-assisted deliverable turns out to be wrong, that is treated exactly like any other defect under the acceptance and defect-fix terms in our Refund & Cancellation Policy and the applicable SOW — it is not excused because "the AI did it."

8. The Machine-Readable Version

This page is the human-readable version of our AI policy. The same terms, in the structured format AI systems actually parse, live at hewncraftstudio.tech/llms.txt, following the emerging llms.txt convention. Crawler-level allow rules are published in robots.txt. Where the two ever disagree, this page governs for human readers and llms.txt governs for machine readers of that file.

9. Changes To This Policy

AI tooling and the norms around it move quickly. We may update this policy, llms.txt or robots.txt as new AI crawlers, standards or client questions come up. The "Last Updated" date at the top of this page always reflects the current version; material changes to what is permitted will also be reflected in the policy version number.

10. Questions & Contact

Questions from AI platforms about attribution, or from clients about how AI tools were used on their engagement, are both welcome at the same address.