Enterprise-grade, from the first conversation.
LUIXER is architected for organizations that can't afford to get this wrong. Here's exactly how the platform is built to protect your data and your customers.
Strict tenant isolation
Every organization's data — AI Employee configurations, conversation history, knowledge base content — is logically separated from every other organization's data. No cross-tenant reads or writes.
Encryption in transit and at rest
All traffic between customers, LUIXER, and AI Employees is encrypted in transit. Stored data is encrypted at rest across the platform's infrastructure.
Role-based access control
Access within an organization's tenant is governed by role-based permissions — not every user or every AI Employee can see or do everything by default.
Human approval gates
Higher-stakes actions can be configured to draft-and-approve rather than send automatically, keeping a human in the loop for anything with financial, legal, or reputational weight.
Full audit logging
Every AI Employee action, every human approval, and every tool call is logged — a record you can review, not a black box you have to trust blindly.
You own your data
Customer data — including AI Employee conversation history, workflow configurations, and knowledge base content — belongs to the organization that generated it, not to LUIXER.
Subprocessors, disclosed
We share information only with subprocessors who help operate the Services (cloud infrastructure, telephony, messaging, AI inference), each bound by confidentiality and data protection obligations. A current list is available on request.
Retention controls
Organizations control retention settings for their own tenant data within platform configuration options and applicable law — data isn't kept longer than it needs to be.
UAE PDPL and GDPR readiness
LUIXER is headquartered in the UAE and built with the UAE Personal Data Protection Law (PDPL) in mind, alongside readiness for frameworks like the EU GDPR where they apply to customers or their end users.
Deployment and data location
Where LUIXER runs, and where your data sits, is an Enterprise conversation rather than a setting — because the honest answer depends on your jurisdiction, your regulator and your own infrastructure. Organisations that cannot move call handling off site can connect the equipment they already run through LUIXER Edge, arranged with us.
Security roadmap
ISO 27001 and SOC 2 readiness is in progress. LUIXER does not currently hold either certification — we're building toward them and will update this page the moment either is achieved, not before.
A recording is only useful if it cannot leak.
Recorded calls are the most sensitive thing LUIXER holds, so the handling is deliberate rather than incidental. Each of the following has been verified on a real call rather than assumed from a successful upload.
Recordings go to private storage, scoped to your organisation
Stored in a private cloud bucket with no public access, under a key bound to your organisation. Verified on a real call.
A recording is only marked stored once it demonstrably is
Presence is confirmed by a separate check against the storage itself, and integrity by comparing the stored checksum against the live object — not inferred from an upload having returned success.
Playback goes through LUIXER, never a raw storage link
Listening to a recording requires being signed in and authorised for that organisation. No storage URL, provider URL or shareable pre-signed link is ever handed out — a request without a valid session is refused.
Whether recording is enabled at all is your decision, configured per organisation and separately for internal and external calls.
Questions about a specific control, a security questionnaire, or a subprocessor list? Contact us directly.