Terms of Service

Guardian Posse AI Platform — Government-Grade Terms & Conditions by CPWE AI

Effective: March 4, 2026 Version: 3.7 Last Updated: March 4, 2026
NIST Aligned CMMC Guidance FAR/DFARS Export Controlled Arkansas Law
Enterprise & Government Agreement
These Terms of Service govern your use of the Guardian Posse AI Platform, operated by CPWE AI. By accessing any of our domains—guardianposse.com, cpwe.ai, or ai-comic-studio.com—you agree to be bound by these terms.
Section 1

Acceptance of Terms

By accessing or using the Guardian Posse AI Platform (“Platform”), including any of our domains (guardianposse.com, cpwe.ai, ai-comic-studio.com), associated APIs, mobile applications, or any services provided thereunder, you agree to be bound by these Terms of Service (“Terms”). If you disagree with any part of these Terms, you may not access the Platform.

Legally Binding Agreement

These Terms constitute a legally binding agreement between you (“User,” “you,” or “your”) and CPWE AI (“Company,” “we,” “us,” or “our”). By creating an account, accessing tools, or using any Platform feature, you confirm that you have read, understood, and agree to these Terms and our Privacy Policy.

If you are accepting these Terms on behalf of an organization, government entity, or other legal entity, you represent and warrant that you have the authority to bind that entity to these Terms.

Section 2

Service Description

Guardian Posse is an enterprise and government-grade AI platform operated by CPWE AI. The Platform provides a comprehensive ecosystem of AI-powered tools and services:

12 Specialized AI Agents

The Guardian Posse multi-agent system for orchestrated task execution across domains.

Comic Artist Studio

AI-powered comic creation, character design, and visual storytelling tools.

Merch Creator

Merchandise design and print-on-demand integration for creative assets.

EPB Bullet Writer

AI-assisted Enlisted Performance Brief bullet generation for military personnel.

Cybersecurity Command Centers

NextGen Security, NIST, CMMC, and PCAP analysis dashboards.

Voice & Phone Agents

AI-powered voice assistants and phone agent deployment systems.

Curriculum Builder

AI-driven educational content and curriculum generation tools.

Visual Inspection Reports

Automated visual inspection documentation and reporting.

Dashboard Builder

Custom analytics dashboards and data visualization tools.

Agent Orchestra System

Multi-agent orchestration, workflow automation, and AI coordination.

Multi-Provider AI

Access to OpenAI, Anthropic, Google Gemini, Perplexity, and xAI models.

Code Generation & Analysis

AI-assisted software engineering, code review, and project scaffolding.

Relay Agent Fleet

Deploy and manage security relay agents on client infrastructure for continuous monitoring.

Active Defense Center

Threat actor investigation, attacker profiling, and automated counter-measures.

Risk Management

Risk registers, tabletop exercises, SOW generation, and compliance assessments.

Enhanced Relay Installer v3.0

Full-automation deployment scripts for Windows, Linux, and macOS with 12-agent fleet, SSL, and security hardening.

CertBot SSL Manager

Automated SSL certificate provisioning via Sectigo CA with renewal, status checks, and revocation.

Physical Pen Test Command Center

30-device hardware security arsenal with C2 mesh networking, ICS/SCADA safety controls, and AI-powered engagements.

RF & Wireless Security

Spectrum analysis, Bluetooth surveillance, RFID/NFC assessment, and Sub-GHz testing capabilities.

Splunk SIEM Integration

Enterprise security event management with HTTP Event Collector forwarding for centralized threat visibility.

Zapier Compliance Automation

10-event webhook pipeline forwarding relay status, compliance posture, and security alerts to Zapier workflows.

Zapier Macro Engine

8 pre-built automation macros for event-triggered actions across Slack, email, CRM, and ticketing systems.

Relay Compliance Map

Fleet visualization with NIST compliance overlay for real-time relay posture awareness.

OpenClaw AGI Security Bridge

Security scanning of third-party OpenClaw deployments with 6 scan types and NIST compliance mapping.

OpenClaw Relay Bridge

Security sidecar monitoring with behavior analysis and compliance enforcement for OpenClaw agents.

Section 3

Free Access & Donations

3.1 Free Platform Access

The Guardian Posse AI Platform is currently provided free of charge. There are no subscription fees, usage fees, or mandatory payments required to access and use the Platform’s features.

3.2 Optional Donations

Users may make voluntary donations to support the continued development and maintenance of the Platform. Donations are processed securely through Stripe. All donations are non-refundable and do not entitle donors to any additional features, priority support, or special privileges beyond what is available to all users.

3.3 No Guarantee of Perpetual Free Access

Service Modifications

CPWE AI reserves the right to modify, suspend, or discontinue any part of the Platform at any time, with or without notice. We may introduce paid tiers, usage limits, or premium features in the future. Continued use of the Platform after such changes constitutes acceptance of the modified terms.

Section 4

User Authentication & OAuth

Replit OAuth Integration

Authentication for the Guardian Posse AI Platform is provided through Replit’s secure OAuth system.

4.1 Account Requirements

  • A valid Replit account is required for Platform access
  • You must provide accurate and complete registration information
  • You are responsible for maintaining the security of your account credentials
  • One account per individual user
  • You must be at least 13 years of age to create an account

4.2 OAuth Permissions

By authenticating via Replit OAuth, you grant the Guardian Posse AI Platform access to:

  • Basic profile information (name, email, profile image)
  • Persistent login sessions
  • User identification for platform personalization and feature access

4.3 Account Responsibility

You are solely responsible for all activity that occurs under your account. You must immediately notify CPWE AI at james@cpwe.biz if you suspect unauthorized access to or use of your account.

Section 5

Government & Military Tool Usage

CRITICAL DISCLAIMER — EPB Bullet Writer & Military Tools
The EPB Writer and all government/military-related tools are provided for ADVISORY AND ASSISTIVE PURPOSES ONLY. All AI-generated content must be independently verified by the user.

5.1 EPB Bullet Writer Advisory Notice

  • All AI-generated EPB bullet statements, accomplishment narratives, and performance content are advisory only and serve as drafts for human review
  • Users are solely responsible for verifying the accuracy, completeness, and appropriateness of all EPB statements before submission
  • The EPB Writer is not a substitute for professional military evaluation guidance, mentorship, or official Air Force writing resources
  • AI-generated EPB content does not represent the official position, guidance, or endorsement of the United States Air Force, Department of Defense, or any government agency

5.2 Classification & Controlled Information

DO NOT Enter Classified or CUI Data

Users must NOT enter any classified information, Controlled Unclassified Information (CUI), For Official Use Only (FOUO) data, or any information restricted by government classification guidelines into any Platform tool. The Guardian Posse AI Platform is NOT an official USAF, DoD, or U.S. Government information system and is not authorized to process classified or controlled data.

5.3 Non-Affiliation Disclaimer

The Guardian Posse AI Platform and CPWE AI are not affiliated with, endorsed by, or officially connected to the United States Air Force, Department of Defense, or any branch of the U.S. Government. Any military-related tools are provided as independent, third-party productivity aids.

Section 6

Cybersecurity Tools Disclaimer

Authorized Use Only
All cybersecurity tools provided on the Platform, including but not limited to the Security Arsenal 42 toolkit, PCAP analysis, OSINT capabilities, red team/blue team/purple team tools, SIEM integrations, API Overwatch monitoring, penetration testing tools, and compliance scanners, are intended for authorized use only.

6.1 Authorization Requirements

  • Users must have proper authorization before using security testing tools against any system, network, or infrastructure
  • PCAP analysis tools must only be used on network captures you are authorized to analyze
  • OSINT tools must be used in compliance with all applicable laws and regulations
  • Penetration testing capabilities must only target systems for which you have written authorization

6.2 Compliance Assessment Tools

  • NIST compliance assessment results are informational and educational only and do not constitute official NIST assessments or certifications
  • CMMC readiness evaluations provide guidance only and are not official CMMC assessments or certifications from an authorized C3PAO
  • Security posture assessments and compliance scoring are advisory tools, not authoritative compliance determinations

6.3 Limitation of Responsibility

CPWE AI is not responsible for any misuse of cybersecurity tools provided on the Platform. Users assume full responsibility for ensuring their use of security tools complies with all applicable federal, state, and local laws, as well as organizational policies and regulations.

Section 6b

Relay Agent Deployment & Client Infrastructure

6b.1 Relay Agent Purpose & Scope

  • Relay agents are software components deployed on authorized client infrastructure
  • They perform security monitoring, static analysis, network forensics, and compliance scanning
  • Relay agents communicate with the Guardian Posse platform via authenticated JWT tokens
  • The platform deploys a fleet of 12 specialized AI agents: SecuritySentinel, DocuGenius, AiOracle, DataWizard, UXWhisperer, PerformancePro, CloudCaptain, CodeGuardian, NetSentinel, ComplianceChief, ThreatHunter, and IncidentCommander

6b.2 Client Infrastructure Authorization

Authorization Required
Users must have explicit authorization from the infrastructure owner before deploying relay agents. Relay agents must only be deployed on systems the user owns or has written authorization to monitor. CPWE AI is not responsible for unauthorized relay deployments.

6b.3 Enhanced Installer v3.0 — Getting Started

The Enhanced Relay Installer provides fully automated setup scripts for Windows, Linux, and macOS. Here is what you need to know before running the installer:

Step-by-Step: Running Your Installer

1. Download the script from the Relay Installer dashboard. Your browser will save it to your Downloads folder.

2. Find the downloaded file. On most computers, open your file manager and look for Downloads in the left sidebar, or press Win+E (Windows) / open Finder (Mac) and click Downloads.

3. Windows users: Right-click the .ps1 file and select “Run with PowerShell”, or open PowerShell as Administrator, type cd $HOME\Downloads and press Enter, then type the filename and press Enter.

4. Linux / Mac users: Open Terminal, type cd ~/Downloads and press Enter, then type bash followed by the script filename and press Enter.

5. Python requirement: The installer needs Python 3.8 or newer. If you don’t have Python installed, the script will tell you and provide a download link (python.org/downloads).

6b.4 What the Enhanced Installer Does

The installer runs a 10-phase automated pipeline:

  1. Pre-flight checks — verifies your system meets requirements
  2. Environment variables — securely stores your relay credentials
  3. Python setup — ensures Python and required packages are installed
  4. Relay client — installs the Guardian Posse relay software
  5. 12-agent fleet — deploys all 12 specialized security agents
  6. SSL/CertBot — sets up HTTPS certificates for secure connections (optional)
  7. Security hardening — configures firewall rules and security settings
  8. Auto-service — registers the relay to start automatically when your computer boots
  9. Health check — runs an 8-point test to confirm everything is working
  10. Uninstaller — creates a removal script you can run anytime to cleanly remove everything

6b.5 Data Collection by Relay Agents

  • System inventory data (hardware, OS, installed software)
  • Configuration drift detection and baseline comparisons
  • Security scan results and vulnerability findings
  • Network traffic metadata and anomaly detection
  • Health metrics and heartbeat data
  • All data transmitted via encrypted channels (TLS 1.2+)

6b.6 Credential Security

How Your Credentials Are Protected

Relay credentials (JWT tokens, relay ID) are stored as environment variables on your machine — not in plain text files that anyone can read. On Windows, they are stored as User-level environment variables. On Linux and macOS, they are stored in a secure .env file with restricted permissions (only your user account can read it). Credentials are never sent to third parties.

6b.7 Relay Agent Deactivation

  • Users can deactivate or remove relay agents at any time using the uninstaller script created during installation
  • Upon deactivation, relay data is retained for 90 days then purged
  • JWT tokens are immediately revoked upon relay deregistration
  • The uninstaller removes the relay client, agent fleet, service registrations, and environment variables from your system
Section 6c

Active Defense & Threat Investigation Terms

6c.1 Active Defense Scope

Active Defense tools investigate threat actors targeting your infrastructure. This includes IP lookup, WHOIS analysis, reputation scoring, and AI-powered attacker profiling.

6c.2 Legal Counter-Measures

The platform can generate abuse reports, cease & desist notices, and law enforcement referral templates. These are TEMPLATES ONLY and do not constitute legal action. Users must review and send independently.

6c.3 Honeypot Traps

Users may deploy honeypot traps (SSH, Web, DB, SMB, RDP, IoT). Honeypots must only be deployed on infrastructure you own or control. CPWE AI is not liable for any interactions honeypots attract.

6c.4 Responsible Use

Defensive Use Only
Active defense tools must be used defensively and in compliance with applicable laws. Users must NOT use these tools for offensive operations, harassment, or illegal surveillance.
Section 6d

Physical Penetration Testing & Hardware Security Terms

30-Device Arsenal — Authorized Use Only
The Physical Pen Test Command Center provides access to a 30-device hardware security arsenal. All devices and engagement tools must only be used with explicit written authorization from the target system owner.

6d.1 Device Categories & Authorization

  • USB Implants: Bash Bunny, USB Rubber Ducky, O.M.G. Cable, USB Armory, P4wnP1 A.L.O.A. — must only be deployed on authorized systems
  • Network Devices: WiFi Pineapple, Packet Squirrel, LAN Turtle, Shark Jack, Throwing Star LAN Tap, Alfa WiFi Adapter, GL.iNet Slate Plus — authorized network testing only
  • Keystroke/Video Capture: Key Croc, Screen Crab — requires explicit consent and legal compliance with wiretapping/surveillance laws
  • RF/Wireless: HackRF One, RTL-SDR v4, YARD Stick One, Ubertooth One, Crazyradio PA — must comply with FCC regulations and applicable radio frequency laws
  • WiFi Offensive/Defensive: Pwnagotchi, ESP32 Marauder, DSTIKE Deauther Watch, WiFi Coconut — WiFi deauthentication and monitoring tools must only target authorized networks
  • RFID/NFC/Access Control: Flipper Zero, Proxmark3 RDV4, iCopy-X — badge cloning only with property owner authorization
  • Passive Monitoring: Signal Owl — passive traffic analysis on authorized networks only
  • Hardware Security Research: GreatFET One — hardware debugging and firmware extraction only on authorized devices
  • Command & Control: Hak5 Cloud C² — fleet management and remote device coordination for authorized engagements only
  • Hardware Resilience Testing: USB Kill v4 — USB surge protection testing must only target test equipment with explicit authorization; destructive testing acknowledged

6d.2 ICS/SCADA Safety Requirements

Industrial Control System Safety

Devices flagged as ICS-Unsafe (active attack tools) must NEVER be deployed against industrial control systems, SCADA networks, or operational technology (OT) environments without explicit ICS safety certification. Only ICS-Safe passive devices may be used in industrial environments. All ICS engagements must comply with IEC 62443 and Purdue Model safety classifications.

6d.3 C2 Mesh Networking

  • Command and Control (C2) mesh networking between devices must only operate within the authorized engagement scope
  • C2 channels must be encrypted and must not interfere with production network operations
  • All C2 traffic is logged and must be included in engagement reports

6d.4 RF Compliance

  • All RF transmission devices (HackRF One, YARD Stick One, Crazyradio PA) must comply with FCC Part 15 and applicable international radio regulations
  • Users must not transmit on frequencies they are not authorized to use
  • Spectrum analysis and passive reception (RTL-SDR) do not require transmission authorization
  • Bluetooth monitoring (Ubertooth One) must comply with applicable electronic surveillance laws

6d.5 Evidence Handling

  • All captured data (keystrokes, network traffic, video, RF signals) must be handled as sensitive engagement evidence
  • Evidence must be encrypted at rest and securely transmitted to the client
  • Evidence retention follows engagement contract terms (default: 12 months) and must be securely destroyed upon expiration
  • Users must maintain chain of custody documentation for all physical evidence
Section 6e

Browser Extension Terms

6e.1 Extension Purpose & Scope

  • The Guardian Relay Browser Extension is a Chrome/Chromium Manifest V3 extension that provides browser-based monitoring and control of relay agents
  • The extension communicates exclusively with the user’s configured Guardian Posse platform instance
  • Core capabilities include: relay status monitoring, security alert notifications, command dispatch, and quick-access platform navigation

6e.2 Data Handling

  • All extension data (platform URL, preferences) is stored locally in chrome.storage.sync within the user’s browser profile
  • The extension does not collect, transmit, or share any data with CPWE AI or third-party services
  • No content scripts are injected into web pages — the extension operates solely through its popup interface and background service worker
  • API authentication uses the same session-based authentication as the main platform dashboard

6e.3 Permissions & Access

Minimal Permissions: The extension requests only the permissions necessary for its core functionality: storage (save preferences), notifications (desktop alerts), and alarms (periodic status polling). Host permissions are required to communicate with your platform instance.

6e.4 Installation & Removal

  • The extension is distributed as a downloadable ZIP file from the Guardian Posse platform for side-loading via Chrome Developer Mode
  • Users can remove the extension at any time through their browser’s extension management page
  • Upon removal, all locally stored extension data (preferences, cached relay status) is automatically deleted by the browser
  • Removing the extension does not affect relay agents, platform data, or account status

6e.5 Disclaimer

  • The extension is provided as a convenience tool and does not replace the full platform dashboard
  • CPWE AI is not responsible for browser compatibility issues, extension conflicts, or data loss resulting from browser updates
  • The extension requires an active, authenticated session on the Guardian Posse platform to function
Section 6f

SSL/CertBot Certificate Management Terms

6f.1 CertBot SSL Manager Purpose

The CertBot SSL Certificate Manager automates SSL/TLS certificate provisioning for relay agent deployments and client infrastructure using the Sectigo Certificate Authority (CA).

  • Available certificate operations: issuance, renewal, status check, and revocation
  • Supported web server types: Apache, Nginx, Standalone, and pip-based installations
  • Certificate automation is provided as a convenience tool to simplify HTTPS setup on your servers

6f.2 Credential Security

Secure Credential Handling

Sectigo EAB (External Account Binding) credentials used for certificate issuance are stored as encrypted platform secrets. Generated CertBot scripts reference environment variables — credentials are never hardcoded into scripts. You must set the required environment variables on your server before running any generated script.

6f.3 User Responsibilities

  • You must own or have administrative control over any domain for which you request an SSL certificate
  • You are responsible for properly configuring your web server and DNS records for certificate validation
  • Certificate renewal is your responsibility — the platform provides renewal scripts but does not automatically renew certificates on your behalf
  • Revoked certificates must be replaced promptly to maintain secure connections

6f.4 Limitations & Disclaimer

  • SSL certificate issuance depends on the Sectigo CA and is subject to their policies, rate limits, and availability
  • CPWE AI is not responsible for certificate issuance failures, validation errors, or CA outages
  • Generated scripts are provided “as-is” and should be reviewed before execution on production systems
  • The CertBot SSL Manager is restricted to admin-level platform access

6f.5 Getting Started with CertBot

Quick Start Guide

1. Navigate to the CertBot SSL Manager from your admin dashboard.
2. Enter your domain name and select your web server type (Apache, Nginx, etc.).
3. Choose an operation (install, renew, check status, or revoke).
4. Download the generated script and save it to your server.
5. Set the required environment variables on your server, then run the script.
6. The script will handle the rest — installing CertBot, requesting your certificate, and configuring your web server.

Section 6g

Splunk SIEM Integration Terms

Enterprise SIEM Forwarding
Guardian Posse supports Splunk Enterprise integration via HTTP Event Collector (HEC) for centralized security event management across your security operations center.

6g.1 Splunk Integration Scope

  • Guardian Posse forwards platform security events to your organization's Splunk instance via HEC
  • 12 event categories are supported: security, compliance, threat intelligence, agent activity, network, relay, CRM, system, OSINT, red team, blue team, and physical penetration testing
  • Events are routed to dedicated Splunk indexes with category-specific sourcetypes for optimal search and correlation
  • Integration requires administrator configuration of HEC URL and authentication token

6g.2 Data Forwarding Responsibilities

  • Users are responsible for configuring and maintaining their Splunk deployment, including index creation, retention policies, and access controls
  • CPWE AI does not have access to, monitor, or store data in your Splunk instance
  • Event forwarding is best-effort; CPWE AI does not guarantee delivery of all events during network outages or Splunk unavailability
  • Users must ensure their Splunk instance complies with applicable data residency and retention regulations

6g.3 Relay Agent Splunk Forwarding

  • Client-deployed relay agents can independently forward events to Splunk without routing through the platform
  • Relay-to-Splunk configuration is the user's responsibility and operates under the same terms as platform-to-Splunk forwarding
  • Relay event forwarding includes task results, OSINT findings, red team operations, and health monitoring data

6g.4 Security & Credentials

HEC Token Security

Splunk HEC authentication tokens are stored encrypted on the platform and are never exposed in API responses, client-side code, or application logs. Tokens are transmitted only in server-to-server HTTPS requests to your Splunk endpoint. Users should rotate HEC tokens periodically in accordance with their organization's security policies.

6g.5 Disclaimer

The Splunk SIEM integration is provided for enterprise security visibility and does not constitute a managed SIEM service. CPWE AI is not responsible for Splunk licensing, infrastructure costs, or any actions taken based on events forwarded to Splunk. Splunk is a registered trademark of Splunk Inc.; Guardian Posse is an independent integration and is not endorsed by Splunk Inc.

Section 6h

Security Arsenal 42 Terms

Enterprise Security Toolkit
The Security Arsenal 42 integrates 42 security tools across 13 categories including OSINT, Red Team, Blue Team, Purple Team, SIEM, Network, Web Application, Credential, Wireless, AI Red Team, Forensics, Compliance, and API Overwatch.

6h.1 Scope of Security Arsenal

  • The Security Arsenal provides tool registry, configuration, and orchestration for 42 integrated security tools
  • Tools are categorized by function: OSINT & Reconnaissance (SpiderFoot, Recon-ng, theHarvester, Shodan, Sherlock, Maltego), Red Team (Nmap, Nuclei, Metasploit, SQLMap, Gobuster, Sliver C2, Empire, Impacket), Blue Team (Suricata, Zeek, YARA, Sigma, Velociraptor, osquery), Web Application (OWASP ZAP, Nikto, Wapiti, Burp Suite), SIEM (Wazuh, Graylog, ELK Stack), Purple Team (MITRE Caldera, Atomic Red Team, ATT&CK Navigator), Network (Wireshark, tcpdump, Netcat), Credential (Hashcat, John the Ripper, Hydra), Wireless (Aircrack-ng), AI Red Team (PyRIT, Garak), Forensics (Volatility, Autopsy), API Overwatch (API Monitoring, API Fuzzer), and Compliance (Compliance Scanner Pro)
  • Each tool includes MITRE ATT&CK technique mappings and NIST 800-53 control mappings for compliance tracking

6h.2 Authorization & Legal Use

  • All offensive security tools (Red Team, Purple Team, Credential) must only be used against systems, networks, and infrastructure for which the user has explicit written authorization
  • OSINT tools must be used in compliance with applicable privacy laws including GDPR, CCPA, and local regulations
  • Users are solely responsible for ensuring their use of Security Arsenal tools complies with all applicable laws and organizational policies
  • CPWE AI does not endorse or encourage unauthorized security testing, hacking, or intrusion

6h.3 Open-Source SIEM Integration

  • The platform provides API connectors for Wazuh, Graylog, and ELK Stack alongside the existing Splunk integration
  • Users are responsible for deploying, configuring, licensing, and maintaining their own SIEM infrastructure
  • CPWE AI provides connector configuration only and does not manage third-party SIEM deployments
  • Wazuh, Graylog, Elasticsearch, Logstash, and Kibana are trademarks of their respective owners

6h.4 Third-Party Tool Trademarks

All tool names, logos, and trademarks referenced in the Security Arsenal belong to their respective owners. Guardian Posse provides integration and orchestration capabilities and is not affiliated with, endorsed by, or sponsored by any third-party tool vendor unless explicitly stated.

6h.5 Security Operations Process

The 10-phase Security Operations Process (Reconnaissance → Scanning → Exploitation → Credential Assessment → Detection → SIEM Correlation → Purple Team Validation → API & Network Overwatch → Forensics → AI Security & Compliance) is provided as a framework and best-practice guide. Users should adapt the process to their organization's specific risk profile, compliance requirements, and operational needs.

6h.6 MCP Tools & Offensive Security Intelligence

The platform provides 59 Model Context Protocol (MCP) tools across 13 categories, accessible via the MCP Connections Hub (admin-only execution). The following terms apply:

  • HexStrike Offensive Security Tools (pentest target profiling, attack chain building, vulnerability scanning, credential auditing, report generation, CTF solving) function as an intelligence and planning layer. They analyze user-provided data and generate recommendations but do not execute actual exploits, network attacks, or unauthorized access attempts
  • OpenClaw Agent Fleet MCP exposes the 12-agent fleet as MCP-compliant tools for external AI clients. Agent invocations are subject to the same authorization and acceptable use policies as direct platform usage
  • Workflow Automation Playbooks provide 20 cybersecurity automation templates (Red Team, Blue Team, AppSec/DevSecOps, Platform Security). Automated macro execution may trigger external notifications (Slack, email) and security actions. Users are responsible for reviewing and authorizing automation workflows before enabling them
  • Web Reconnaissance Tools (security headers, DNS, SSL, WHOIS, tech detection) include SSRF protection that blocks scanning of private, loopback, link-local, and multicast IP ranges. Users must only scan domains they own or have written authorization to test
  • All MCP tool executions are logged with tool name, parameters, timestamp, results, and executing admin identity for audit purposes
  • Misuse of MCP tools for unauthorized scanning, reconnaissance, or attack planning against systems without explicit written authorization constitutes a violation of these Terms and may result in immediate account termination
Section 6i

API Overwatch Monitoring Terms

6i.1 API Monitoring Scope

  • API Overwatch provides real-time monitoring of platform API transactions including method, endpoint, status code, response time, and anomaly detection
  • Transaction logs are stored in-memory for operational monitoring and are not persisted to permanent storage
  • Anomaly detection identifies patterns such as slow responses, rate limiting, server errors, authentication brute-force attempts, and mutating requests

6i.2 Data Retention

  • API transaction logs are retained in-memory with automatic rotation (most recent 10,000 transactions)
  • Anomaly alerts are retained in-memory with automatic rotation (most recent 1,000 anomalies)
  • Scan history is retained in-memory with automatic rotation (most recent 500 scans)

6i.3 API Fuzzer Disclaimer

The API Fuzzer tool is intended for testing your own applications and authorized targets only. Unauthorized fuzzing of third-party APIs, services, or endpoints is prohibited and may violate applicable laws.

Section 6j

Zapier Compliance Automation & Macro Engine Terms

6j.1 Zapier Compliance Automation Pipeline

The Zapier Compliance Automation Pipeline forwards platform events to user-configured Zapier webhooks. The pipeline supports 10 event types including relay status changes, compliance posture updates, agent task results, security alerts, scan completions, fleet health metrics, incident triggers, policy violations, audit log entries, and scheduled compliance reports.

Third-Party Data Forwarding
By configuring Zapier webhooks, you authorize Guardian Posse to forward event data to the third-party Zapier service. CPWE AI is not responsible for how Zapier or downstream integrations process, store, or share your data. Users must review Zapier’s terms of service and privacy policy independently.

6j.2 Zapier Macro Engine

The Zapier Macro Engine provides 8 pre-built automation macros that trigger automated actions based on platform events. Macros may send emails, post Slack messages, update CRM records, create tickets, or perform other automated actions via Zapier integrations.

Automated Execution Risks

Macros execute automatically when triggered by platform events. Users are solely responsible for configuring macro triggers, reviewing automated actions, and ensuring macros do not produce unintended consequences. CPWE AI is not liable for emails sent, messages posted, records modified, or any other actions performed by automated macros.

6j.3 Relay Compliance Map

The Relay Compliance Map provides fleet visualization with NIST compliance overlay, aggregating relay telemetry data for compliance posture awareness. Compliance map visualizations are informational and do not constitute official NIST compliance certifications.

6j.4 Data Retention for Zapier Events

  • Zapier webhook event logs are retained for 90 days
  • Macro execution history is retained for 90 days
  • Failed webhook deliveries are retried up to 3 times, then logged as failed
  • Users may request deletion of Zapier event logs by contacting james@cpwe.biz
Section 6k

OpenClaw AGI Security Bridge & Compliance Terms

6k.1 OpenClaw AGI Security Bridge

The OpenClaw AGI Security Bridge provides security scanning of third-party OpenClaw deployments. Guardian Posse serves as the cybersecurity layer for OpenClaw deployments, offering proactive security assessment and compliance enforcement.

6k.2 OpenClaw Security Scanner

The OpenClaw Security Scanner provides 6 specialized scan types:

  • Config Auditor: Analyzes OpenClaw deployment configuration for security misconfigurations
  • Skill Scanner: Inspects installed OpenClaw skills for malicious patterns or vulnerabilities
  • CVE Checker: Cross-references OpenClaw components against known vulnerability databases
  • Port Exposure: Identifies unnecessarily exposed network ports on OpenClaw deployments
  • Permission Auditor: Reviews permission grants and access control configurations
  • Prompt Injection Detector: Tests for prompt injection vulnerabilities in OpenClaw agent configurations
Scanning Results Disclaimer
OpenClaw security scan results are provided on a best-effort basis and are not guaranteed to identify all vulnerabilities, misconfigurations, or security risks. Scan results do not constitute a comprehensive security audit, penetration test, or compliance certification. Users must independently verify scan findings and engage qualified security professionals for authoritative assessments.

6k.3 OpenClaw NIST Compliance Framework

The OpenClaw NIST Compliance Framework maps 19 NIST 800-53 control families to OpenClaw-specific requirements, providing compliance posture assessment for OpenClaw deployments. Control families covered include Access Control (AC), Awareness & Training (AT), Audit & Accountability (AU), Configuration Management (CM), Contingency Planning (CP), Identification & Authentication (IA), Incident Response (IR), Maintenance (MA), Media Protection (MP), Personnel Security (PS), Physical & Environmental Protection (PE), Planning (PL), Risk Assessment (RA), Security Assessment (CA), System & Communications Protection (SC), System & Information Integrity (SI), System & Services Acquisition (SA), Supply Chain Risk Management (SR), and Program Management (PM).

Compliance Framework Advisory

NIST compliance mappings for OpenClaw deployments are advisory and educational. They do not constitute official NIST assessments, FedRAMP authorization, or any government-recognized compliance certification.

6k.4 OpenClaw Relay Bridge

The OpenClaw Relay Bridge operates as a security sidecar, providing continuous monitoring of OpenClaw deployments. Capabilities include:

  • Behavior analysis of OpenClaw tool execution patterns
  • Detection of credential access attempts, data exfiltration patterns, and anomalous behavior
  • Compliance enforcement against configured security policies
  • Real-time alerting for security-relevant events

6k.5 Agent Zapier-Aware & OpenClaw Capabilities

Guardian Posse AI agents have been enhanced with Zapier-aware and OpenClaw-aware skillsets. Agents may autonomously trigger Zapier macros, initiate OpenClaw security scans, or recommend compliance actions based on detected events. All autonomous agent actions are logged and auditable.

6k.6 Data Retention for OpenClaw Scanning

  • OpenClaw deployment registry metadata (name, URL, version, last scan) is retained for the lifetime of the deployment registration
  • Scan results are retained for 180 days
  • CVE findings are retained until the associated deployment is deregistered
  • Behavior analysis logs from the Relay Bridge are retained for 90 days
  • Users may request deletion of OpenClaw scan data by contacting james@cpwe.biz
Section 6l

ZeroClaw Runtime & Omnichannel Messaging Terms

6l.1 ZeroClaw Runtime Integration

Guardian Posse integrates with ZeroClaw, a Rust-native AI agent runtime framework by zeroclaw-labs, for lightweight edge deployment of cybersecurity agents. ZeroClaw enables Guardian Posse agents to operate on resource-constrained devices (under 5MB RAM, sub-10ms cold start) while maintaining full access to the platform's 62 MCP tools and multi-provider AI system.

6l.2 AIEOS Agent Identity

ZeroClaw agents deployed through Guardian Posse operate under a defined identity (AIEOS specification) and soul file that governs:

  • Agent capabilities and behavioral boundaries
  • Supported compliance frameworks (NIST 800-53, NIST 800-171, CMMC Level 2, SOC 2, MITRE ATT&CK, OWASP)
  • Autonomy mode (ReadOnly, Supervised, or Full) with deny-by-default sandboxing
  • Knowledge sources and response format constraints

6l.3 Omnichannel Messaging Services

Guardian Posse's ZeroClaw integration supports cybersecurity question-and-answer services through multiple messaging channels:

  • Supported Channels: Telegram, Discord, Slack, WhatsApp, Signal, Matrix/Element, Email, and Web Chat
  • Service Scope: CVE lookups, compliance guidance, security header checks, DNS/SSL validation, hardening recommendations, incident response guidance, and general cybersecurity education
  • No Credential Collection: The ZeroClaw agent will never request passwords, API keys, private keys, or other credentials through any messaging channel
  • AI-Powered Responses: All messaging responses are generated by AI providers (subject to Section 7 AI Content Disclaimer) using the agent's soul context for cybersecurity expertise

6l.4 Edge Deployment Terms

  • ZeroClaw edge nodes deployed as relay fleet members must authenticate via JWT tokens and check in with the Guardian Posse command center at configured intervals
  • Edge nodes operate under Supervised autonomy mode by default — critical actions require platform approval
  • Users deploying ZeroClaw edge nodes are responsible for ensuring the target device/server is authorized for such deployment

6l.5 OpenClaw Compatibility

ZeroClaw maintains backward compatibility with OpenClaw identity formats (IDENTITY.md, SOUL.md). Migration from OpenClaw to ZeroClaw runtime is supported but does not guarantee identical behavior. Users should test migrated agents before production deployment.

6l.6 Third-Party Messaging Platform Terms

Use of messaging channels is subject to each platform's own Terms of Service and Acceptable Use Policies. CPWE AI is not responsible for:

  • Service interruptions, message delivery failures, or data handling by third-party messaging platforms
  • Changes to third-party platform APIs that may affect messaging channel availability
  • Data processing performed by third-party platforms on messages sent to or received from the Guardian Posse agent
Advisory Nature of Messaging Responses: Cybersecurity guidance provided through messaging channels is advisory and educational only. It does not constitute a professional security assessment, penetration test, compliance audit, or certification. Users must independently verify all guidance and engage qualified professionals for authoritative security assessments.

6l.7 Channel Administration

  • Enabling or disabling messaging channels is restricted to platform administrators
  • CPWE AI reserves the right to disable any messaging channel at any time for security, compliance, or operational reasons
  • Rate limiting may be applied to prevent abuse of messaging-based query services
Section 7

AI-Generated Content Disclaimer

7.1 General AI Content Notice

  • AI-generated outputs may contain errors, inaccuracies, hallucinations, or outdated information
  • AI content is not a substitute for professional advice, including legal, medical, financial, military, or cybersecurity guidance
  • CPWE AI makes no warranties regarding the accuracy, completeness, reliability, or fitness for purpose of any AI-generated content
  • Users are solely responsible for reviewing, verifying, and validating all AI-generated outputs before use or reliance

7.2 AI Art & Creative Content

  • AI-generated artwork, images, and visual content may be subject to intellectual property considerations under evolving law
  • Users should independently verify copyright and IP compliance for any AI-generated art used commercially
  • Comic content produced through the Platform represents creative expression and is not intended as factual representation
  • AI-generated character designs may share similarities with existing works; users are responsible for clearance checks

7.3 Code Generation

AI-generated code should be thoroughly reviewed, tested, and validated before deployment in production environments. CPWE AI is not liable for bugs, security vulnerabilities, or failures in AI-generated code.

Section 8

Acceptable Use Policy

Permitted Uses

  • Software development and engineering
  • AI-assisted code generation and analysis
  • Team collaboration on projects
  • Educational and learning purposes
  • Commercial software development
  • Security research on systems you are authorized to test
  • Curriculum and educational content creation
  • Creative content and comic art generation
  • Business process automation
  • EPB bullet drafting (subject to Section 5)
  • Compliance readiness assessments (advisory)
  • Deploying relay agents on authorized infrastructure
  • Active defense and threat investigation on your own systems
  • Generating risk assessments and tabletop exercises
  • Physical penetration testing with written client authorization
  • RF spectrum analysis and wireless security auditing on authorized networks
  • ICS/SCADA safety assessments using ICS-Safe classified devices
  • Configuring Zapier webhooks for compliance automation on your own deployments
  • Running OpenClaw security scans on deployments you own or are authorized to assess
  • Using ZeroClaw messaging channels to ask cybersecurity questions and receive guidance
  • Deploying ZeroClaw edge nodes on devices and servers you own or are authorized to manage
  • Using the Relay Compliance Map for fleet posture visualization
  • Configuring Zapier macros for automated event-driven workflows

Prohibited Activities

  • Entering classified, CUI, or FOUO information
  • Using security tools against unauthorized targets
  • Generating malicious code, malware, or exploits for harmful purposes
  • Impersonating government officials or military personnel
  • Reverse engineering or unauthorized access to Platform systems
  • Violating third-party intellectual property rights
  • Generating harmful, abusive, or illegal content
  • Circumventing security measures or access controls
  • Sharing access credentials with unauthorized parties
  • Automated scraping or data harvesting
  • Using the Platform for any purpose that violates applicable law
  • Deploying relay agents on unauthorized systems
  • Using active defense tools for offensive operations
  • Deploying honeypots on networks you do not control
  • Using physical pen test devices without written authorization
  • Deploying ICS-Unsafe devices against industrial control systems without safety certification
  • Unauthorized RF transmission or jamming
  • Keystroke or video capture without legal consent
  • Requesting SSL certificates for domains you do not own or control
  • Running OpenClaw security scans against deployments without authorization
  • Using ZeroClaw messaging channels to distribute malware, phishing, or social engineering attacks
  • Deploying ZeroClaw edge nodes on unauthorized systems or networks
  • Impersonating the Guardian Posse cybersecurity agent on messaging platforms
  • Configuring Zapier webhooks to exfiltrate data to unauthorized third parties
  • Using Zapier macros to spam, harass, or conduct denial-of-service attacks
Section 9

AI Provider Terms

Third-Party AI Services
Your use of AI features on the Guardian Posse AI Platform is subject to additional terms from the underlying AI providers. By using AI-powered features, you also agree to the terms of the applicable provider(s).
AI Provider Additional Terms Data Processing
OpenAI OpenAI Terms of Use Subject to OpenAI’s privacy policy
Anthropic Anthropic Terms of Service Subject to Anthropic’s privacy policy
Google Gemini Google AI Terms Subject to Google’s privacy policy
Perplexity Perplexity Terms Subject to Perplexity’s privacy policy
xAI (Grok) xAI Terms of Service Subject to xAI’s privacy policy

CPWE AI is not responsible for changes to third-party AI provider terms, policies, or service availability. Users should review each provider’s terms independently.

Section 10

Intellectual Property

10.1 Platform Ownership

CPWE AI owns all rights, title, and interest in the Guardian Posse AI Platform, including but not limited to:

  • Platform source code, architecture, and proprietary algorithms
  • The Guardian Posse brand, name, logos, and visual identity
  • Guardian House Style design system and UI/UX elements
  • The 12 Guardian characters, their names, likenesses, and associated storylines (trademarked)
  • All original comic art, character designs, and creative assets created by CPWE AI

10.2 User Content

Your Content & Creations

You retain all rights to original content, code, projects, and creative works you produce using the Platform. CPWE AI claims no ownership over your intellectual property. By uploading content to the Platform, you grant CPWE AI a limited, non-exclusive license to process, display, and store your content solely for the purpose of providing the Platform services.

10.3 AI-Generated Content

  • Content generated by AI providers through the Platform is subject to the respective AI provider’s terms regarding ownership and usage rights
  • AI-generated content may not be unique or copyrightable under current law
  • Users should review all AI-generated content for accuracy, originality, and compliance before use
  • Attribution may be required as specified by individual AI providers
Section 11

Privacy & Data Protection

Your privacy is critically important to us. Our collection, use, and protection of personal information is governed by our comprehensive Privacy Policy, which is incorporated into these Terms by reference.

GDPR Compliant

Full compliance with EU General Data Protection Regulation.

CCPA Compliant

California Consumer Privacy Act compliance for US users.

NIST 800-171

Aligned with NIST cybersecurity and privacy frameworks.

COPPA & FERPA

Children’s privacy and educational data protections.

Section 12

Service Availability

12.1 Platform Availability

CPWE AI strives to maintain high availability of the Guardian Posse AI Platform but does not guarantee uninterrupted, error-free, or continuous service. Planned maintenance will be announced in advance when possible.

12.2 AI Provider Dependencies

Third-Party Dependencies

AI features depend on third-party providers (OpenAI, Anthropic, Google, Perplexity, xAI) and may experience interruptions, degraded performance, or outages beyond our control. CPWE AI is not liable for third-party service disruptions.

12.3 Service Modifications

CPWE AI reserves the right to modify, update, or discontinue any features or services at any time. We will make reasonable efforts to notify users of significant changes.

Section 13

Limitation of Liability

Important Legal Notice
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, CPWE AI SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES ARISING FROM YOUR USE OF THE PLATFORM.

13.1 General Limitations

CPWE AI, its officers, directors, employees, and agents shall not be liable for:

  • Indirect, incidental, special, consequential, or punitive damages of any kind
  • Loss of profits, data, business opportunities, or goodwill
  • AI-generated content accuracy, suitability, or fitness for any particular purpose
  • Third-party AI provider service interruptions or data processing
  • Unauthorized access to or alteration of your data or transmissions

13.2 Government & Military Tool Limitations

  • CPWE AI bears no liability for EPB outcomes, evaluation results, or career impacts based on AI-generated suggestions or bullet statements
  • Military performance evaluation content is advisory only; users assume full responsibility for submitted evaluations
  • No liability for decisions made based on compliance assessment tool outputs

13.3 Cybersecurity Tool Limitations

  • No liability for security assessment results, false positives, false negatives, or incomplete vulnerability identification
  • No liability for consequences arising from misuse of security testing tools
  • Compliance readiness scores and assessments are informational and carry no guarantee of actual compliance
  • No liability for physical damage to hardware, networks, or industrial systems during authorized pen test engagements
  • No liability for RF interference, signal disruption, or FCC violations caused by user-operated devices

13.4 Maximum Liability

IN NO EVENT SHALL CPWE AI’S TOTAL AGGREGATE LIABILITY EXCEED THE GREATER OF (A) THE AMOUNT PAID BY YOU TO CPWE AI FOR USE OF THE PLATFORM IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM, OR (B) ONE HUNDRED U.S. DOLLARS ($100.00).

Section 14

Indemnification

You agree to indemnify, defend, and hold harmless CPWE AI, its officers, directors, employees, contractors, and agents from and against any and all claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys’ fees) arising from or related to:

  • Your use of, or inability to use, the Platform
  • Your violation of these Terms or any applicable law or regulation
  • Your infringement of any third-party intellectual property or other rights
  • Content you submit, generate, upload, or transmit through the Platform
  • Misuse of cybersecurity tools, including unauthorized security testing, PCAP analysis of unauthorized captures, or OSINT activities that violate applicable law
  • Misrepresentation of AI-generated content as official government, military, or institutional communications
  • Entry of classified, CUI, or restricted information into the Platform
  • Any consequences resulting from reliance on AI-generated EPB content, compliance assessments, or security evaluations
Section 15

Termination

15.1 Termination by You

You may stop using the Platform at any time. To request deletion of your account and associated data, contact us at james@cpwe.biz. Data deletion requests will be processed in accordance with our Privacy Policy.

15.2 Termination by CPWE AI

We may suspend or terminate your access to the Platform immediately, without prior notice or liability, if you:

  • Violate these Terms of Service
  • Engage in prohibited activities as outlined in Section 8
  • Compromise or attempt to compromise Platform security
  • Enter classified or controlled information into the Platform
  • Misuse cybersecurity tools against unauthorized targets
  • Fail to comply with applicable laws or regulations

15.3 Effect of Termination

Upon termination, your right to use the Platform ceases immediately. Sections relating to Intellectual Property, Limitation of Liability, Indemnification, Governing Law, and Dispute Resolution shall survive termination.

Section 16

Governing Law

These Terms of Service shall be governed by and construed in accordance with the laws of the State of Arkansas, United States, without regard to its conflict of law provisions. You agree to submit to the personal and exclusive jurisdiction of the courts located within the State of Arkansas for the resolution of any disputes arising under or related to these Terms.

Jurisdiction

All legal proceedings related to these Terms shall be brought in the state or federal courts located in the State of Arkansas, United States. You waive any objection to the exercise of jurisdiction over you by such courts and to venue in such courts.

Section 17

Export Controls

U.S. Export Control Compliance
The Platform and its components may be subject to U.S. export control laws and regulations.

17.1 Export Restrictions

  • The Platform may contain encryption technology and other items subject to export control under the Export Administration Regulations (EAR) and International Traffic in Arms Regulations (ITAR)
  • You may not access, download, use, or export the Platform or any underlying technology in violation of U.S. export laws or regulations
  • You represent and warrant that you are not located in, or a national or resident of, any country subject to U.S. sanctions or embargoes

17.2 User Obligations

  • Users must comply with all applicable export control laws, including EAR and ITAR as applicable
  • Users must not re-export or transfer Platform technology to restricted parties or countries
  • Users are responsible for obtaining any required export licenses or approvals
Section 18

Government Use Rights

18.1 Commercial Item Designation

The Platform and all associated documentation and services are “Commercial Items” as defined in 48 C.F.R. §2.101, consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.7202, as applicable.

18.2 FAR/DFARS Provisions

Government Licensing

If the Platform is acquired by or on behalf of a U.S. Government agency, the Government’s rights in the Platform and documentation shall be only those set forth in these Terms, in accordance with 48 C.F.R. §12.212 (for civilian agencies) and 48 C.F.R. §227.7202-1 through 227.7202-4 (for Department of Defense agencies). The contractor/manufacturer is CPWE AI, contact: james@cpwe.biz.

Section 19

Dispute Resolution

19.1 Good Faith Negotiation

Before initiating any formal dispute resolution proceeding, the parties agree to first attempt to resolve any dispute, claim, or controversy arising out of or relating to these Terms through good faith negotiation for a period of at least thirty (30) days after written notice of the dispute is provided to the other party.

19.2 Binding Arbitration

If a dispute cannot be resolved through good faith negotiation, the parties agree that any dispute, claim, or controversy arising out of or relating to these Terms shall be resolved by binding arbitration administered in accordance with the rules of the American Arbitration Association (AAA). The arbitration shall take place in the State of Arkansas, and the arbitrator’s decision shall be final and binding.

19.3 Class Action Waiver

Waiver of Class Proceedings

YOU AGREE THAT ANY DISPUTE RESOLUTION PROCEEDINGS WILL BE CONDUCTED ONLY ON AN INDIVIDUAL BASIS AND NOT IN A CLASS, CONSOLIDATED, OR REPRESENTATIVE ACTION. You waive your right to participate in a class action lawsuit or class-wide arbitration against CPWE AI. If for any reason a claim proceeds in court rather than in arbitration, you waive any right to a jury trial.

19.4 Exceptions

Notwithstanding the above, either party may seek injunctive or other equitable relief in any court of competent jurisdiction to prevent the actual or threatened infringement, misappropriation, or violation of intellectual property rights.

Section 20

Changes to Terms

CPWE AI reserves the right to update, modify, or replace these Terms at any time. We will provide notice of material changes through:

  • Email notification to registered users
  • Prominent notice on the Platform
  • Updated “Last Updated” date at the top of these Terms

Continued use of the Platform after changes are posted constitutes your acceptance of the revised Terms. If you do not agree to the updated Terms, you must discontinue use of the Platform.

Version 3.7 — Effective March 4, 2026 — Added ZeroClaw Runtime & Omnichannel Messaging Terms (Section 6l) covering AIEOS agent identity, soul file governance, omnichannel messaging services (Telegram, Discord, Slack, WhatsApp, Signal, Matrix, Email, Web Chat), edge deployment terms, OpenClaw compatibility, third-party messaging platform terms, channel administration, and advisory disclaimers. Updated Acceptable Use Policy with ZeroClaw permitted and prohibited activities.
Version 3.6 — Effective March 3, 2026 — Added MCP Tools & Offensive Security Intelligence section (Section 6h.6) covering 59 MCP tools across 13 categories. Added HexStrike offensive security tools terms (intelligence/planning layer, no actual attacks). Added OpenClaw Agent Fleet MCP terms. Added Workflow Automation Playbook terms (20 cybersecurity templates). Added Web Recon SSRF protection disclosure. Added MCP execution logging and audit requirements.
Version 3.5 — Effective February 25, 2026 — Added Zapier Compliance Automation terms and OpenClaw AGI Security Bridge terms covering deployment registry, 6-type security scanning, NIST 800-53 compliance mapping, behavior monitoring, and macro automation risks.
Version 3.2 — Effective February 19, 2026 — Added SSL/CertBot Certificate Management Terms (Section 6f). Updated Relay Agent section (6b) with Enhanced Installer v3.0 step-by-step instructions, 12-agent fleet details, credential security, and beginner-friendly getting started guide. Added CertBot SSL Manager to Service Description. Updated Acceptable Use Policy with SSL certificate domain ownership requirement.
Version 3.1 — Effective February 16, 2026 — Added Browser Extension Terms (Section 6e) covering data handling, permissions, installation, and disclaimer.
Version 3.0 — Effective February 13, 2026 — Added Relay Agent Deployment terms, Active Defense & Threat Investigation terms, expanded Service Description with infrastructure monitoring and risk management services, updated Acceptable Use Policy.
Version 2.0 — Effective February 1, 2026 — Complete rewrite for government-grade compliance
Section 21

Contact Information

For questions, concerns, or requests regarding these Terms of Service, please contact us:

CPWE AI

Guardian Posse AI Platform
Operator & Data Controller

Domains

guardianposse.com
cpwe.ai
ai-comic-studio.com

Related Policies

Privacy Policy — How we collect, use, and protect your data.