Security & data protection

Your SAP® data stays yours.

Data protection and the responsible handling of customer data are core principles of everything we build. Pseudonymised processing, the model of your choice, and hosting in Germany.

01 — Data protection & security

Three principles we build everything on.

Data protection and the responsible handling of customer data are central guidelines for how we develop EIS, QCC and every other Quatelio product — and how we work in your systems as consultants.

01

Privacy by design

Personal data is pseudonymised before any AI processing. The language model only sees anonymous records — it cannot trace them back to real people.

  • Names, IDs and bank data replaced before processing
  • Re-identification only inside your tenant
  • No training on your own data needed
02

Bring your own model

You decide which language model runs: one we provide, or your own model from the provider of your choice — to fit your IT compliance rules.

  • Quatelio-provided model, hosted in Germany
  • Your own Azure OpenAI, AWS Bedrock or Mistral tenant
  • Local open models on your own hardware
03

GDPR-compliant hosting in Germany

Our services run in ISO/IEC 27001 certified data centres in Germany, in line with the GDPR and the EU AI Act.

  • Data stays in Germany
  • Data processing agreement (AVV) per Art. 28 GDPR
  • Prepared for EU AI Act transparency duties
02 — How your data flows

What a language model sees — and what it doesn't.

Every request from EIS or QCC passes the same path. Your SAP® authorisations apply, personal data is pseudonymised, and every step is written to the audit log.

Source
Your SAP® system
S/4HANA or ECC — data stays where it is.
Transport
Secure connection
SAP® Cloud Connector or RFC with a read-only technical user.
Control
Quatelio gateway
Authorisation check, pseudonymisation, audit log. Keys stored separately.
Reasoning
Language model
Ours in Germany — or yours. Sees anonymous records only.
✓Answers are re-identified only inside your tenant ✓Calculations run in code, not in the model ✓Nothing is written to SAP® without approval
03 — Deployment

Run it where your compliance rules say.

Most common

Quatelio Cloud

Managed by us, hosted in Germany.

  • ISO/IEC 27001 certified data centre
  • Separate tenant per customer
  • Fastest start — days, not months

Your SAP® BTP

Runs in your own SAP® BTP account on Kyma.

  • Your BTP region and contracts
  • SAP® Destination and Connectivity services
  • Your identity provider

On-premises

Runs in your data centre, next to your SAP® system.

  • No data leaves your network
  • Works with local open-source models
  • Your operations and backup rules
04 — Controls

The details your security team will ask about.

Encryption

TLS in transit, encryption at rest. SAP® credentials and keys are kept apart from application data.

SAP® authorisations apply

Users only see what their SAP® roles allow. We never work around your authorisation concept.

Read-only by default

Analytics and assessments only read. Write access exists only where a product needs it.

Human approval

Every change QCC proposes is shown as a diff and applied only after a person approves it.

Audit trail

Every question, data access and change is logged — who, what, when and why.

Single sign-on & roles

Login via your identity provider (SAML or OpenID Connect) with role-based access.

Tenant isolation

Your data is never shared with other customers and never mixed into another tenant.

Deletion on request

Data is deleted when you end the contract or ask us to — documented in the AVV.

FAQ

Good questions to start with

Is our company data shared with other customers?

No. Every customer runs in a separate tenant. Your data, prompts and results are never shared with or visible to other customers.

Do language models see personal data?

No. Personal data is pseudonymised before it reaches a model. The model works with anonymous records and cannot trace them back to real people; names are put back only inside your tenant.

Is our data used to train AI?

No. Your data is never used to train our models or any provider's models — and our products do not need training on your data to work.

Can we run everything on-premises?

Yes. EIS and QCC can run in your own data centre or your SAP® BTP account, with a local or your own language model.

Do you sign a data processing agreement?

Yes — an AVV according to Art. 28 GDPR, together with our technical and organisational measures (TOMs).

How do you handle the EU AI Act?

We document how our AI features work, keep a person in the loop for every change, and give you the information you need for your own AI Act duties.

Need our security documentation?

Request our TOMs, data processing agreement and architecture overview — or talk to us about your requirements.

Request documentsContact us