A simple privacy baseline for the current FireProof product path.
This page explains, in plain language, what the current product path collects and why. It is intentionally narrower than a large enterprise policy because the active wedge itself is intentionally narrower.
Operational visibility
We keep only the data needed to run the current wedge and review consequential activity.
Current scope
The policy reflects the current product path, not every future subsystem the doctrine may eventually enable.
What we collect
FireProof collects the account information needed to operate the current product path, including username, email address, submission metadata, execution evidence, and the technical signals required to run and review wedge activity.
How the data is used
We use this data to authenticate users, manage current wedge access, process submissions, surface integrity-related signals, and keep the active proof path operational. We do not position the product as a data resale business.
Assessment and integrity records
Challenge attempts can generate submission records, code snapshots, receipts, and operational logs tied to the current wedge. These records exist to support review, verification, and controlled operational visibility.
Security and environments
The product direction is isolated execution and independently verifiable action trails. Production-oriented environments may use stronger operational controls, while local or demo environments can run in compatibility modes during development.
Data requests
If you need help regarding account data, deletion, or access questions, contact the platform operator using the current project contact path before relying on the current product path for high-stakes legal processing.