Operator and controller: GRAPE SC, a.s., company ID 25708783, VAT ID CZ25708783, registered office: Karlovo náměstí 559/28, Nové Město, 120 00 Praha, Česká republika. Privacy contact: info@grapesc.cz.
1. Scope and roles
This notice covers cloud account administration and operation. GRAPE SC, a.s. is the controller for account and service security data. For personal data stored by customers in their VMs, we provide hosting on their instructions as a processor or subprocessor. See the VM data processing terms.
2. Data and sources
We process email, username, password hash, account ID, creation and modification dates, language, permissions and security settings. Depending on features used, we also hold an avatar, team memberships, shared VM access, assigned services, payment status and service linkage identifiers. Optional GitHub integration stores a GitHub account identifier and an encrypted OAuth token.
Operation and security can generate IP addresses, access times, session identifiers, task and command records, errors and operation history. Records may contain user-supplied data; passwords and access tokens do not belong in ordinary logs. Data comes from the user, an authorised administrator of their organisation, service operation and, when connected, GitHub. Contact us for further information about sources.
3. Purposes and legal bases
Account creation and the contracted service are based on Article 6(1)(b) GDPR when the individual is a contracting party. Access administration for a business customer's personnel is based on the legitimate interests of providing and administering the service, under Article 6(1)(f). Security, availability and troubleshooting rely on the legitimate interests of the operator and customers. A specific applicable legal obligation may require processing under Article 6(1)(c).
Email and login credentials are necessary for standard account access. Avatars and GitHub integration are optional. No general GDPR consent is required for essential account operation. GitHub OAuth authorisation instructs the optional integration and is not blanket consent to all processing. We do not carry out advertising profiling or solely automated decisions producing legal or similarly significant effects.
4. Retention and account closure
Account data is kept while the account and service are maintained. After account closure successfully completes, the account is immediately removed from the live database together with directly associated database logs and related records. Any specific legal retention requirement is handled separately. VM and backup deletion is a separate infrastructure process. Account deletion does not replace an instruction to delete customer VMs; coordinate service termination with support.
Under the declared operating model, service logs are kept in the application. Ordinary cloud operational, error and command logs are retained for no more than 24 hours after each record is created. This limit does not apply to account settings, current service state, customer VM content or the minimum necessary records of rights requests and security incidents. Ordinary logs are not archived as substitute long-term history.
Account database backup retention, in days: not yet confirmed by the operator. Previously completed erasures must be reapplied after restoring a backup. Data retained for a specific legal obligation or legal claim is separated from ordinary operation; we explain the reason and retention period or criteria.
5. GitHub and recipients
GitHub connection is voluntary. OAuth requests read:user and repo; repo also covers private repositories within the authorisation granted. The service uses GitHub APIs for repositories, branches, languages and commit history, and for agreed repository operations. Disconnecting in the profile removes the locally held identifier and token. Authorisation can also be revoked in GitHub settings. Before deleting a connected cloud account we request revocation of the app authorisation. If GitHub does not confirm it, deletion is paused and retry or manual resolution is requested.
GitHub also processes data under its own privacy statement. Its processing may involve countries outside the EEA; that statement describes its transfer mechanisms. Transfers we arrange must have an appropriate mechanism under Chapter V GDPR; information and relevant safeguards are available on request.
Within the operator, access is limited to authorised persons who need it. Team and shared VM users receive access according to configured permissions. When loading technical interface libraries, a browser may contact their distribution provider, revealing in particular its IP address. We do not sell personal data. Data may be disclosed to authorities when legally required. This notice does not govern a separate customer CRM.
6. Cookies and security
Authentication uses necessary technical cookies and sessions for login, protection against forged requests and language selection. Session duration follows the service configuration; support can provide current details. This notice does not introduce consent to analytics or advertising cookies. Any future use requires separate assessment and prior consent where required.
Security measures include password hashing, access control and optional two-factor authentication. GitHub tokens are encrypted in the database. Reading customer VM content is not part of ordinary account administration; infrastructure administration follows customer instructions and the processing terms.
7. Rights and contact
Subject to GDPR conditions, you may request access and a copy, correction, erasure, restriction and portability. You may object to processing based on legitimate interests. Where consent applies, it can be withdrawn without affecting prior lawful processing. Erasing essential login data can require account closure. Administrators correct email addresses after verifying the request.
A JSON download of account and related records is available in the profile. It excludes authentication secrets, VM disks and some raw logs; it does not replace responding to a broader access request. Write to info@grapesc.cz. We verify identity proportionately, preferably through the account or a verified contact. We respond without undue delay and normally within one month. An extension of two further months is possible under GDPR conditions, with reasons communicated in the first month.
You may complain to the Czech Office for Personal Data Protection, Pplk. Sochora 27, 170 00 Praha 7, or another competent supervisory authority. Your rights are governed by the GDPR.