Skip to content
Sub-processor register

Every vendor that touches the platform.

A complete, published list of the sub-processors MediVault engages to deliver the Service, what each one does, where it operates, and — critically — whether it can access patient data. Most cannot.

Sub-processors
7
With patient access
0
Change notice
30 days
Jurisdictions
3
Last updated: 25 August 2026Document version 1.9
Demonstration content

MediVault AG is a fictional company built for a portfolio / demo website. This page is illustrative template content only — it is not real legal advice, it has not been reviewed by counsel, and it creates no actual rights or obligations. Do not rely on it for an actual product, business or legal decision.

Freight containers stacked in tiers at a port terminal.
Every link in the chain
Illustrative only — each vendor in the register below is one link in a custody chain for encrypted shards, and none of them holds a key that could open the cargo.

Name, purpose,
jurisdiction and access.

Data centre operators hold encrypted shards and nothing else — MediVault holds the only keys, in HSMs the data-centre operator cannot reach. No sub-processor below has standing access to decrypted patient data.

Sub-processorPurposeLocationData categoriesPatient data access
Swiss Data Centres AG — Rümlang (ZH-DC-01)Primary production vault — physical hosting and power/coolingRümlang, Kanton Zürich, SwitzerlandEncrypted data at rest, encrypted backupsNo — encrypted shards only, no key access
Swiss Data Centres AG — Glattbrugg (ZH-DC-02)Synchronous replica — synchronous replication facilityGlattbrugg, Kanton Zürich, SwitzerlandEncrypted data at rest, encrypted backupsNo — encrypted shards only, no key access
Swiss Data Centres AG — Meyrin (GE-DC-03)Disaster recovery vault — warm standby, 15-minute RPOMeyrin, Canton de Genève, SwitzerlandEncrypted data at rest, encrypted backupsNo — encrypted shards only, no key access
Helvetia Cloud Compute AGCompute, network and orchestration layer for the Swiss production environmentZürich, SwitzerlandEncrypted data at rest and in transit, infrastructure telemetryNo — encrypted shards only, no key access
Alpen Mail Relay SATransactional email delivery — account notifications, invoices, password resetsLausanne, SwitzerlandName, work email address, notification content (no clinical content)No
Sentry-class error monitoring provider (EU region)Application error and performance monitoring for the engineering teamEuropean Union (Frankfurt region), Standard Contractual Clauses in placeStack traces, request metadata, pseudonymised user identifiers — scrubbed of patient content by policyNo — scrubbing pipeline blocks clinical fields before export
ST Comp Holdings Sdn. Bhd.Engineering partner — product engineering, tooling and platform build supportMalaysiaSource code, non-production test fixtures, synthetic data onlyNo standing access to production or customer data

ST Comp Holdings Sdn. Bhd., our engineering partner (stcompholdings.com), builds and maintains platform tooling under a signed confidentiality and security agreement. Its engineers work exclusively against synthetic and non-production fixtures and hold no standing credentials to any production or customer environment.

30 days' notice,
a real right to object.

2.1

Notice before a change

Before adding a new sub-processor, or replacing an existing one in a way that changes its access to Customer Data, MediVault updates this register and emails every Enterprise and Spital account's registered administrator at least 30 days in advance.

2.2

Right to object

A Customer that reasonably objects to a new sub-processor on data-protection grounds may raise the objection in writing within the notice period. If MediVault cannot address the objection — for example by routing that Customer's data around the new vendor — either party may terminate the affected module without further liability, as set out in the data processing agreement.

2.3

Emergency replacement

Where a sub-processor must be replaced immediately for security reasons, MediVault will notify Customers as soon as practicable after the change and explain the circumstances, rather than delay remediation to preserve the standard notice period.

Register last reviewed: 25 August 2026Next scheduled review: February 2027
Sub-processors

Want change notices
sent to your team directly?

Enterprise and Spital customers can add a distribution list to receive sub-processor change notices automatically, in addition to the primary account administrator.

7 sub-processors · 0 with standing patient-data access