Grapesc Cloud Personal data protection VM data processing terms Česky English

VM data processing terms

Processor: GRAPE SC, a.s., company ID 25708783, VAT ID CZ25708783, Karlovo náměstí 559/28, Nové Město, 120 00 Praha, Česká republika, contact info@grapesc.cz.

Customer: the customer identified in the cloud service contract or order. The customer is the controller when determining processing purposes and means; when acting for another controller, these are subprocessing terms and the customer must be authorised to engage us.

1. Agreement, subject and duration

These terms govern processing under Article 28 GDPR when hosting customer VMs, disks and agreed backups. They become contractual only through express incorporation in a contract or order and acceptance by both parties. Merely publishing this page or logging in does not conclude the agreement. Existing customers need a demonstrable addendum or equivalent contractual incorporation. Version: 2026-10-06.

Processing continues for the service duration and thereafter only as necessary for agreed return or deletion, or a specific legal requirement. The Czech text is the reference version; this English text explains the same terms.

2. Processing description

The purpose is hosting, availability, security and administration ordered by the customer. Operations include storage, transmission for service delivery, backup, restoration and deletion; application or file administration requires customer instructions.

The customer determines data subject categories, for example customers, employees, suppliers and application users. Data may include identity, contact, commercial, employment and operational information. Special categories and criminal conviction data require the customer to satisfy the relevant legal conditions and verify the adequacy of service security. Not every VM configuration is suitable for every high-risk processing activity.

3. Instructions, access and confidentiality

We act only on documented customer instructions, including international transfers. Instructions include the contract, order, authorised support requests and actions by authorised interface users. Where law requires processing, we inform the customer beforehand unless legally prohibited. We immediately inform the customer of instructions that infringe GDPR or other applicable data protection rules.

The customer controls access inside its VM and its applications and users. We do not routinely inspect its content. Hosting nevertheless entails virtualisation administration; the interface can perform console, SSH and file operations on customer instructions. These terms do not promise that access is technically impossible. Any authorised operator access requires a specific operational reason or instruction and is limited to what is necessary. Authorised personnel must be bound by contractual or statutory confidentiality.

4. Security measures and responsibilities

We implement risk-appropriate Article 32 measures: individual accounts, permissions, protected administrative access, secure transmission, infrastructure updates, separation of customer access, controlled backup and recovery, incident procedures and regular effectiveness review. Cloud passwords are hashed, optional GitHub tokens encrypted and users can enable two-factor authentication.

Unless administration is explicitly ordered, the customer secures and updates its OS, applications and credentials. VM disk encryption with customer-held keys is not automatically included. Backup and restoration parameters follow the order; this does not guarantee restoration from backups that were not ordered or verified.

5. Subprocessors and transfers

The declared hosting model uses the operator's own infrastructure. The current list of any subprocessors and processing locations must be confirmed to the customer when concluding the contract; absence of subprocessors cannot be assumed without verification.

Engaging a subprocessor requires prior specific or general written customer authorisation. With general authorisation, intended additions or replacements are notified at least 30 days in advance, allowing reasoned objections. An unresolved objection prevents the proposed subprocessor from handling the affected data. Equivalent relevant obligations are imposed on subprocessors and we remain responsible for their performance. Transfers outside the EEA require documented instructions and a Chapter V mechanism. Optional GitHub integration follows explicit authorisation; it does not generally authorise transfer of entire VM contents to GitHub.

6. Assistance and incidents

Taking account of the processing and available information, we assist with individual rights, security, breach notifications, impact assessments and prior consultation. Requests about personal data inside a customer VM are referred to the customer; we do not determine the purposes of its database.

We notify the customer of personal data breaches without undue delay after becoming aware. Available details include the nature, affected categories, likely consequences, measures and a contact. Further information is supplied progressively. This does not replace the customer's obligation to notify the authority within 72 hours where GDPR requires it.

7. Return and deletion

Before termination the customer chooses return or deletion. Return is arranged securely, for example by allowing download or export before removing the VM. After return, or on deletion instructions, we delete personal data and existing copies unless law requires retention; any such requirement is explained to the customer.

VM and backup removal takes place on Proxmox infrastructure and must cover relevant storage, snapshots and replicas. Acceptance of an asynchronous task does not prove completed deletion. Confirmation is available on request after completion. Ordinary cloud logs have a maximum 24-hour retention, which does not set retention for ordered customer backups. Deleted services must not be assumed recoverable.

8. Accountability and audits

We provide information needed to demonstrate Article 28 compliance and allow audits, including inspections by the customer or its auditor. The parties arrange secure procedures, protection of other customers and reasonable operational conditions without effectively excluding audit rights. Questions, instructions and incident reports: info@grapesc.cz.

info@grapesc.cz

Document version: 2026-10-06