Security & trust
Secure by design. Governed by people.
How Inovent Workforce OS keeps every workspace separate, every credential sealed and every decision — by a person or a robot — on the record.
Controls
What protects your data today.
Every item below is how the product works now — no roadmap promises.
Tenant isolation
- Every record carries its organization
- APIs take the organization from the signed-in session, never from the request
- Robots, AI credentials, knowledge and routing rules are per workspace
- The platform owner's console is separate from client workspaces
Access control
- Roles, permission policies and role templates
- Data scopes: organization, department, branch or selected employees
- Salary, bank, ID and personal fields need their own permissions
- Reports drop salary columns for viewers without salary rights
Accounts & sign-in
- Passwords hashed with scrypt
- HTTP-only session cookies, marked secure in production
- Sign-in attempts are rate-limited
- One-time password reset links that expire after 30 minutes
- Changing a password signs out every other device
Credentials & files
- AI provider keys and integration credentials sealed with AES-256-GCM
- Secrets are never returned by an API or shown again — only a hint
- OAuth connections use PKCE and single-use state
- Uploaded files are served only through an authorised handler
Approvals & audit
- Multi-level approvals with versioned workflows
- Audit trail of data changes, exceptions and sign-ins
- Every robot step, tool call and approval is recorded
- Direct actions that need approval are blocked until approved
AI governance
- Robots start paused with no permissions
- Autonomy levels never add permissions
- Sensitive actions always wait for a person
- Budgets, rate limits and an emergency stop
- Emails, chats and web pages are treated as data, never instructions
- Protected fields are masked before text reaches a model
Hosting & data residency
Clear answers, in writing.
Inovent Workforce OS is a containerised Next.js application on PostgreSQL. We confirm where your workspace is hosted, and any residency commitment, in your contract — we don't claim certifications or regions on this page that we can't back up there.
Questions
Security, answered.
Where is our data hosted?
Inovent Workforce OS runs as a containerised application on PostgreSQL. Ask us where your workspace will be hosted — we only commit to a hosting region in writing, in your contract.
Can Inovent staff see our employee data?
Platform administrators run the platform from a separate console and never hold module access inside client workspaces. Our support team never discusses employee, payroll or HR records with anyone not verified as the account owner.
Can we use our own AI provider account?
Yes, where your package allows it. Your key is encrypted with AES-256-GCM, shown only as a hint, and your own endpoints must be public HTTPS addresses.
Have a security questionnaire?
Send it to us with your contact details and we'll answer it with the facts of how the platform works.