Security & Data Protection
razorBridge Managed kOS combines workspace access controls with configurable AI routing and data retention. Hosting and processing depend on the Shared or Dedicated tier and the services you use.
Controls, Scope & Evidence
Review our certification, hosting choices and controls for your security assessment.
ISO 27001 certified
KlusAI holds an accredited ISO 27001 certificate.
Hosting locations
Shared hosting is configured for Frankfurt. The current Dedicated deployment is configured for Paris. AI processing and service exceptions are described below.
Data protection controls
Organization permissions, selected audit events and retention settings support data protection. They do not by themselves establish GDPR compliance for your use case.
AI use and review
razorBridge Managed kOS is designed for EU AI Act readiness. Model routing and usage records support your use-case assessment.
Where kOS runs
razorBridge Managed kOS comes in two tiers, described by where the data centre is, who runs it, and where AI requests are processed.
Workspace data is stored in Frankfurt, Germany, in a data centre of a provider headquartered in the United States. AI requests are sent to model providers that may process them outside the EU.
The current Dedicated configuration uses a separate deployment in Paris, France, with an EU-headquartered provider. Model routing is restricted to that provider. This does not mean that every model runs on hardware reserved for your organization. Named exceptions include transactional e-mail through a provider in the United States and, where configured, speech transcription in the Netherlands through a provider headquartered outside the EU. Web search may send screened search terms to a provider in the United States.
Sub-processing and international transfers are set out in the Data Processing Agreement.
Security Practices
Available controls and their limits depend on the deployment and configuration.
Infrastructure Security
- Shared hosting uses common infrastructure; the Dedicated configuration defines a separate deployment cell.
- The Dedicated configuration supports HTTPS and enables managed database encryption at rest.
- The Dedicated configuration defines a private network for its database and application services.
- Encryption is configured for new Dedicated storage objects; that setting does not establish encryption of older objects.
- Dedicated database backups are configured in the same region, with a configurable retention period.
Access Controls
- Workspace permissions use roles, capabilities and organization membership.
- Organizations can require two-factor authentication for workspace access.
- Microsoft and Google sign-in are supported where configured.
- Security logs record selected authentication and access-management events, not every action or read.
- Organization membership and active status are checked when resolving workspace access.
Data Protection
- Shared workspaces use application-level organization scoping, not physical separation for each customer.
- Scheduled cleanup covers selected audit records, temporary uploads and conversations.
- Retention varies by data type and configuration. Deactivating an organization does not erase its data.
- Provider retention and training restrictions vary by service and route. Shared kOS does not enforce a universal no-training policy.
- Document screening can use reversible pseudonyms. Original text and restoration mappings remain stored.
Operational Evidence
- Published legal documents have version identifiers, with acceptance recorded against the document version.
- Configuration changes can produce audit records; recording is best-effort for some changes.
- Gateway usage records include model and provider identifiers; they are not a complete activity history.
- Backup configuration alone does not demonstrate a successful restore or disaster recovery exercise.
- For security reviews, ask which operational records are available for your deployment.
AI Controls & Limits
AI controls apply to specific routes and workflows. Review their scope before sending sensitive material.
Provider Routing
Deployment policies can restrict model providers. A restricted route is not proof of dedicated model hardware or isolated fine-tuned models.
Document Screening
Supported document workflows can screen extracted text. Image extraction may use a vision model before text screening, and screening depends on the source and policy.
Tool Permissions
Assistant tools have permission checks and selected actions require confirmation. These controls do not guarantee protection against prompt injection.
Usage Records
Gateway usage, selected security events and optional retrieval traces provide partial records. Coverage and retention vary by workflow.
Interaction Retention
AI interactions may be stored according to deployment settings. Document screening does not mean that originals or interaction logs are deleted.
Human Review
Review AI output and supporting sources before using them in a decision. This page makes no claim of a completed adversarial testing programme.
Security Questions?
Contact us to discuss the controls, hosting configuration and evidence needed for your security review.
Responsible Disclosure: Report security vulnerabilities to [email protected]