ReachWeaver: license, warranty disclaimer and responsible-use notice

Updated 14 October 2026. This notice accompanies the free, experimental ReachWeaver v0.2 software and Claude Code plugin.

Software license controls. ReachWeaver is distributed under the Apache License, Version 2.0. In particular, Sections 7 and 8 set out the warranty disclaimer and limitation of liability. This notice explains the tool’s purpose and the operator’s responsibilities; it does not replace or amend Apache-2.0, impose additional conditions on its copyright permissions, or create a separate negotiated contract merely because someone downloads or runs the software. If anything here conflicts with the license, the license controls. Rights and obligations imposed by applicable law or independently agreed written contracts may also apply.

1. Experimental software; no warranty

The software is provided “AS IS” without warranties or conditions except as required by applicable law or agreed in writing, as described in Apache-2.0 Section 7. Features, AI-generated content, security controls, analytics and publishing integrations can be incorrect, incomplete, interrupted or unsuitable for a particular purpose. The maintainers do not promise accuracy, uninterrupted service, compliance certification, commercial results, reach, likes, account acceptance or fitness for high-stakes uses.

Review the source and test safely before relying on the software. Do not use an untested workflow for critical business or personal decisions.

2. Independent operator; no publishing agency

ReachWeaver is user-operated software, not a hosted social-media management service. Installing it does not make its author or contributors the operator’s employee, agent, publisher, representative, compliance officer, data processor or professional adviser merely by supplying the software. No contributor is appointed to speak or act on a user’s behalf merely by distributing the code, and no user is authorized to act or make promises on the developer’s behalf.

The software runs on the operator’s own computer. Drafts and other state are normally local, and live publishing is disabled by default. An operator must configure an account and permissions, review the exact content and destination, give the required approval and explicitly activate a live send. These controls help prevent mistakes but are not a guarantee against unexpected behavior, compromised environments or third-party failures.

Operators choose their own accounts, audiences, content, schedules, targets, data sources, integrations and applicable settings. No software license grants permission to use someone else’s accounts or content, bypass platform restrictions or violate the law.

3. Responsibility for content and third-party rules

Each operator is responsible, to the extent imposed by applicable law and the agreements they have accepted, for their own decisions, accounts, credentials, data and publishing activity. Before publishing, the operator should:

• Obtain authorization to operate each personal, employer, institutional or client account, and check relevant organizational policies.
• Verify every draft’s factual claims, quotations, rights to use text and media, attribution, audience, destination, preview and accessibility, even when an AI model suggested them.
• Check platform terms, API permissions, rate limits and automation rules, and applicable laws on privacy, data protection, copyright, trademarks, defamation, advertising, sponsorship disclosures, competition, consumer protection and unsolicited communications.
• Respect privacy and opt-out requests, use only lawfully obtained information and avoid impersonation, harassment, deceptive endorsements, fake engagement or unauthorized bulk messages.
• Review a live send on the actual external platform, reconcile unknown outcomes and remove or correct content through the platform when appropriate.

An operator’s independent violation of platform rules or law does not automatically establish that the project’s contributors took part in that violation or are legally responsible for it. This statement does not prevent a third party from bringing a claim, and legal responsibility is determined by applicable law and the facts. The maintainer cannot independently approve or supervise every downstream use, modified fork or account configuration.

4. Independent users, forks and third-party conduct

ReachWeaver’s author publishes source code, not user-created posts or a promise to supervise how people deploy it. Except where the actual facts or applicable law provide otherwise, the original author and other contributors do not choose or control an independent user’s accounts, passwords, contacts, target audiences, media, AI prompts, commands, third-party integrations, stored data, advertising campaigns, final content or publication decisions. Making a tool available does not mean approving or participating in any user’s particular activity.

Independent operators and downstream developers may run, change, combine, host or redistribute the software in accordance with Apache-2.0 and other applicable rights. Their own choices, modifications, configurations, third-party services and operations are not automatically attributable to or authorized by the original author. The original author does not make representations about an independently modified version or about a third party’s deployment, service quality, compliance or security. Redistributions must follow Apache-2.0, including the modification and notice requirements in Section 4. Section 6 does not grant a general right to use the author’s trademarks to suggest endorsement.

Use of ReachWeaver does not grant any user permission to violate another person’s rights, impersonate others, spam, gather data unlawfully, bypass platform restrictions, make misleading endorsements or perform otherwise unlawful acts. The actor and any applicable deployer or operator must determine their own permissions and legal duties. A modified fork or external service must not represent its own obligations, warranties, advice, approvals or actions as those of the original contributors.

These statements describe independent responsibility and the project’s operational boundaries; they are not a blanket waiver of non-waivable duties, proof that the maintainer could never be a legal participant in an incident, or a bar against claims by nonparties. Liability always depends on facts and applicable law.

5. AI and third-party services

ReachWeaver is not affiliated with, endorsed by or sponsored by Anthropic, Claude, any social network or other named integration. External platforms and AI providers apply their own terms, policies, security practices and data handling. The operator is responsible for reviewing and satisfying those terms. The maintainers do not control third-party decisions such as account suspension, API changes, content removal, rate limits or service outages.

Generated content and growth/measurement recommendations are information for human evaluation, not legal, security, financial, medical or other professional advice. The software cannot assess legal compliance in every jurisdiction or guarantee moderation approval.

6. Limitations of liability and damages

To the extent permitted by applicable law and as provided by Apache-2.0 Section 8, contributors limit their liability to users for damages arising from the license or the use or inability to use the software. Potential harms include erroneous, duplicate or unwanted posts; loss of accounts, followers, reputation or revenue; content or copyright disputes; provider sanctions; data loss, credential compromise or security incidents; and claims by third parties.

This is a summary of the existing license, not an independent promise that nobody can sue, an automatically enforceable user indemnity in favor of the author, a guarantee that every injury has no remedy, or a waiver of third parties’ rights. No provision excludes or restricts responsibility where the law prohibits doing so, including applicable rules on intentional or grossly negligent conduct, mandatory public-interest obligations and non-waivable consumer rights. Separate contracts signed by a contributor may establish additional obligations that this notice cannot cancel.

Downstream support or warranties: Under Apache-2.0 Section 9, a redistributor who voluntarily accepts support, warranty, indemnity or other liability obligations must do so on its own behalf and sole responsibility (not on behalf of other contributors) and agree to indemnify, defend and hold contributors harmless for liability or claims arising from those added obligations, as the license states. This applies according to the terms of the license; it is not a new obligation invented by this notice.

7. Privacy, security and support

The maintainer does not currently operate a service that collects local drafts, databases or social credentials automatically. The plugin has network-enabled functions, including its GitHub update notice; external providers may receive connection metadata and, when explicitly used, approved content or credentials. Local state may persist until the operator manages it. The exact data flows and limits are described in the privacy policy and the data lifecycle documentation.

Operators must safeguard account credentials, machines, backups and exported data. Review the security policy, use least-privilege access and report vulnerabilities privately. Maintenance and support are best-effort; no availability, maintenance period, response-time SLA or individual remediation guarantee is offered, except where independently agreed or required by law.

8. No affiliation; notices and changes

Product names and trademarks belong to their respective owners and identify compatibility only. The project may change; users should consult documentation for their installed version and verify current legal and provider requirements before each live publishing workflow.

Key documents: Apache-2.0 license · privacy policy · security policy.

Legal scope: This notice does not alter statutory rights of consumers, data subjects, affected third parties or others, and cannot override the author’s separate contracts. No one can promise that the publication of a disclaimer prevents litigation. A qualified lawyer should assess enforceability for any particular jurisdiction or commercial deployment.