Data security with AI: your people build, your rules apply
Many people may build, but only what a person releases goes into operation. The AI sees no personal data while building, and everything runs on your server. This page is written for your IT, your data protection and your works council.
- Runs on your server
- Reads only, never writes
- GDPR ready
- First result in weeks
Six rules that always apply
Data stays with you
Platform, analysis copy, applications, roles and logs run on your server. An installation just for you.
Masked while building
In development, the copy holds no personal data. The AI has no path to the clear data; only released applications read it.
Release by people
New applications first run in a test stage. They go into production only when a responsible person releases them.
Rights follow the person
The platform assigns roles per person and application. Each role sees only its own section.
Read only
Onagero connects with users who may only read. Nothing is written to ERP or machines.
Everything logged
Logins, rights decisions and security-relevant actions are recorded in an exportable log.
What stays on your server
- The Onagero platform, an installation just for you
- The analysis copy of your data and the data map
- All applications, roles, definitions and logs
- Backups, on your schedule
What the language model sees
- Masked excerpts of individual requests
- No complete tables, no database dumps
- Nothing that concerns other customers
Which model provider is used under which terms is stated in the contract. You see it before you sign.
What we supply for your review
- An overview of all sources and columns read
- The list of masked fields
- The path of every request to the model
- Logging, retention and deletion
- Subcontractors and processing locations
- The data processing agreement
What you never have to do
- Upload data to a third-party cloud
- Grant write access to your ERP
- Rebuild or replace your ERP
- Trust an application that nobody has released
Questions from IT and data protection
Is Onagero GDPR-compliant?
Yes. Onagero is built for GDPR-compliant use: platform and data run on your server, during development the AI sees only masked data, rights follow the person, and security-relevant actions are logged. You receive the data processing agreement and the technical documentation before the start.
Does our data leave the building?
Your databases, the analysis copy and all applications stay on your server. The language model receives only the masked excerpts of individual requests, never whole tables or database dumps.
Does the AI see personal data?
Not while building. During development the AI works on a copy that holds no personal data, and it has no path to the clear data. Only a released application reads what its roles allow.
Who decides what goes into operation?
A person. An application built by the AI first runs in a test stage; it goes into production only after release by a responsible person.
Who may see an application?
Roles determine that; the platform assigns them per person and application. Each application learns from the platform which role the person has, instead of keeping its own user lists.
Does Onagero share a database with other customers?
No. Every customer gets its own installation with its own credentials and its own backups.
Can an application write to our ERP?
No. Onagero connects with users who may only read. Your ERP remains the leading system.
Is it logged who does what?
Yes. Logins, rights decisions and other security-relevant actions are recorded in a log that you can view and export.
We answer your IT’s questions directly
Write to us which documents your IT or data protection would like to see in advance. You get them before the first conversation.
Request documents →