Tenant separation
NURA is designed as a multi-tenant service. Workspace identity, roles, permissions and data access are enforced in the application and data layers so one tenant should not be able to access another tenant's workspace data.
Authentication and permissions
Access requires authenticated sessions. Role-based permissions limit the actions available to tenant staff and platform operators.
Secrets and integrations
Provider credentials and tokens are kept outside normal user-facing workflows and are not intended to be stored in source code, screenshots or public logs.
AI boundaries
AI providers are selected by configured routing and workspace policy. Human approval can be required before customer-facing or consequential actions are sent or applied.
Operational resilience
Production changes use versioned releases and guarded deployment steps. Backups, restore procedures and release rollback are part of the operational hardening process.
Report a concern
Security concerns can be reported to security@datamonks.io. Please avoid including passwords, private keys or unnecessary customer data in the initial report.