1. Parties, incorporation and roles
This Data Processing Agreement (DPA) forms part of the accepted eVPS service agreement between Redcluster LTD, HE387801, Medousis 26 Of. 202, Larnaca, 6059, Cyprus ("Provider"), and the customer identified in the order ("Customer"). It applies where Provider processes personal data on Customer’s behalf under Regulation (EU) 2016/679 (GDPR) and applicable supplementary data-protection law.
Customer acts as controller, or as processor acting for another controller. Provider acts respectively as processor or sub-processor. A Customer acting as processor confirms that it is authorised to appoint Provider and pass on the documented instructions and obligations of the relevant controller. Each party remains responsible for its own statutory duties.
Provider acts separately as controller for account, billing and other processing described in the Privacy Policy. This DPA prevails over inconsistent service terms for its subject matter; mandatory transfer clauses prevail over inconsistent provisions. Electronic acceptance of the service agreement incorporating this DPA binds the parties; a separate signature is not required where valid electronic contracting is used.
2. Annex A: processing particulars
- Subject matter: the unmanaged VPS and associated networking, storage and included backup functions identified in the accepted order. Features not ordered are not added by this DPA.
- Duration: the service term and the limited return, retrieval and deletion phase described below. Obligations continue for as long as Provider or an authorised sub-processor holds Customer Personal Data.
- Nature and purpose: automated hosting, storage, transmission, copying for included backups, retrieval, support access when authorised or necessary under instructions, infrastructure protection and deletion to provide the contracted service.
- Data subjects: Customer’s users, customers, visitors, employees, contractors and other people whose data Customer lawfully places in the service.
- Data types: as determined by Customer, potentially identifiers, contact details, account data, communications, transaction records, device/network data and content. Customer must provide more specific categories and requirements where needed for a risk assessment.
- Sensitive data: Customer must identify special-category data under Article 9 or criminal-offence data under Article 10, establish the necessary legal conditions, and assess the suitability of this unmanaged service before processing it. Appropriate additional safeguards, including encryption under Customer-controlled keys where suitable, must be agreed where necessary.
- Location: production storage in the country recorded in the accepted order/service record. Provider supplies the applicable backup, support-access and sub-processor locations through the processing record described in Annex C. A production-country selection alone does not describe all processing locations.
- Customer rights and obligations: determine lawful purposes, issue documented instructions, select return/deletion, receive assistance and information, exercise the audit rights below, and secure the guest environment.
The order, this Annex and Customer’s documented configuration and support instructions together describe the processing. Customer must not upload data for a use that requires unagreed safeguards or a regulated service that Provider has not accepted.
3. Documented instructions and lawful access
Provider processes Customer Personal Data only on documented instructions, including regarding transfers. Instructions include this agreement, authorised control-panel actions and verified support requests. Access is limited to what is necessary to operate, secure, support, return or delete data under those instructions. Provider does not use Customer Personal Data for advertising, sale or unrelated analytics.
If Union or Member State law binding on Provider requires other processing, Provider informs Customer before that processing unless the law prohibits notice on important public-interest grounds. Provider assesses and limits disclosure requests to their lawful scope, including GDPR Chapter V and Article 48 where relevant; a foreign demand alone is not treated as sufficient authority.
Provider promptly informs Customer if it considers an instruction contrary to applicable data-protection law and may suspend the affected instruction while seeking clarification. Provider is not required to follow an unlawful instruction. Work outside the contracted scope may require a separately agreed scope and fee, without obstructing mandatory assistance.
4. Customer responsibilities
Customer is responsible for its lawful basis, notices, controller authorisations, data minimisation, accuracy, subject-rights decisions and any required impact assessment. Customer must not place unnecessary passwords, identity documents or sensitive data into support tickets.
For the guest operating system and applications, Customer manages patching, authentication, permissions, firewall configuration, encryption/key management, data exports and independent backups. Customer maintains an incident and privacy contact in the account and provides instructions in time for statutory deadlines.
5. Annex B: infrastructure security measures
Provider shall maintain measures appropriate to the processing risks under Article 32, considering the state of the art, implementation costs, scope and impact on individuals. The following are contractual minimum measures for Provider-controlled infrastructure:
- People and permissions: access only for authorised personnel with a work-related need, confidentiality commitments or equivalent statutory duties, and removal or adjustment of access when roles change.
- Administrative access: individual privileged identities where supported, protected authentication and administrative channels, least privilege and review of privileged access. Credentials and access records are protected from unauthorised use.
- Physical and tenant protection: controlled access to hosting facilities, logical isolation of VPS instances and controls intended to prevent one tenant accessing another tenant’s data.
- Host protection: appropriate hardening, security-update and vulnerability-management procedures for systems managed by Provider; event logging, monitoring and incident triage proportionate to risk.
- Transmission and media: appropriate protection of administrative and backup transfers; controlled handling, reuse and disposal of storage media to prevent unauthorised recovery. Customer controls application encryption and its own keys unless a specific managed feature is agreed.
- Availability and recovery: procedures to detect infrastructure failures, protect the included backup process, restore access following incidents and periodically assess recovery arrangements. No additional backup product or contractual RPO/RTO is created, but statutory security duties remain applicable.
- Governance: periodic review of the effectiveness of safeguards, incident procedures, supplier controls and deletion procedures; retention of evidence sufficient to demonstrate compliance.
Provider may update measures while maintaining an appropriate overall level of protection. On request it provides information needed to assess the measures applicable to the service. Data-center ISO certifications, where stated, belong to the facility and are not Provider certifications.
6. Sub-processors and Annex C processing record
Customer gives general written authorisation for the sub-processors identified in the service-specific processing record supplied by Provider before processing starts. That record forms Annex C to this DPA and identifies each legal entity, its function, processing/access countries and any international-transfer mechanism. Provider keeps it current and makes it available to Customer on request.
Provider gives written notice of an intended addition or replacement, identifying the proposed sub-processor, relevant processing and intended start date. The notice specifies a reasonable period to raise a written objection on substantiated data-protection grounds before the change takes effect. Customer must identify the relevant risk and cooperate in assessing a practicable solution. If no objection is received within that period, Provider may proceed under the general authorisation. Provider is not required to maintain a separate supplier arrangement or redesign the service for an individual Customer. If an objection cannot be resolved, either party may terminate the affected service before the disputed sub-processor processes the affected data, with required return/retrieval and a refund of unused prepaid service charges.
Provider imposes equivalent relevant data-protection obligations by a binding written contract, checks sufficient guarantees and remains fully liable to Customer for the sub-processor’s performance of those obligations as required by Article 28(4). An infrastructure supplier is a sub-processor to the extent it actually processes Customer Personal Data on Provider’s behalf; not every carrier or independent billing provider has that role.
7. International transfers and location changes
Provider does not transfer Customer Personal Data, including by remote access, outside the EEA without documented instructions/authorisation and a valid GDPR Chapter V mechanism. Where standard contractual clauses are used, the parties use the applicable module and complete its annexes, assess the transfer and implement required supplementary measures. Any required transfer clauses and annexes must be completed before the transfer.
Provider gives advance information about a proposed material change of processing countries through the sub-processor or service-change process. Where a binding order seeks access, Provider applies the applicable legal safeguards and informs Customer unless legally prohibited. Customer is responsible for the lawfulness of its requested public transmissions and exports; Provider’s statutory transfer duties remain applicable.
8. Personal data breaches
Provider notifies Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data processed under this DPA. Provider has no obligation to monitor the contents of unmanaged guest systems. Notification covers breaches of which Provider becomes aware in its processor role; further information may follow as it becomes available.
The notice describes the nature of the breach, available information about affected data/individuals and approximate numbers, likely consequences, the contact for further information, and mitigation undertaken or proposed. Information may be supplied in stages without undue further delay. Provider investigates within its control, preserves relevant evidence and cooperates with Customer.
Customer determines its notification obligations to supervisory authorities and individuals; Provider assists under Articles 33 and 34 and does not notify on Customer’s behalf unless instructed or legally required. An incident notice is not an admission of liability.
9. Rights requests and regulatory assistance
Taking account of the processing and information available, Provider assists Customer by appropriate technical and organisational measures, insofar as possible, with data-subject requests and duties under Articles 32 to 36, including security, breach notification, impact assessments and prior consultation.
Provider promptly forwards requests concerning Customer Personal Data and does not respond substantively for Customer unless authorised or legally required. Customer normally uses its own administrator access for searching, correcting, exporting or deleting guest data; Provider supplies necessary assistance for information or systems under Provider’s control.
Any reasonable charge for substantial additional assistance must be disclosed and agreed in advance, be lawful and not make mandatory rights ineffective. Provider does not charge Customer to remedy Provider’s own breach and does not delay necessary statutory cooperation while a fee is disputed.
10. Return, deletion and residual copies
At the end of processing, Customer chooses return or deletion of Customer Personal Data, and Provider deletes remaining copies unless Union or Member State law requires retention. Customer can export guest-accessible data during the service and request assistance for other data Provider must return. Provider provides a reasonable opportunity to communicate the choice before irreversible deletion, subject to binding lawful restrictions.
Any applicable Data Act transition and minimum retrieval period in the Terms takes precedence. Otherwise, after the agreed export/retrieval opportunity ends, Provider completes deletion of live copies without undue delay.
Residual backup copies remain protected, isolated from ordinary processing and deleted through a documented rotation/erasure schedule, with a maximum period disclosed in Annex C before processing starts. They may be used only for necessary recovery or a binding retention duty; if restored, deletion instructions are reapplied. Where a legal hold requires retention, Provider limits its scope and duration and deletes when the duty ends.
Provider supplies confirmation of completion on request and propagates required deletion/return to sub-processors. Nothing promises recovery of data already lawfully deleted or restores guest data previously deleted by Customer.
11. Information and audits
Provider makes available information necessary to demonstrate Article 28 compliance and allows and contributes to audits, including inspections, by Customer or an independent auditor mandated by Customer. Documentary evidence and remote review should be used first where they adequately answer the question; these methods do not waive an inspection necessary to verify compliance.
Ordinary audits require reasonable notice, agreed scope, suitable confidentiality protections and arrangements to protect other tenants and infrastructure security. Routine audits should normally be no more frequent than annually, but this is not a cap where a credible incident, material non-compliance or legal/regulatory requirement justifies another audit. An auditor must be independent and competent; confidentiality is not used to prevent lawful reporting to a regulator.
Reasonable scheduling and a lawful, agreed allocation of exceptional audit costs may apply. Provider bears the cost of remedying its own non-compliance. The parties arrange a suitably protected alternative where a proposed audit method would expose other customers, while preserving the audit access required by Article 28.
12. Liability, duration and law
The liability provisions of the Terms apply between the parties to the extent permitted by data-protection law. They do not bind data subjects or supervisory authorities, reduce Provider’s Article 28(4) responsibility, exclude non-excludable Article 82 liability, or automatically shift Provider’s fines to Customer. Each party remains responsible for its own infringement and any statutory contribution/regress right.
This DPA continues until all relevant personal data has been returned or deleted except lawful retained copies, for which protection continues. Material changes follow the notice and lawful variation process in the Terms and cannot retrospectively authorise processing. Cyprus law and the competent forum under the Terms apply without restricting mandatory data-protection rights.
Data-protection instructions and incident contact: [email protected]. Customer’s contact is its verified account contact or a separately notified privacy/security representative.