Data security
Your production data remains under your control.
PPI keeps you in control of your data while making the analysis traceable. You decide where your data is processed, which models may be used and whether external services are permitted at all.
01
Read-only
Access to production sources is read-only by default.
02
Strict client separation
Databases, roles, access and results are managed separately for each customer.
03
No raw data sent to the model
Models receive structured analysis results instead of complete production data.
04
You decide
External models can be excluded, approved case by case or explicitly permitted.
Deployment models
As local as you need it to be.
The same security principles apply whichever deployment model you choose. Processing starts locally; external models are used only if your agreed policy allows them.
01 · LOCAL
On-premises
PPI can operate within your own infrastructure. Production data and models do not leave your system environment.
02 · CONTROLLED
Local, with controlled extensions
Analysis starts locally. An external model may be added only where a defined use case requires it and your policy permits it.
03 · APPROVED
External models
Only minimised, structured information is transferred. The provider, model and transfer are documented so the process can be traced.
Security architecture
Security begins with the system design.
PPI keeps data, access and results separate. Analyses can be reproduced, and PPI never makes automatic changes to equipment or production systems.
Data minimisation
Only the data needed for a particular analysis is processed.
Client separation
Customer data, configurations, results and access rights remain separate.
Controlled access
Access to data sources is limited to the permissions needed for the task.
Traceability
Data sources, analysis steps, models, results and approvals are documented.
Data lifecycle
Retention, backups and deletion are agreed for each customer and deployment.
People decide
PPI analyses and recommends. Production changes are made only after technical approval.
Compliance and quality
Preparing carefully, without claiming more than we can substantiate.
The architecture is being designed around relevant European requirements and documented quality management. Final classifications and reviews will take place before each pilot or customer deployment.
In preparation
EU AI Act
Before deployment, we will formally establish the risk classification, provider and deployer roles, technical documentation, logging and human oversight.
Privacy by design
GDPR
PPI follows the principles of purpose limitation, data minimisation, limited retention, integrity and confidentiality. The assessment is made for the specific use case.
Preparing for certification
ISO 9001:2026
Our management manual, documented working practices and audit agent already provide a robust foundation for formal certification.
Planned option
Shared knowledge base
Shared knowledge. Separate customer data.
We plan to let customers contribute voluntarily to a shared knowledge base. This could reveal patterns across companies without exposing raw production data or the identities of participating customers.
- Participation is entirely voluntary
- PPI remains fully usable without participation
- no raw production data in the shared pool
- only technically reviewed, irreversibly anonymised or sufficiently aggregated patterns
- contractually defined purpose and usage rights
- no conclusions about individual companies, plants or people
Data flows
What leaves the plant?
The answer depends on the selected deployment model. Raw production data is transferred neither to external models nor to a shared data pool. When PPI-owned hardware is used, processing takes place within the EU.
| Operating mode | Does raw production data leave the plant? | Processing |
|---|---|---|
| On-premises | No | Remains within your infrastructure |
| PPI infrastructure | Only to the explicitly agreed extent | On PPI hardware within the EU |
| External model | No | Only minimised information under the customer policy |
| Voluntary data pool | No | Only approved, anonymised or aggregated information |
Which security model fits your plant?
The right setup depends on your data, your systems and your security requirements.