> For the complete documentation index, see [llms.txt](https://dualguard.gitbook.io/dualguard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dualguard.gitbook.io/dualguard/disclaimer.md).

# Disclaimer

#### **What DualGuard is**

DualGuard provides security review programs and related services designed to help teams identify and remediate vulnerabilities in onchain systems. These services can materially reduce risk, but they do not eliminate it. Web3 systems operate in adversarial environments, and failures can still occur even after review.

#### **What DualGuard is not**

No guarantees. DualGuard does not and cannot guarantee that a smart contract will be free of vulnerabilities, that an exploit will not occur, or that any particular finding will be identified during a review.

No financial coverage. DualGuard does not currently offer insurance, reimbursement guarantees, or any coverage-style product.

**What protocol teams are paying for**

Security review outcomes are probabilistic. Protocol teams engaging DualGuard programs are paying for access to a structured security process and for the outputs of that process, including findings, severity assessments, and remediation guidance. Security research is not deterministic: reviewers may miss issues, severity may be debated, and outcomes depend on scope, code maturity, time constraints, and the protocol’s architecture and integrations.

Scope matters. Results apply only to the defined scope and version(s) reviewed. Code changes, new deployments, upgrades, integrations, configuration changes, and operational decisions after the review can materially change the effective risk profile.

**Bug bounty availability**

DualGuard currently supports pre-launch bug bounties only.

Post-launch bug bounties are not available yet.

Protocol teams should not treat any review or pre-launch bounty as a substitute for strong engineering, operational controls, monitoring, incident response planning, or disciplined risk management.

**Guidance on communications**

Protocol teams should avoid public statements that imply guarantees, certainty of outcomes, or assured financial recovery. Any description of DualGuard's services should be accurate, qualified, and consistent with the applicable written terms.

**Independent diligence**

Protocol teams remain solely responsible for their code, deployments, operations, and user communications. Teams should conduct their own diligence and risk assessment and should not rely on DualGuard services as the sole control for preventing loss.

**Legal disclaimer**

*This documentation is provided for informational purposes only and does not constitute legal, financial, tax, investment, or other professional advice. Nothing on this page forms or modifies any contract, agreement, warranty, or guarantee. Any services or deliverables are governed solely by the applicable written agreements and program terms. To the extent permitted by law, DualGuard disclaims all warranties, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. In the event of any conflict between this documentation and the applicable agreements or program terms, the agreements and program terms control.*