Information Security
iosys develops and integrates ERP, MES and production systems for manufacturing companies. This page describes how we handle your information.
What we hold, and what we do not
We work with our customers' source code, contracts and requirements.
We do not process production data from your systems. ERP, MES and machine data stay in your environment, in your own tenant. We develop and hand over; operation and data ownership remain with you.
Test and proof-of-concept environments contain no real customer data.
Where your material is stored
| Location | |
|---|---|
| Customer documents, contracts, requirements | Nextcloud at Infomaniak, Geneva |
| Development environments | Switzerland and EU (Railway, Amsterdam) |
| Source code | GitHub (US), under a data processing agreement |
| Identity and email | Microsoft 365 (EU) |
Where a provider offers a Swiss or EU region, we use it.
Providers we use
We maintain a supplier register with a risk assessment and a review date for every entry. The providers relevant to customer information:
| Provider | Purpose | Location | Certifications |
|---|---|---|---|
| Infomaniak | Documents, servers | Switzerland | ISO 27001:2022, ISO 9001, ISO 14001, ISO 50001 |
| Microsoft | Identity, email, cloud | EU / US | ISO 27001, ISO 27017, ISO 27018, ISO 27701, SOC 1/2/3 |
| GitHub | Source code, CI/CD | US | ISO 27001, SOC 1/2 Type II, PCI DSS, CSA STAR |
| Cloudflare | DNS, TLS, WAF | US | ISO 27001, ISO 27701, PCI DSS, SOC 2 Type II |
| Anthropic | AI in development | US | ISO 27001, ISO 42001, SOC 2 Type II |
| Bitwarden | Credentials | EU | ISO 27001:2022, SOC 2 Type II, SOC 3 |
| Linear | Project management | US | ISO 27001:2022, SOC 2 Type II |
| Railway | PoC and dev environments | EU (Amsterdam) | SOC 2 Type II, SOC 3 |
| Optiverse | Meeting assistance | Switzerland | per provider statement; no training on customer data |
| Probo | Compliance management | self-hosted | provider has no access to our instance |
Access
- Every account is personal. No shared logins.
- Multi-factor authentication is enforced for access to source code.
- Access to source code is granted through roles rather than blanket permissions, and can therefore be withdrawn in one place when someone leaves.
- Credentials live only in dedicated vaults, never in documents, tickets or chats.
Development
- Changes to the main branch go through pull requests. No direct overwriting, no rewriting of history.
- Separate environments for development, test and production.
- Dependencies are monitored for known vulnerabilities.
- Delivery is automated, not manual.
Artificial intelligence in development
We use AI tools in development, and we are open about how.
For every combination of data class and customer it is defined which tool is permitted. Credentials and secrets never go into an AI request. Results are reviewed before they are delivered: responsibility rests with the person, not the tool.
Customer-specific requirements take precedence. If you wish to restrict or exclude the use of AI for your projects, we will follow that; we record it when the project is set up. Conversely, we tell you actively where AI is used.
The providers we use are certified to ISO 27001 and SOC 2, one of them additionally to ISO 42001, the international standard for AI management systems.
Where work happens
Our engineering work takes place on Swiss and EU infrastructure. Where contributors work from outside the EU and Switzerland, access is via Swiss infrastructure; no local copies are created.
Incidents
We report security incidents to you within the contractually agreed deadlines. Internally: immediate notification of management, containment before root-cause analysis, and every incident is documented, including the one that turned out harmless.
Statutory reporting duties under the Swiss FADP and the GDPR are recorded with their deadlines.
Security-relevant reports: [email protected]
Evidence
Our information security management system is aligned with ISO 27001:2022. We maintain controls, risks, suppliers and evidence in a dedicated system and review them regularly.
Further material, from the information security policy to the statement of applicability and the detail on individual controls, is available to prospective customers on request.
Last updated: August 2026. Questions about this page: [email protected]