Claude commercial or consumer account for construction files: controller, training and retention questions

Identify the product and contract first

Claude Free, Pro and Max are consumer products, while Claude for Work and the Anthropic API sit under commercial terms. The interface name alone does not establish which contract applies, especially when staff use personal accounts or Claude Code. Record the account owner, plan, organisation, login method and route used by any third-party tool. Do not copy a commercial no-training or processor statement onto a consumer account, and do not assume an employee's paid subscription is an enterprise workspace.

Compare training choices without oversimplifying

Anthropic's current consumer notice says chats and coding sessions may be used for model improvement when the user allows it, with related retention consequences. The notice explicitly excludes commercial services from that consumer change. For construction files, turn this into an account policy: which plans may receive tenders, invoices, plans, photos or personal data, and which content is prohibited. Verify settings periodically; a screenshot of one user's preference is not an organisation-wide control.

Retention differs by product and feature

Anthropic's commercial privacy guidance says API inputs and outputs are normally deleted from its backend within thirty days, subject to stated exceptions, while saved commercial conversations are retained to provide the product experience until controlled or deleted. Features such as files and agreed zero-retention arrangements have separate boundaries. Map local copies, project knowledge, exports, feedback and safety exceptions as well. A provider deletion statement does not remove the contractor's own legal retention duties.

Create an approved route for sensitive files

Use Anthropic's current commercial retention guidance and consumer terms update as provider sources. Define an approved account, data classification, human reviewer and deletion test. This comparison does not imply that Alfie integrates with or uses Claude. Enfin's governed actions and provider claims are separate questions and should remain separate in architecture and customer communication.

Turn the decision into a controlled workflow

Do not leave this control in an isolated note. Record who checks the inputs, which source supports the decision, which exception requires human review and who confirms the final action. Enfin can bring customer, project, quote and invoice context together, while Alfie can prepare or execute actions within verified permissions. That is not a substitute for legal or tax advice, but it makes the contractor's control repeatable. Explore Enfin, review pricing, or discuss the workflow.