How the product and our own services are secured — and where the honest limits are.
Version 1.0 · effective 2 August 2026
The strongest property is structural: your data never reaches us. There is no vendor-side copy of your databases, documents, or derived knowledge to breach, subpoena, or leak. Air-gapped operation is supported.
All traffic uses TLS 1.2 or better with certificates from a public CA. Vendor-side data at rest is encrypted with platform-managed keys. Your self-hosted data is encrypted according to your own infrastructure.
The product ships SSO over OIDC, reverse-proxy and Kerberos integration, role-based access, per-agent capability allowlists, and an autonomy ladder that must be earned through measured performance. Governance changes require a second approver, so no single person can quietly widen their own permissions.
Every governed decision is written to a hash-chained, append-only audit log. The knowledge substrate keeps a bitemporal event log that can be replayed and diffed against live state, so a mutation that bypassed the log is detectable rather than invisible.
Credentials are referenced from a vault or the environment, never stored in configuration files. Vendor signing keys are held in a managed key vault with soft-delete protection.
Report to security@factrule.com. We acknowledge within 2 business days and aim to remediate critical issues within 14 days. We credit reporters who want credit, and we will not pursue good-faith research.
We are not SOC 2 or ISO 27001 certified today, and we will not imply otherwise. An independent penetration test is planned before general availability. If your procurement requires a certification we do not hold, tell us — we would rather lose a deal than misrepresent our posture.
Security contact: security@factrule.com. We answer security questionnaires directly.