Last Updated: October 13, 2026
Regulus is designed for client operations that need clearer control around approvals, billing, document handling, and delivery records. Confidentiality, integrity, and availability guide these controls. This page summarizes the product-level security posture in plain language.
Regulus checks workspace membership on protected requests and scopes records to the active workspace. Project files use private storage and temporary download links. Sensitive vault values are encrypted, and API responses are marked private and no-store. Public client links grant access to their intended workflow; treat them as confidential and rotate or revoke them when needed.
Quoted scope terms are protected after acceptance, and repeated scope decisions and duplicate scope invoices are rejected. Deletion requires a signed-in workspace owner and explicit confirmation. Issued invoices, invoices tied to accepted scope, and sent or accepted proposals are retained. Linked records block client or project deletion. Deletion requests and successful deletions are recorded in the workspace audit trail.
Regulus provides separate process health and database readiness checks. Database readiness has a time limit and reports unavailable when its dependency cannot be reached. Request limits and bounded provider calls help contain failures, and navigation does not wait for an outgoing page animation. Operational monitoring, backup retention, and successful restoration need ongoing verification; this page does not promise an uptime SLA or recovery time.
Security checks include workspace isolation, rejected unauthorized writes, financial-term protection, private file access, and concurrent burn-on-read behavior. These checks do not constitute independent certification or prove that every integration is secure. Report suspected vulnerabilities through the support page, without sending passwords, API keys, or confidential client links.
If you need a security clarification, responsible disclosure contact, or product-level trust detail, use the support and security channels listed in the public site footer and policy pages.