Skip to content
CamouDatAI
HUEN
Live demo →

How it works

The journey of data through CamouDatAI

Every request travels this same fixed sequence. A failure at any step means the request is rejected: the system is closed by default.

Sign-in from your own directory

Users sign in from your Microsoft 365 directory, through an application registered in your own tenant. The system also verifies the multi-factor claim inside the token and rejects the request without it. Disabled accounts are locked out automatically: the session is re-validated against the directory every 15 minutes. Sessions expire after 30 minutes of inactivity or 12 hours absolute, and sign-out invalidates every active session immediately.

Permissions, budget, content filtering

First the role-based permission and the monthly cost budget are evaluated, then content filtering rules run on the raw text. There are four levels of intervention: block, warn, mask and log; the stronger effect always overrides the weaker one. Filtering runs on all outgoing content: the message, the history, the document context and text extracted from files alike.

Masking: the model never sees the real value

Each sensitive value is replaced with a type-specific placeholder, generated by the instance's secret key. Identical input yields an identical placeholder, so the same person always maps to the same token and the answer stays coherent. The original cannot be derived from it; the real value and its pair remain in encrypted storage on the instance.

A single permitted outbound path

All outbound traffic is denied by default; only named destinations are allowed, enforced at two independent levels: cloud firewall and host firewall. The application has no general-purpose outbound client, only the configured endpoint. The provider contract excludes model training and, where available, retention. EU-only processing can be enabled, on a Frankfurt endpoint.

Restore and logging

Placeholders are automatically restored in the response for the user: they see the real data, the model never did. The interface shows what and how much was masked. The request receives a hash-chained log entry: who, when, with what filtering result, at what cost and through which endpoint.

Architecture

A gateway between the organisation and the external model

Users reach their own web interface. The request passes through the security gateway, then travels over an encrypted channel, with minimised content, to the external model.

Inside the organisation · dedicated instance

User layer

Browser-based chat interface · SSO sign-in · TLS-encrypted connection

↓
CONTROL POINT

Security gateway (CamouDatAI)

Permissions · de-personalisation · content filtering (DLP) · logging · budgets

↓

Data and log layer

Encrypted chat store · hash-chained audit log · encrypted backup

Outside the organisation

External model (e.g. Claude)

Enterprise / API access · contractual guarantees · sees masked data only

Files

The journey of an uploaded file

The bytes of the original file never reach the model, only the extracted, filtered and masked text.

01

Type check

Based on the real format of the content, not the file name.

02

Virus scan

Locally running scanner; on infection the file is quarantined and logged.

03

Text extraction

Processing runs on the instance; the raw file never leaves the machine.

04

Filtering

Credential detection, then full content filtering on the extracted text.

05

Storage

Both the file and the extracted text are stored encrypted on the instance.

Principles

Four principles every layer is built on

The platform does not rely on a single control, but on independent, layered defences.

01

Closed by default

If any security step fails, the request is rejected. No data leaves the organisation because a check was skipped.

02

Least privilege

Whatever is not explicitly allowed is denied. Raw conversation content is visible only to its own user by default.

03

Everything is logged

Every request, sign-in and admin action gets a traceable entry in a log that cannot be modified afterwards.

04

Dedicated instance

Your organisation gets its own isolated server: no shared database, key or log with any other client.