AI Use Policy

84EM uses AI tools as assistive development tooling, similar to an editor or framework, to improve speed and quality of engineering output.

Current AI providers

Additional AI-powered tools may be used in the development environment (editor integrations, MCP servers, image search). A current inventory is available on request.

84EM uses commercial / API tiers where the option exists, with training opt-out configured where available. Provider-side data handling is governed by each provider’s data processing terms.

Human review

AI-assisted output is reviewed for material correctness before being committed or delivered. Review depth is calibrated to risk: security-sensitive code, database operations, and client-facing deliverables receive line-by-line review; routine refactors and well-tested patterns receive lighter review.

84EM is a solo practice; the principal engineer (31 years of web development experience) performs all review.

Client data handling

84EM maintains a knowledge base for each client engagement. It holds the project record: meeting notes, proposals, contracts, email, project management threads, git commits, documentation, and build summaries. The AI tooling used to do the work reads that record. That is what makes the record useful, and it means client material, including confidential material, is processed by the providers listed above, each acting as a subprocessor for that processing.

84EM uses commercial or API tiers where the option exists, with training opt-out configured where the provider offers it. Client data is not used to train third-party models.

Autonomous AI workflows

Some internal operational tasks, including knowledge base enrichment, monitoring and summarization, run without per-task human review. These operate on the same project record. They do not produce client-facing deliverables.

Client-facing code, content, and communications are produced under engineer review.

Data retention

Local development context (conversation history, session logs) is retained on 84EM systems per the development tooling defaults and is not centrally archived.

Provider-side telemetry and retention follow each provider’s terms. 84EM selects settings that favor data minimization where configurable.

Code provenance

AI-generated code is reviewed before commit. 84EM does not knowingly accept AI output that reproduces identifiable third-party copyrighted code. Open-source dependencies introduced through AI-assisted work are reviewed for license compatibility on the same basis as manually selected dependencies.

Prohibited uses

AI tools are not used at 84EM to:

Subcontractors

When subcontractors or agency partners contribute to client projects, 84EM requires them to handle client data under confidentiality terms consistent with 84EM’s own. Their specific AI tooling and policies are their own, and 84EM does not warrant them. Subcontractor involvement is disclosed to clients before work begins on engagements where subs will have access to client systems or data.

Provider incidents

If an AI provider discloses a security incident affecting 84EM’s usage of their service, 84EM assesses potential client impact and notifies affected clients within 72 hours of confirmed impact.