SUPPORT, RELEASES, AND EVALUATION

The ClaudeWar changelog records user-visible releases, affected audiences, availability, required action, and related documentation.

• Account or billing: include the account email and transaction date, but never send passwords or full payment details.
• API: include the request path, timestamp, status code, request ID if present, and sanitized response.
• Data correction: include the source, observation time, page or card, and evidence supporting the correction.
• Security: follow the security policy.

Contact: contact@claudewar.info

The Tools directory includes focused browser tools built on ClaudeWar data. A free account is required. Tool availability and permissions can differ from the main globe.

1. Open and cite the original source, not only the ClaudeWar summary.
2. Record observation and retrieval times in UTC.
3. Distinguish sensor data, public reporting, ClaudeWar correlation, and AI analysis.
4. Seek independent confirmation before describing an event as verified.
5. Contact ClaudeWar for screenshots, corrections, or methodology questions.

Use ClaudeWar to assemble context across hazards, transportation, outages, and public reporting. Use the appropriate government warning service, local emergency authority, air or maritime authority, and organizational procedures for action.

Evaluate source licensing, geographic coverage, latency, confidence labels, failure modes, retention, API contracts, security controls, support, and service levels against your mission. Acceptance into a program or network does not imply endorsement, procurement, or operational approval.

Visit the Press page for company facts and contact information. Confirm dynamic usage and scale metrics at the time of publication rather than copying an old value.

• Legal overview
• Terms of Service
• Privacy Policy
• Editorial Policy
• Security Policy