Data Export, Formats and Jurisdiction Register

GPU Server Hub — version 1.7 dated 19 October 2026
Editorial revision r1 — English translation EN-1
Public path on the Provider's website: Data Export, Formats and Jurisdiction Register

This document is an English translation provided for convenience. The Polish version 1.7 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 and describes export during the active Service and the rules for ending access and deleting data. It does not exclude mandatory provisions, including Chapter VI of Regulation (EU) 2023/2854 (Data Act), to the extent that they apply to the Service.

1. Exportable data and assets

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 tools and protocols configured by the Customer.
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. The Customer independently performs logical or sector-level drive exports during the active Service or under an agreed return procedure. The Provider does not provide drive imaging, managed migration or restoration of Customer Data as standard. The Customer should complete export and verify backups before the Service ends, or request return or switching beforehand under section 4.6.

4. End of access and data deletion

1. The start, end and extension of the Service term are governed by sections 4.8, 4.10 and 11 of the Terms. At the end of the paid term without an effective extension, the Provider disables access and begins erasing Customer Data without undue delay as soon as technically feasible, unless an erasure hold applies. The Customer chooses deletion when entering into the Agreement and may change that choice before the Service ends under section 12.11 of the Terms.
2. There is no additional general data-retention or retrieval period after the Service ends. The time technically needed for erasure does not provide additional access or data retrieval. A prior return request and periods required for switching providers are governed by paragraphs 5 and 6.
3. A confirmed hardware failure requiring replacement of the Server is subject to section 6.8 of the Terms: data on the faulty Server is deleted as soon as technically feasible, including before a Replacement Server is available and before the Customer restores its environment, subject to erasure holds under sections 12.7 and 12.11 of the Terms. The Provider does not transfer drives or migrate data. The Customer restores its environment from its own backups.
4. The Provider does not retain the Customer’s encryption keys. A physical drive failure may prevent export of data that the Customer has not previously copied. The duty to protect storage media and securely delete data remains governed by the Terms and their annexes.
5. Mandatory law and the choice to return personal data take precedence under section 12.7 of the Terms and Annex 1. Switching covered by Chapter VI of the Data Act is subject to the notice, transitional and retrieval periods, extension rules and erasure holds specified there. This does not create a general 30-day retention period for every ended Service or a separate data-storage environment. An express choice of deletion without switching is a separate procedure.
6. Return of data or switching must be requested before the Service ends through the portal form or at gpu@bestconnect.pl under section 12.11 of the Terms. The form confirms acceptance and immediately suspends automatic erasure. The Provider handles email and ensures suspension upon receipt of an effective instruction; emails are not automatically processed by the erasure mechanism. The form is recommended for urgent requests. The Provider confirms how and when export will be performed. Return does not constitute managed application migration.
7. During an active Service, the Customer may also request irreversible erasure of data from all Server drives through the portal. Section 12.10 of the Terms applies; successfully erased data is not retained for retrieval, and erasure alone does not shorten the paid term.

5. Infrastructure jurisdiction

Starting to process data in another EEA state requires an update to the Register and, where applicable, subprocessor notification. The locations above describe the Provider’s infrastructure. Remote access by the Customer or other recipients outside the EEA and data exports by the Customer require separate consideration of actual data flows and, where applicable, Chapter V GDPR. The Server’s location in Poland does not, by itself, exclude a transfer outside the EEA. Part E of Annex 1 to the Terms applies.

6. Protection against unlawful access by third-country authorities

The Provider:

• restricts physical and logical access and logs interventions;
• requires staff and subcontractors to maintain confidentiality;
• 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.