Trust and security

Your data, inside your perimeter.

A data processing agreement before we touch a single file, a dedicated EU server and every query logged. What you can't see at the source, you can't see by asking either.

Security

How information is handled.

Infrastructure

A dedicated EU server, contracted in your name.

No intermediary and no markup. The information stays inside your perimeter.

Zero retention

The models don't store your data or train on it.

Data processing agreement

Signed before we touch a single file.

Inherited permissions

What you can't see at the source, you can't see by asking either.

  • By role and by source
  • By rows, columns and actions
  • The same for people and agents

Personal data

Pseudonymised before indexing, with the key table encrypted separately.

Audit

Who asked, what they received and from which source.

Setup

Four phases. Read-only until the criteria are validated.

  1. 01

    Assessment

    Sources, pilot domain and data processing agreement.

  2. 02

    Modelling

    System connections and the business ontology.

  3. 03

    Capture

    Criteria, corpus and read connectors via MCP.

  4. 04

    Go-live

    Agent, manual and FAQ, permissions, audit and training.

    Validation

Questions about security

Where is my data processed?

On a dedicated EU server contracted in your name. On-premise option on request.

Does the model provider see my data?

The models run with zero retention: they don't keep what they receive or use it for training. And they only receive what each question needs.

Who sees what?

Each person and each agent sees only what their token allows, inherited from the source system.

What about personal data?

It is pseudonymised before indexing. The mapping table is stored encrypted and separately.

Does KnowOS write to my systems?

Not in the first phase. After that, only actions approved by a person with permission.

Show us a question that takes an afternoon today.

A 30-minute session on a real case: a historical price list, an internal procedure, a query that today ends up as a request to IT. You leave with the scope of sources and a fixed price.