Use the platform only for authorized security work
Do not use CanaryVaults to test, probe, or monitor systems you do not own or have clear permission to assess.
Last updated: July 14, 2026. A concise operating summary for how CanaryVaults should be used, what customers control, and where product responsibility begins and ends.
This page is intentionally brief and operational. It is designed to help teams understand the main boundaries before they adopt the platform.
Do not use CanaryVaults to test, probe, or monitor systems you do not own or have clear permission to assess.
You are responsible for the documents, prompts, trap endpoints, account details, and external systems you connect to the product.
Hashes, timestamps, and transaction references help preserve evidence, but they do not replace incident investigation, policy review, or legal advice.
Usage limits, support scope, and upgrade paths are defined by the plan attached to the account and can change when plans are updated or renewed.
Entity, governing law, and billing facts, stated plainly. Entity and forum details are published as they are formalized rather than invented here.