Security / Evidence / Limits
Controls you can inspect
Security claims should describe a control and its limits. This page describes repository controls, not a certification or a live production attestation.
01Identity and tenant scope
Retained operational APIs verify identity server-side and derive role and tenant membership from protected profiles. Database hardening includes scoped browser reads and restricted writes. Live application of configuration must be verified separately.
02Platform access
Platform HQ requires verified super_admin authority and audited cross-tenant access. Tenant administrators do not gain global administration by opening a platform page.
03Critical actions
Requester and reviewer identity are server-derived. Unsupported approval or execution paths fail closed rather than simulate success.
04Evidence and limits
No SOC 2, ISO 27001, uptime guarantee, penetration-test certification or blanket production-security claim is made. Provider setup, live configuration and ongoing operational monitoring require separate verification.
05Reporting a concern
Use your established account support channel. A public vulnerability-reporting address and response commitments have not been approved; no unmonitored address is advertised.