AI Data Use

Enji Guard uses approved third-party AI and coding providers so the Service can run selected audits. We do not train Enji-owned models on your code, and we do not sell it.

To run the work you select, the Service may send selected task context to an AI or coding provider — for example code snippets, file paths, dependency manifests, configuration, logs, and audit findings needed for that task.

• Does not train or operate Enji-owned foundation models on customer content.
• Does not sell customer code or personal data.
• Does not use customer content for unrelated advertising.

Approved providers process selected task context under their own published or contracted data-use and retention terms. Default retention, abuse-monitoring, and privacy controls differ by provider and route.

Because of this, we do not represent that every provider route is zero-retention. Where strict guarantees are required, they are handled through customer-controlled deployments or written agreements.

Self-hosted and customer-controlled deployments can restrict the approved providers and routes the Service uses, including bring-your-own-AI, where you use customer-controlled AI provider routes or credentials so calls run under your own accounts and agreements.

The current list of approved AI and coding providers is available on request and to enterprise customers under review. We keep the list current rather than publishing volatile per-provider terms here.

AI-assisted output can be incomplete or inaccurate and is decision-support, not a guarantee. Review outputs before acting on them. See the Terms of Service for details.