Effective October 28, 2026. These terms cover the Claude, Codex and Perplexity plugins and optional publisher usage-reporting service; they do not change the license of other LogForge products.
Provided by 17811365 Canada Incorporated, using the LogForge brand. Contact: adan@logforge.dev.
The LogForge Claude plugin source is distributed under Apache License 2.0 as stated in its LICENSE file. These service terms do not replace that source license or change licenses of other LogForge products.
These terms cover the LogForge Claude, Codex and Perplexity plugins and its optional publisher usage-reporting service. You may install and use the plugin to inspect and instrument applications and infrastructure you own or are authorized to access. You remain responsible for securing your deployment, obtaining necessary permissions, and reviewing proposed changes before applying them.
The plugin does not grant access to another person's systems, bypass LogForge permissions or approvals, or unlock paid capabilities. Your connected LogForge deployment and any separately licensed components remain subject to their applicable terms and licenses. Anthropic, OpenAI and other third-party services are governed by their own terms.
Diagnostic outputs reflect the code, checks, filters, and paths actually executed. A passing check does not establish that every path or production condition was tested. Review source context and use appropriate backups and testing before making operational changes. The plugin and diagnostic results are provided as available, without a promise of uninterrupted service, complete coverage, or error-free results. These statements do not limit rights or remedies that applicable law does not permit us to exclude.
To the fullest extent permitted by applicable law, the plugin, optional reporting service, and diagnostic outputs are provided “as is” and “as available,” without warranties or conditions of any kind, express, implied, or statutory, including merchantability, fitness for a particular purpose, accuracy, availability, security, and non-infringement.
To the fullest extent permitted by applicable law, 17811365 Canada Incorporated and its directors, officers, employees, and contractors are not liable for any direct, indirect, incidental, special, consequential, exemplary, or punitive loss or damage arising from or related to use of, inability to use, or reliance on the plugin, reporting service, or diagnostic outputs. This includes loss of data, profits, revenue, business opportunities, or goodwill; downtime; security incidents; and damage resulting from code changes, commands, remediation, or AI-generated suggestions, even if the possibility of such loss was advised. These exclusions apply regardless of the legal theory of a claim, including contract or negligence.
Nothing in these terms excludes or limits liability for fraud, wilful misconduct, or any liability, warranty, right, or remedy that applicable law does not allow to be excluded or limited. Mandatory consumer protections continue to apply. If an exclusion is unenforceable, it applies only to the extent legally permitted.
You retain ownership of your code and diagnostic data. Connecting a deployment allows the selected AI client to receive the tool results you request; its own data terms also apply. Minimal aggregate publisher usage reporting is enabled by default in the versions identified in the privacy notice, with disclosure before use, a persistent off switch, and preservation of explicit disabled settings. Disabling it does not limit plugin functionality. Its fields, retention, disabling, and deletion-request process are explained in the plugin privacy notice. The publisher reporting service does not receive your application logs, source code, feature tags, or .logforge report contents.
This plugin does not collect payments or create a subscription. Separately purchased LogForge products or third-party services may have their own charges. Support is available through LogForge plugin support; no response-time or availability guarantee is included with this plugin.
You can stop using the plugin by disabling or uninstalling it. Disable optional publisher reporting separately to stop new queued reports; uninstalling does not delete reports already received. Contact us using the privacy notice for deletion requests. We may update the plugin and these terms; published revisions will carry an updated effective date. Separate signed agreements and applicable component licenses continue to govern their own subject matter.