Last updated: [date of publication]
Version 1.0 · Effective [date] · Governed by the GDPR (EU) 2016/679 and Swedish law
Acceptance by use. By accessing or using Hyperkub AB's services, you (the "Customer") agree to this Data Processing Agreement on behalf of yourself or the entity you represent. This DPA forms part of Hyperkub AB's Terms of Service and is incorporated by reference. No separate signature is required.
Contents
- 1Parties and scope
- 2Definitions
- 3Roles and responsibilities
- 4Processing of personal data
- 5Information security
- 6Personal data breaches
- 7Data subject rights
- 8Sub-processors
- 9International transfers
- 10Confidentiality
- 11Audit rights
- 12Liability
- 13Term and termination
- 14Governing law
- AProcessing details
- BSub-processors
1. Parties and scope
1.1This Data Processing Agreement ("DPA") is between Hyperkub AB, a company incorporated in Sweden (org. no. 559127-7453), with its registered address at Upplandsgatan 32, 113 28 Stockholm, Sweden ("Hyperkub AB"), and the Customer accessing or using Hyperkub AB's managed Kubernetes service ("Customer").
1.2This DPA applies where Hyperkub AB processes personal data on behalf of the Customer in connection with Hyperkub, its managed Kubernetes service: the Hyperkub control plane, its API and MCP access, and the Kubernetes clusters the Customer runs with it, including their worker nodes, networking and storage (the "Services"), as described in the
Terms of Service.
1.3This DPA forms part of and is subject to Hyperkub AB's Terms of Service. In the event of a conflict between this DPA and the Terms of Service with respect to the processing of personal data, this DPA shall prevail.
1.4Hyperkub AB was founded in 2017 and operates exclusively under European jurisdiction. All infrastructure is physically and legally based within the EU/EEA.
2. Definitions
2.1Terms not defined here have the meanings given in the GDPR. In this DPA:
| Term | Meaning |
|---|
| Customer Data | Any personal data that the Customer or its end users submit to or process via the Services. |
| Data Controller | The Customer, who determines the purposes and means of processing Customer Data. |
| Data Processor | Hyperkub AB, acting on the Customer's instructions when processing Customer Data. |
| Data Subject | A natural person to whom personal data pertains. |
| EEA | The European Economic Area, including all EU member states, Iceland, Liechtenstein, and Norway. |
| GDPR | Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016. |
| Personal Data Breach | A breach of security at the infrastructure layer leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Customer Data. |
| Services | The managed Kubernetes service provided by Hyperkub AB, as described in section 1.2 and Appendix A: the Hyperkub control plane, its API and MCP access, and the Customer's Kubernetes clusters, including their worker nodes, networking and storage. |
| Sub-processor | Any third party engaged by Hyperkub AB to process Customer Data in connection with the Services. |
| Sub-processor List | The list of Sub-processors published at hyperkub.com/subprocessors, as updated in accordance with Section 8. |
3. Roles and responsibilities
3.1The Customer acts as data controller for Customer Data. Hyperkub AB acts as data processor, processing Customer Data solely on the Customer's behalf and in accordance with the Customer's instructions.
3.2Hyperkub AB provides infrastructure only. The responsibility boundary is as follows:
Hyperkub AB is responsible for
- Security and availability of physical and virtual infrastructure
- Network-level isolation between tenants
- Encryption of data in transit at the infrastructure layer
- Patching and maintenance of host systems and hypervisors
- Physical security of data centre facilities
- Infrastructure-layer audit logging
- Notifying the Customer of infrastructure-layer breaches
The Customer is responsible for
- All applications and workloads deployed on the infrastructure
- Configuration and security of Customer-managed software
- Access management for Customer's own users
- Compliance of the application layer with GDPR
- Ensuring a lawful basis for processing Customer Data
- Responding to data subject requests at the application level
- Backing up application-layer data as needed
3.3The Customer is solely responsible for the lawfulness of processing Customer Data, including ensuring that an appropriate legal basis exists under the GDPR for all processing carried out through the Services.
4. Processing of personal data
4.1Hyperkub AB shall process Customer Data only on documented instructions from the Customer. By using the Services and configuring them, the Customer provides its instructions for the purposes of this DPA. Hyperkub AB shall inform the Customer if, in its opinion, an instruction infringes the GDPR.
4.2Hyperkub AB shall not process Customer Data for its own purposes, including for analytics, product improvement, marketing, or model training. Hyperkub AB's personnel shall not access Customer Data except as strictly necessary to deliver, maintain, or support the Services.
4.3The subject matter, duration, nature, purpose, categories of personal data, and categories of data subjects are set out in
Appendix A.
4.4Hyperkub AB shall ensure that personnel authorised to process Customer Data are bound by appropriate confidentiality obligations.
5. Information security
5.1Hyperkub AB implements and maintains appropriate technical and organisational measures at the infrastructure layer to protect Customer Data, taking into account the state of the art, implementation costs, and the nature, scope, context, and purposes of processing. These measures include:
| Category | Measures |
|---|
| Encryption | Data encrypted in transit (TLS 1.2+) |
| Access control | Role-based access control; multi-factor authentication for all administrative access; least-privilege principle; SSH key-based authentication |
| Tenant isolation | Logical network-level isolation between Customer environments |
| Logging & monitoring | Infrastructure access and event logging; alerting on predefined operational thresholds |
| Backup & recovery | Automated backups of infrastructure data; tested restore procedures; backups stored within the EEA |
| Patch management | Regular patching of host systems, hypervisors, and infrastructure components; vulnerability scanning |
| Physical security | Infrastructure hosted in certified EU/EEA data centres with physical access controls, redundant power, and network connectivity |
| Incident response | Documented breach detection, containment, and notification procedures |
5.2These security obligations apply to the infrastructure layer only. The Customer is solely responsible for implementing appropriate security measures at the application layer, including the configuration, access control, and security of any software or workloads deployed on Hyperkub AB's infrastructure.
5.3Hyperkub AB shall assist the Customer with data protection impact assessments and prior consultations with supervisory authorities, to the extent such assistance relates to infrastructure-layer processing and the information available to Hyperkub AB.
6. Personal data breaches
6.1In the event of a personal data breach at the infrastructure layer, Hyperkub AB will notify the Customer without undue delay and no later than 48 hours after becoming aware of the breach. Notification will be sent to the contact address registered on the Customer's account.
6.2The notification will include, to the extent available at the time:
- The nature of the breach, including categories and approximate number of data subjects and records affected;
- Whether the breach originated at the infrastructure layer;
- Contact details for Hyperkub AB's point of contact;
- The likely consequences of the breach;
- Measures taken or proposed to address the breach and mitigate its effects.
Where information is not available at once, it will be provided in phases without undue further delay.
6.3The Customer is responsible for assessing whether to notify its own supervisory authority and data subjects, and for making any such notifications in accordance with Articles 33 and 34 of the GDPR. Hyperkub AB will provide reasonable assistance upon request.
6.4Hyperkub AB's notification obligations under this Section apply to infrastructure-layer breaches only. The Customer is responsible for detecting and reporting breaches originating at the application layer.
7. Data subject rights
7.1The Customer, as data controller, is responsible for responding to requests from data subjects exercising their rights under Chapter III of the GDPR (including access, rectification, erasure, restriction, portability, and objection).
7.2Hyperkub AB will, where technically feasible at the infrastructure layer, assist the Customer in fulfilling such obligations. If Hyperkub AB receives a data subject request directly, it will forward it to the Customer without undue delay and will not respond to the data subject directly.
8. Sub-processors
8.1The Customer provides general authorisation for Hyperkub AB to engage sub-processors. The current sub-processors are set out in the Sub-processor List at
hyperkub.com/subprocessors (see
Appendix B).
8.2Hyperkub AB will provide at least 30 days' notice before adding or replacing a sub-processor, by updating the Sub-processor List and notifying registered Customers by email. Such updates do not require a new version of this DPA. Customers who object to a new sub-processor on reasonable data protection grounds may notify Hyperkub AB in writing within the notice period.
8.3Hyperkub AB will impose data protection obligations on sub-processors that are no less protective than those in this DPA, and will remain liable for sub-processors' compliance.
9. International transfers
9.1Hyperkub AB stores and processes Customer Data exclusively within the
EEA. Hyperkub AB operates data centres in the EEA. A current list of data centre locations is maintained at
hyperkub.com/regions.
9.2Where a sub-processor processes Customer Data outside the EEA, Hyperkub AB ensures that an appropriate transfer safeguard is in place, such as Standard Contractual Clauses (SCCs) adopted by the European Commission or another valid mechanism under Chapter V of the GDPR. Transfer mechanisms in use are set out in the
Sub-processor List.
10. Confidentiality
10.1Hyperkub AB will treat Customer Data as confidential and will not disclose it to any third party except to sub-processors engaged in accordance with Section 8, or where required by law or order of a competent authority. In the latter case, Hyperkub AB will notify the Customer unless prohibited by law.
10.2Access to Customer Data is limited to personnel who require it for the performance of the Services. All such personnel are subject to confidentiality obligations.
11. Audit rights
11.1Hyperkub AB will make available to the Customer, upon written request, information reasonably necessary to demonstrate compliance with this DPA. Hyperkub AB may satisfy this obligation by providing relevant third-party audit reports or certifications, subject to appropriate confidentiality protections.
11.2Where the Customer reasonably determines that such documentation is insufficient, it may request an on-site audit conducted by an independent third-party auditor agreed upon by both parties. Such audits are at the Customer's cost, require a minimum of 30 days' advance written notice, and must be conducted during normal business hours in a manner that minimises disruption to Hyperkub AB's operations. Audit rights are limited to once per calendar year unless a confirmed breach requires otherwise.
12. Liability
12.1Hyperkub AB's liability under this DPA is subject to the limitations set out in the Terms of Service, except where such limitation is prohibited by applicable law.
12.2Hyperkub AB is not liable for any personal data breach, loss, or regulatory sanction arising from the Customer's application layer, including misconfiguration of Customer-managed software, insecure application code, or failure by the Customer to implement adequate security at the application layer.
12.3Each party is liable for its own obligations under the GDPR. If a supervisory authority fines one party because of the other party's failure, the party at fault compensates the other. Hyperkub AB's liability under this clause is subject to the limits in section 13 of the Terms of Service, except where the failure was intentional or grossly negligent, and is not excluded as a claim from a third party.
13. Term and termination
13.1This DPA is effective from the date the Customer first accesses or uses the Services and remains in force for the duration of the Customer's use of the Services.
13.2Hyperkub AB deletes Customer Data as set out in the Terms of Service: at once when the Customer deletes a cluster. When a cluster is suspended, including when Hyperkub AB ends the Services, Hyperkub AB may delete it and its Customer Data once 10 days have passed without the suspension being lifted. This applies unless applicable law or an authority requires continued storage. Hyperkub AB confirms the deletion in writing on request.
13.3The Customer is responsible for exporting or deleting any Customer Data residing within its own applications or workloads prior to or upon termination.
14. Governing law
14.1This DPA is governed by Swedish law. Any dispute arising from this DPA that cannot be resolved amicably shall be submitted to the exclusive jurisdiction of the Swedish courts, with the Stockholm District Court as the court of first instance.
14.2Hyperkub AB may update this DPA from time to time to reflect changes in law, supervisory authority guidance, or its services. Customers will be notified of material changes with at least 30 days' notice. Continued use of the Services after the effective date of a revision constitutes acceptance of the updated DPA.
Appendix A – Processing details
| Parameter | Description |
|---|
| Subject matter | Provision of the Services by Hyperkub AB: managed Kubernetes clusters, including their control plane, worker nodes, networking and storage, and the Hyperkub control plane, API and MCP access used to manage them. |
| Duration | For the duration of the Customer's subscription to the Services. |
| Nature | Infrastructure-level hosting, storage, transmission, and availability management of Customer Data. Hyperkub AB does not process Customer Data at the application layer. |
| Purpose | To provide managed Kubernetes clusters on which the Customer runs its applications and services. Hyperkub AB processes Customer Data solely as an infrastructure operator, without accessing or analysing its contents beyond what is technically necessary. |
| Types of personal data | Determined by the Customer. May include names, email addresses, and any other personal data the Customer or its end users introduce to the Services. The scope is entirely determined by the Customer's application. |
| Categories of data subjects | Determined by the Customer. May include the Customer's employees, representatives, and end users, as well as any other persons whose personal data the Customer processes through the Services. |
| Processing location | Within the EEA. Hyperkub AB operates data centres in the EEA; see hyperkub.com/regions for the current list. No processing outside the EEA except via sub-processors with appropriate transfer safeguards as set out in the Sub-processor List. |
Appendix B – Sub-processors
The sub-processors engaged by Hyperkub AB are listed in the Sub-processor List at hyperkub.com/subprocessors, which forms part of this DPA. It names each sub-processor, its location, its processing activity and the transfer safeguard in use. It is updated in accordance with Section 8, without a new version of this DPA.
Questions about this DPA?
Contact Hyperkub AB at legal@hyperkub.com. We are based in Stockholm, Sweden, and operate under Swedish and EU law.
This document is being finalised and will be published here shortly. Until then, email us at legal@hyperkub.com with any questions.