Prove before claiming
Publish controls, audits, certifications, and service commitments only after they exist and can be evidenced.
Security direction
Trust begins with saying what is not finished.
FireGuard is still developing its production architecture and security program. We will not claim certifications, compliance, uptime guarantees, or controls before they are implemented and independently supportable.
Working principles
Security claims should be evidence, not decoration.
Minimize sensitive data
Collect and retain only what the product needs, with explicit boundaries for operational and patient information.
Design for recovery
Treat tested backup, restoration, provenance, and customer export as product requirements rather than afterthoughts.
Make responsibility legible
Document what FireGuard protects, what customers configure, and how incidents and vulnerabilities are reported.
Before production use
The real security package will be reviewable.
Before accepting production customer data, FireGuard will document its actual controls, subprocessors, recovery procedures, vulnerability intake, privacy and data-processing terms, and any applicable compliance scope. Customer commitments will live in reviewed agreements—not in unsupported landing-page badges.
security@joinfireguard.comService status
No uptime to report yet—and no pretending otherwise.
FireGuard does not yet run a generally available customer service, so there is no production uptime history or service-level commitment to publish. Before launch we will set up monitoring, incident communication and recovery procedures, and this section will report real availability from them. Any availability commitment will live in a signed customer agreement.