Good service starts with trust.
From support tickets to website chats: see how inbrix protects customer data, where it is processed and which agreements apply.
Customer data is not training material.
Protect credentials, keep organisations separate and make AI processing transparent.
Encrypted credentials
Credentials are stored with additional AES-256-GCM encryption.
The AI runs in Europe
Your tickets are processed in the EU – by the language models too. On every plan.
Made & hosted in Germany
Our own Kubernetes cluster at Hetzner in Germany, in certified data centers. No data leaves for a third country.
Remove sensitive details before AI search
Detected sensitive information is removed before content enters AI search.
Protected access links
Signed links protect access to shared content.
Display emails in isolation
Email content is displayed in isolation. Scripts and remote content are blocked.
Keep customer data separate
The database enforces separation between organisations in addition to application-level checks.
No training on customer data
Your content is not used to train AI models.
A key for each organisation
Each organisation has its own key. It is destroyed on deletion; you can export your data beforehand at any time.
Transparency obligation met – with nothing to configure.
Article 50 requires people to be told when an AI is talking to them. inbrix does it automatically: in the chat widget, the web form and every bot email – including a header marker and a clear path to a human.
What data protection officers ask first.
Where is the data hosted?
Is inbrix itself ISO 27001 certified?
Is inbrix GDPR-compliant?
Is our data used for AI training?
How are tenants isolated?
How is data encrypted?
What happens on deletion?
Does inbrix meet the EU AI Act?
Is ISO 27001 a dealbreaker for you?
Tell us with one click. It shows us how much our own certification matters to customers – and if you like, we'll reach out the moment it's in place.