# Data Export, Formats and Jurisdiction Register

**GPU Server Hub — version 1.1 dated 9 September 2026**  
**English translation revision EN-1**  
Public path on the Provider's website: **/data-export-register/**

This document is an English translation provided for convenience. The Polish version 1.1 is binding. In the event of any discrepancy, the Polish version prevails, subject to the priority of an individually agreed Order and any mandatory provisions of law.

This Register supplements section 12 of the Terms available at **/terms/**. It applies to the extent that the Service is subject to Chapter VI of Regulation (EU) 2023/2854 (Data Act).

## 1. Exportable data and assets

| Category | Scope | Format or structure | Standard method |
|---|---|---|---|
| Customer input data and content | files, databases, models, containers, images, secrets and other data stored by the Customer | format and structure selected by the Customer; the Provider does not impose a schema | protocol operated by the Customer, such as SSH/SFTP, rsync, HTTPS or a database's native export facility |
| output data | computation results, application logs, models and artefacts generated by the workload | format selected by the Customer | as above |
| volumes and system images | logical or sector-level content of drives | native file system; upon a separate request, a raw `application/octet-stream` image | network transfer or encrypted storage medium |
| Customer configurations | scripts, manifests, containers, operating-system and application configurations stored on the Server | native format, text, JSON, YAML or another format selected by the Customer | network transfer |
| Service metadata required for migration | hardware specification, port configuration and IP/DNS assignments, Service periods, resource usage, reports and technical logs relating to the Customer's configuration | PDF, CSV, JSON or plain text | file transferred through a secure channel |
| data generated jointly through use | events and telemetry available to the Provider which relate to the Server and are needed to reproduce the configuration or achieve functional equivalence | CSV, JSON or plain text | file transferred through a secure channel |

The Provider does not offer a managed application layer or its own virtual-machine format. File systems, database structures and application formats are selected by the Customer.

## 2. Exclusions

The following are not transferred:

- ownership of or the right to use IP addresses after termination of the Service; however, the list of prior assignments and settings necessary for reconfiguration is exported;
- other customers' data;
- the Provider's credentials, detailed topology of the protected network and security rules whose disclosure would create a vulnerability;
- code, automation and documentation constituting the Provider's intellectual property or trade secrets;
- internal analyses not generated directly or indirectly through the Customer's use of the Service.

Exclusions are interpreted narrowly and may not be used to impede switching provider. Upon request, the Provider will explain a specific exclusion.

## 3. Export during the Service

1. During the active Service, the Customer has administrative/root control over its system and may copy data using protocols that it installs itself.
2. Maximum bandwidth corresponds to the port parameter in the Order, taking account of current traffic, protocol overhead, drive performance and network events.
3. Upon request, the Provider supplies available metadata in one of the formats specified in the table.
4. A raw image or release of a storage medium requires prior selection of a secure channel, encryption, means of delivery and the cost of the storage medium or transport itself.

## 4. Minimum retrieval method after the transitional period

1. For 30 calendar days, the Provider retains the original storage media, keeps them out of reuse, and accepts a retrieval request at contact@gpuserverhub.com.
2. Within 2 business days after a request, the Provider connects the storage media to the original or an isolated Server and provides authenticated remote transfer. Access continues until the end of the 30-day period and, for a request made in the final part of that period, for at least 7 days.
3. The retrieval port is at least 1 Gbit/s or the parameter specified in the Order if that parameter is lower. Actual speed depends on the storage media, protocol and destination network.
4. If remote access is technically impossible, the Provider offers an encrypted raw image or encrypted storage medium without a switching charge; the Customer may bear the previously accepted cost of the medium and shipping.
5. The Customer provides any necessary keys solely for its own system or decrypts the data itself. The Provider does not retain the Customer's encryption keys.
6. A physical drive failure does not create a copy that was not made previously and may restrict retrieval.

## 5. Infrastructure jurisdiction

| Element | Location and jurisdiction |
|---|---|
| Server and Customer Data on its drives | 4DataCenter, Katowice, Poland; Polish and EU law |
| power, cooling and remote hands | 4DataCenter/Quicktel, Katowice, Poland |
| Bestconnect network and addressing | infrastructure controlled by Bestconnect in Poland |
| Order system, Service control and security logs | Bestconnect's own infrastructure in Poland |

Adding an element processed in another EEA state requires an update to the Register and, where applicable, subprocessor notification. Customer Data is not normally located outside the EEA.

## 6. Protection against unlawful access by third-country authorities

The Provider:

- restricts physical and logical access and logs interventions;
- imposes confidentiality on staff and subcontractors;
- encourages the Customer to encrypt drives with a key kept outside the Server;
- assesses the legal basis and scope of each authority request, discloses only the required minimum and documents the response;
- informs the Customer unless prohibited by law;
- challenges a manifestly unlawful request where an effective legal remedy is available;
- does not create voluntary, permanent access for an authority of a third country.

## 7. Amendments to the Register

An amendment affecting an ongoing Agreement is provided to the Customer, together with the complete new text, at least 30 days in advance unless an urgent legal or security obligation requires shorter notice. The version accepted with the Order is archived.