AI & Automation Disclaimer

Enforcer Labs Private Limited

Effective Date: May 1, 2026
Last Updated: July 3, 2026
Applies To: Enforcer Dashboard Only

1. Purpose

This disclaimer addresses the risks, limitations, and responsibilities associated with the automation capabilities embedded in Enforcer Dashboard and with its limited, optional AI-assisted features. This document is critical for enterprise procurement review and risk assessment.

2. AI in Enforcer Dashboard — Scope and Boundaries

2.1 Compliance Findings and Evidence Are Not AI-Generated

Enforcer Dashboard's drift detection, policy evaluation, compliance scoring, and compliance report artifacts are produced by a deterministic, rule-based policy engine. No large language model (LLM) or other generative AI system is used to generate, evaluate, or alter compliance findings, compliance scores, or evidence records.

2.2 Optional AI-Assisted Features

Separately from the evidence path described in Section 2.1, Enforcer Dashboard includes limited, optional AI-assisted convenience features, currently limited to:

(a) Evidence narrative synthesis — AI-assisted drafting of narrative summaries from compliance evidence already produced by the deterministic policy engine;

(b) Natural language Q&A — a conversational interface for asking questions about compliance status.

These features are ancillary conveniences. Their outputs are not compliance evidence, do not create or modify compliance findings, and are subject to the disclosures in Section 3.

3. AI Limitations — Critical Disclosures

The following disclosures apply to the AI-assisted features described in Section 2.2 and to any AI-assisted capabilities introduced in the future.

3.1 No Guarantee of Accuracy

AI-GENERATED OUTPUTS MAY CONTAIN ERRORS, INACCURACIES, OMISSIONS, OR INCOMPLETE ANALYSIS. AI models are probabilistic in nature and may produce outputs that are incorrect, misleading, or inconsistent. Enforcer Labs does not guarantee the accuracy, completeness, reliability, or suitability of any AI-generated output.

3.2 Not Legal, Regulatory, or Professional Advice

AI-GENERATED OUTPUTS DO NOT CONSTITUTE LEGAL ADVICE, REGULATORY GUIDANCE, AUDIT OPINIONS, OR PROFESSIONAL COMPLIANCE CONSULTING. All AI outputs should be reviewed by qualified compliance professionals, legal counsel, and domain experts before being relied upon or acted upon.

3.3 Third-Party AI Models

The AI-assisted features rely on AI models and services configured by Customer, which may be third-party services (e.g., the OpenAI API) or Customer-hosted model-serving infrastructure. Where a third-party provider is configured, Enforcer Labs:

(a) does not control the training data, behavior, or outputs of third-party AI models;

(b) is not responsible for changes to third-party AI model behavior, availability, or pricing;

(c) cannot guarantee the continued availability or performance of third-party AI services;

(d) cannot guarantee that third-party AI outputs will comply with specific regulatory requirements.

3.4 Data Processing by AI

When the AI-assisted features are used:

(a) Data submitted to AI models may be processed by third-party AI providers, subject to those providers' terms and privacy policies;

(b) Customer is responsible for ensuring that data submitted to AI features does not include data prohibited by Customer's policies or applicable regulations;

(c) Customer should review the data handling practices of configured AI providers.

For self-hosted deployments: Customer controls which AI providers are configured and what data is submitted to them. Enforcer Labs has no access to or control over this configuration.

4. Automation Capabilities

4.1 Scope of Automation

Enforcer Dashboard may include automation capabilities, including:

(a) Drift detection — automated scanning and identification of configuration deviations;

(b) Approval-gated remediation workflows — proposed corrections of detected drift that execute only when (i) the relevant environment has been expressly placed in remediation mode by Customer, and (ii) a human approver has approved the specific action. The Software does not remediate autonomously;

(c) Compliance checks — automated evaluation of infrastructure against defined controls;

(d) Alerting — automated notification of compliance events and deviations;

(e) Scheduled tasks — recurring automated compliance scans and reports.

4.2 Automation Risks

CRITICAL: AUTOMATED ACTIONS, INCLUDING REMEDIATION, MAY MODIFY CUSTOMER'S PRODUCTION INFRASTRUCTURE AND CARRY SIGNIFICANT RISKS.

Customer acknowledges and accepts the following risks:

(a) Service disruption — automated changes may cause service outages, degraded performance, or application failures;

(b) Data loss — automated actions may result in deletion, corruption, or modification of data;

(c) Security exposure — automated configuration changes may inadvertently create security vulnerabilities;

(d) Cascading failures — automated changes in one component may trigger failures in dependent systems;

(e) Incorrect remediation — the Software may propose or execute remediation actions that are technically incorrect or inappropriate for Customer's environment;

(f) Stale data — automated actions may be based on outdated infrastructure state information.

5. Customer Obligations for Automation

Customer shall:

(a) Implement human-in-the-loop controls — use approval gates and review workflows for all critical remediation actions before they are executed;

(b) Test in non-production first — validate automation behavior in development/staging environments before enabling in production;

(c) Maintain rollback capability — ensure that infrastructure changes can be reversed in the event of adverse outcomes;

(d) Limit blast radius — configure automation scope to minimize the impact of potential errors;

(e) Monitor execution — actively monitor automated actions and their outcomes;

(f) Maintain backups — ensure current backups exist before enabling automated remediation;

(g) Review audit logs — regularly review the Software's audit logs for unexpected automated actions;

(h) Train personnel — ensure that personnel responsible for the Software understand the automation capabilities and associated risks.

6. Enforcer Labs' Non-Liability for Automation

ENFORCER LABS SHALL NOT BE LIABLE FOR ANY DAMAGE, LOSS, COST, OR EXPENSE ARISING FROM OR RELATED TO:

(a) Automated actions executed by the Software within Customer's Environment;

(b) Customer's decision to enable, configure, or execute automated remediation;

(c) The accuracy or appropriateness of automated remediation proposals;

(d) Infrastructure changes resulting from automation, whether or not approved by Customer;

(e) Customer's failure to implement human-in-the-loop approval controls;

(f) Interactions between automated actions and Customer's existing infrastructure, applications, or configurations.

7. Recommended Safeguards

Enforcer Labs strongly recommends that Customer implement the following safeguards:

8. Contact

Enforcer Labs Private Limited
Email: legal@enforcer-cca.com

This document is subject to attorney review. AI and automation liability exclusions are critical for enterprise compliance platforms and must be validated for enforceability in each target jurisdiction.