Ground rules for using the current FireProof product path.
These terms describe the current operating baseline for the product. They are written to match the real active path instead of pretending the system is larger than it is.
Scope matters
These terms cover the currently active FireProof path: account access, current wedge challenges, submissions, review, and related operational surfaces.
Use of the current product path
FireProof currently exposes a focused product path around challenge-driven proof flows. Access to the product does not mean every historical or future feature is active in the current path.
Accounts and responsibility
You are responsible for the activity performed through your account and for keeping your credentials secure. Misuse of another person's account or attempts to bypass platform controls are not permitted.
Challenge submissions
You retain responsibility for the code and material you submit. The product may store submissions, related execution evidence, and operational records to support review, verification, and integrity analysis.
Acceptable use
Do not use the product to run malicious payloads, abuse infrastructure, attack other systems, or intentionally disrupt execution and review workflows. The current path is for legitimate trust-oriented evaluation use only.
Service limitations
This product is still an active path, not a blanket enterprise promise. Some environments, integrations, or controls may differ between demo, local, and production-oriented setups unless separately agreed.