Azure EU Data Boundary & Netherlands Data Residency
The IITS platform is deployed exclusively on Microsoft Azure Netherlands infrastructure (West Europe region, primary; North Europe region, secondary failover). All data processing — including generative AI prompts, natural language completions, vector embeddings processed by Azure OpenAI Service, and data pipeline transformations — remains within European borders under the Microsoft EU Data Boundary.
Enterprise clients operating in financial services, healthcare, or municipal public administration face strict legal mandates dictating that sensitive corporate and personal data must not leave the European Economic Area (EEA). IITS meets this requirement by default — no special configuration is required.
Dutch Algorithmic Transparency & the Algorithm Register
The Dutch government actively promotes human-centred AI through the Dutch algorithm register, which currently houses over 700 algorithms contributed by governmental bodies including the Municipality of Amsterdam and the Social Insurance Bank (SVB). The IITS platform generates algorithmic documentation that aligns with register entry requirements.
This focus on transparency is a direct response to national controversies such as the childcare benefits scandal (toeslagenaffaire, 2018), in which opaque, biased algorithmic decision-making caused severe harm to thousands of families. IITS systems are designed to be fully auditable, with data lineage tracing and explainability as core, non-optional features — not add-ons.
The Dutch Ministry of Finance's algorithmic control framework identifies four critical compliance themes: governance and accountability, privacy, data and model integrity, and information security. Every IITS deployment maps to controls across all four themes, with formal documentation available for audit purposes.
Information Security
All IITS Azure deployments include access management, encryption at rest and in transit (AES-256 / TLS 1.3), vulnerability management, and incident response procedures. Azure Policy assignments are enforced at the subscription level to maintain consistent security posture across all environments.
Access control is implemented via Microsoft Entra ID with role-based access control (RBAC) at the Azure resource and data layer. Platform architecture enforces data minimisation by design: only data fields explicitly required for the AI model's defined purpose are ingested.