Verified identity
Organization access begins only after identity and email verification.
Platform 2.0 security overview
Security claims should follow verified controls.
PrimeOps is designing the customer platform around OWASP ASVS Level 2, default-deny tenant authorization, evidence lineage, privacy minimization, and reversible release controls.
Target customer controls
Role-based access
Owner, administrator, manager, analyst, and viewer permissions stay explicit.
Tenant-scoped records
Every protected query and object check must be bound to an authorized organization.
Session controls
Customers can review and revoke active sessions after the identity provider is activated.
Audit history
Sensitive identity, membership, export, upload, and role events are append-oriented.
Privacy requests
Export and deletion requests follow authorization and retention controls.
Current release state
This marketing site includes a synthetic portal preview and never collects credentials. Sign-in and account creation hand off to the production workspace, where provider-backed authentication is active and re-proven by an authenticated smoke test after every deploy, and tenant row-level security is enforced in the database and proven in CI on every change; invitation email is delivered through a transactional provider, and a production backup restore drill passed on 2026-08-26. Account creation is by invitation for now. Encrypted customer storage, MFA, session revocation, and audit retention are not represented as active until their external owners and evidence are approved.
Report a concern
Send a concise security report to support@getprimeops.ai. Do not include credentials, payment data, or unnecessary personal information.