Security & Trust
How the platform protects your data
Tenant isolation, role-based access and an audit layer are part of how every module works, not add-ons.
Separate by tenant, controlled by role
Each company works in its own tenant. Inside it, every module uses the same access rules, and sensitive changes are recorded in the audit layer.
Security controls
The documented controls behind the platform.
Tenant isolation
Every record belongs to one tenant. The tenant is taken from the signed-in session, never from the request, and a record from another tenant is treated as not found.
Roles and permissions
Access is granted through roles and checked by the platform on every request, not only hidden in the interface. Nobody can grant a permission they don't hold themselves.
Organizations and branches
Inside a tenant, the organization is structured into branches, departments and teams, and users can be given access to specific branches.
Sign-in and sessions
Email and password sign-in for verified email addresses. Sign-in attempts are rate-limited, password reset links are single-use and time-limited, and a password reset ends every existing session.
Audit layer
The system provides an audit layer for sensitive events and changes, within the scope of each tenant and the viewer's permissions. Audit records can't be edited or deleted.
Data protection
Traffic is encrypted in transit with TLS 1.2 or later, and sensitive fields are encrypted at rest. Passwords are stored with a modern adaptive hash, never with reversible encryption.
File security
Files are private by default and are downloaded through short-lived signed links, issued only after the tenant and permission checks pass.
What this page covers
This page describes the platform's documented controls. Details on data retention, security testing and API access will be added here once they are approved for publication.
Common questions
Yes. The platform is built as a multi-tenant system in which each company's data is isolated from every other company's. Access is controlled by role, and key actions are recorded in an audit log.