Terms Of Service
Effective date: 7 June 2026
Enji Guard is provided by Enji.ai. For legal, privacy, security, or support questions, contact us at [email protected].
1. The Service
Enji Guard is a product interface for software reliability, security, and quality automation. It may be used by individuals, companies and other organizations, and maintainers of open-source projects. It helps customers connect repositories and websites, run audits, review reports, schedule improvement jobs, and create GitHub issues or pull requests where enabled.
Selected actions are executed by the Enji Fleet agents orchestrator, which handles agent execution, runbooks, tasks, schedules, artifacts, authentication, and permissions.
2. Authority To Use Enji Guard
You may use Enji Guard only for repositories, projects, websites, domains, and systems that you own or are authorized to manage or test.
If you connect a GitHub organization, repository, project, website, or domain, you represent that you have authority to act on behalf of the owner.
If you use Enji Guard for a company or other organization, you represent that you are authorized to bind that organization to these Terms.
If you use Enji Guard for an open-source project, you represent that you have maintainer authority or other permission required to connect the repository, run checks, and create related GitHub output for that project.
3. Customer Content
You retain ownership of your code, repository content, website targets, task inputs, reports, generated outputs, and other Customer Content.
You grant Enji.ai a limited license to process, store, transmit, display, analyze, and generate outputs from Customer Content only as needed to provide, secure, support, and operate Enji Guard and the Enji Fleet agents orchestrator.
You are responsible for ensuring that your Customer Content and use of Enji Guard comply with applicable laws, third-party rights, repository-hosting terms, cloud-provider terms, and internal policies.
4. AI And Automation
Enji Guard does not train or operate its own foundation models. Enji Guard uses approved third-party AI model providers and coding tool providers under the providers’ public data-use and retention terms unless a separate written agreement says otherwise.
Customers with strict provider, residency, or retention requirements can contact Enji.ai about a separately priced and contracted on-premises or customer-controlled deployment. In that model, the customer is responsible for choosing, approving, configuring, and monitoring the AI model providers or coding tools connected to the customer’s environment.
AI and agent outputs can be incomplete, inaccurate, unsafe, or outdated. You are responsible for reviewing, testing, approving, and accepting any report, recommendation, issue, pull request, code change, or other output.
Enji Guard should not be treated as a substitute for professional engineering, security, legal, compliance, or operational judgment.
Unless a future feature clearly says otherwise, Enji Guard and the Enji Fleet agents orchestrator do not merge pull requests or deploy code automatically.
5. GitHub App Actions
When you install or use the Enji Guard GitHub App, you authorize Enji Guard and the Enji Fleet agents orchestrator to access selected repositories and perform the actions you configure.
Depending on the feature, this may include reading repository contents and metadata, inspecting branches and commits, creating reports, opening GitHub issues, opening pull requests, posting review comments, or adding related workflow output.
You can revoke GitHub App access from GitHub. After revocation, future tasks, schedules, and GitHub actions may fail or pause. Existing reports and history may remain for security, investigation, auditability, and product-history purposes unless you send a deletion request to [email protected].
More detail is available in GitHub App Permissions.
6. Authorized Testing
Some Enji Guard features, including Auto-pentest and active website checks, may send active requests to a target website.
You may run active checks only against systems that you own or have written permission to test. You may not use Enji Guard to scan, probe, attack, or test third-party systems without authorization.
Active checks may cause temporary errors, slowdowns, logs, alerts, WAF events, or security-monitoring events. You are responsible for confirming that your hosting provider, organization, and affected stakeholders permit the testing.
Auto-pentest consent applies only to the specific project, website/domain, and selected active-check scope you confirm. Enji Guard may require renewed confirmation if the target, scope, ownership, project owner, organization, or connection state changes, or if 12 months have passed since the previous confirmation.
Destructive testing, denial-of-service, credential stuffing, malware, data exfiltration, persistence, lateral movement, and testing outside the authorized scope are prohibited.
More detail is available in Authorized Testing.
7. No Security Guarantee
Enji Guard reports are informational and are intended to help you find, prioritize, and remediate risks.
Enji Guard does not guarantee that all vulnerabilities, defects, compliance issues, supply-chain risks, or operational issues will be found. False positives and false negatives are expected.
You remain responsible for your own security, compliance, testing, review, deployment, and incident-response decisions.
8. Acceptable Use
You must not use Enji Guard to:
- access, scan, test, or modify systems without authorization;
- bypass authentication, authorization, usage limits, rate limits, or tenant isolation;
- upload malware or illegal content;
- exfiltrate data from third parties;
- perform denial-of-service or destructive testing;
- violate GitHub, hosting-provider, cloud-provider, model-provider, or other third-party terms;
- use generated output to harm third parties;
- use prompt injection, task instructions, repository content, configuration, scripts, or other inputs to make agents perform dangerous, unrelated, abusive, or harmful actions;
- reverse engineer, scrape, benchmark, or competitively monitor the service without written permission;
- use Enji Guard to train competing models or extract model-provider data in violation of provider terms.
9. Demo, Pro, Paid Plans, And Beta Features
Demo accounts may have limits on projects, repositories, websites, runs, schedules, members, and other features.
Self-serve paid plans and payment processing are planned but are not part of the public Terms. Enji Guard does not name a billing or payment processor in these Terms.
If a customer needs paid access, support, or a custom arrangement before self-serve billing is available, Enji.ai may provide it under a signed order form, statement of work, or separate agreement. If signed terms conflict with these public Terms, the signed terms control for that customer.
Beta, preview, or experimental features may change, fail, be rate-limited, or be removed.
10. Suspension And Termination
Enji.ai may pause, suspend, limit, or terminate access to Enji Guard, tasks, schedules, GitHub actions, public summaries, or other features if we believe there is abuse, account compromise, security risk, legal risk, non-payment, provider-limit risk, or violation of these Terms.
If Enji.ai detects or reasonably suspects a security incident, abuse, malicious prompt injection, harmful agent instruction, or attempted misuse of the service, Enji.ai may investigate relevant repository content, generated artifacts, task inputs, logs, and related records. Enji.ai may preserve evidence and escalate serious incidents to appropriate law-enforcement or regulatory authorities when required or appropriate.
You may stop using Enji Guard at any time. You remain responsible for revoking third-party access, including GitHub App access, where applicable.
11. Disclaimers
Except where a signed agreement says otherwise, Enji Guard is provided on an “as is” and “as available” basis.
Enji.ai disclaims warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted operation, error-free operation, and complete security coverage to the maximum extent permitted by law.
12. Changes
We may update these Terms as Enji Guard changes. The effective date identifies the current version.
13. Governing Law
These Terms do not name a governing-law jurisdiction or dispute venue. Those terms may be handled in customer-specific signed agreements.
