Skip to main content

Security & Trust

How Zation protects your data — technically and organizationally. These are the technical and organizational measures referenced in Clause 5.2 of the DPA.

Customer Isolation​

  • Your data is logically isolated from every other customer's data.
  • Every data access is scoped to your organization and enforced on the server — no client request can reach another customer's data.
  • Cross-customer access is covered by automated tests on every release.

Data Residency — Switzerland​

  • All customer content and personal data we store is stored in Switzerland North, and the application logic that processes it runs there.
  • Backups stay within Switzerland. The databases are single-region and are not geo-replicated across borders.
  • Limited operational metadata required to authenticate and route requests may be processed by Microsoft identity services within the EEA under appropriate safeguards (see Sub-Processors).

Three components run outside Switzerland North, and we name them rather than round the statement off:

  • Ingress. api.platform.zation.io is published through Azure Front Door, which routes by anycast and may transit points of presence outside Switzerland and the EEA. Caching is switched off on the API route, so no response is stored at an edge location; the origin and all storage stay in Switzerland North.
  • Frontend delivery. platform.zation.io is served from Azure Static Web Apps in West Europe — static files only, no personal data — because that service is not offered in Switzerland North.
  • Platform email. Notification and invitation email is dispatched through Zation's own Microsoft 365 tenant (EU), which processes recipient name, email address, and message content.

The full picture, including where Microsoft Entra ID and Microsoft Graph API process data, is in Clause 7 of the DPA.

Encryption​

  • Customer data is encrypted in transit (TLS 1.2 or higher).
  • Customer data is encrypted at rest.

Secrets Management​

  • Secrets and credentials are held in a dedicated, managed secrets store.
  • No secrets live in application code or configuration files.
  • Services authenticate using managed identities rather than shared credentials.
  • Secrets are rotated on a regular schedule.

Logging​

  • No personal data in logs — logs capture only operational fields.
  • Where an identifier is unavoidable, it is hashed.
  • Logs are retained for a limited period and then deleted automatically.

Audit Trail​

  • Every write operation produces an audit log entry.
  • Security-relevant actions — such as scheduling or approving optimisations — are recorded per user.
  • Audit entries are permanent and cannot be modified or deleted.
  • They record the action and the operator who performed it — not the personal data of your end users.
  • Customer admins can view their own audit trail in the Portal.

Network controls​

  • All Platform traffic is served through a global edge layer with DDoS protection and TLS termination; application origins accept traffic from that edge layer only.
  • The Platform's outbound connections to your Microsoft environment originate from a fixed, published IP range (20.250.10.216/30), so you can restrict access on your side to exactly these addresses.
  • Organizations with strict network policies (for example, banks) can enable a per-organization inbound IP allowlist: sign-ins to your Platform tenant are then accepted only from the IP ranges you define.

The egress range is documented under Permissions. Authenticated customers find the Conditional Access and allowlist configuration guides in the private documentation.

Data breach notification​

If we become aware of a personal data breach affecting your data, we notify your admin contact without undue delay, as required by the DPA. The notification covers the nature of the breach, the data categories affected, and the measures we have taken. This supports your duty to notify the Federal Data Protection and Information Commissioner (FDPIC) under Art. 24 revDSG.

Confidentiality​

Everyone we authorize to process your data is bound by confidentiality obligations. Access is limited to personnel who need it to deliver the Platform services.

Data subject requests​

If you receive a request from a data subject (for example, access or deletion), we assist you in responding. Because we process data only on your instructions, such requests are handled through you as the controller.

For detailed questions on auth and permissions, see Permissions.