By Nexora Cyprus editorial team · Editorial maintenance only; no named regulated professional review is attributed.
TL;DR
Cyprus companies within scope are subject to the GDPR and Cyprus Law 125(I)/2018. Test DPO and Article 30 record duties, notify a personal-data breach within 72 hours after awareness unless it is unlikely to result in risk, and select a valid Chapter V mechanism for each restricted transfer. Article 83 maximums are not automatic penalties and depend on the infringement and statutory assessment factors.
Legal Framework
GDPR (Regulation EU 2016/679) applies directly in Cyprus as EU law. The Cyprus implementation legislation, Law 125(I)/2018 (the Personal Data Protection Law), supplements GDPR with Cyprus-specific provisions on derogations (employment data processing, health-data processing, scientific research) and the establishment of the Office of the Commissioner for Personal Data Protection.
The Commissioner is Cyprus's supervisory authority for data-protection matters. For any enforcement or priority statement, use the Commissioner's current published decision, annual report or guidance and distinguish GDPR, Cyprus implementing law and the separate ePrivacy rules.
Lawful Bases for Processing
Article 6 GDPR enumerates six lawful bases for processing personal data:
Contract — necessary for performance of a contract with the data subject
Legal obligation — required by Cyprus or EU law
Vital interests — protection of life or limb (rare in commercial context)
Public interest — relevant for public bodies; rarely for private companies
Legitimate interests — balanced against the data subject's rights and freedoms (must be documented in a legitimate interests assessment)
Special-category data under Article 9 GDPR requires an applicable Article 9(2) condition in addition to the Article 6 analysis. Article 9(2)(b) covers processing necessary for specified employment, social-security and social-protection obligations or rights where authorised by Union or Member-State law or a qualifying collective agreement with appropriate safeguards. Cyprus Law 125(I)/2018 section 9 instead contains Cyprus-specific rules for genetic and biometric data; do not cite it as a general employment-data derogation.
When a DPO is Mandatory
Article 37 GDPR mandates appointment of a Data Protection Officer (DPO) where:
Processing is by a public authority or body, subject to the Article 37 exception for courts acting in their judicial capacity
Core activities require regular and systematic monitoring of data subjects on a large scale (e.g. employee monitoring, behavioural advertising, telemetry)
Core activities involve large-scale processing of special category data or criminal-conviction data
'Large scale' is not defined by one GDPR number; relevant factors include the number or proportion of data subjects, data volume and range, duration and geographic extent. A voluntarily designated GDPR DPO is subject to the applicable statutory position, including independence and conflict rules. The controller or processor must publish the DPO's contact details and communicate them to the supervisory authority; the GDPR does not describe this as registration of the DPO.
Article 30 ROPA
Article 30 distinguishes the controller's record under Article 30(1) from the processor's record of categories of processing carried out for each controller under Article 30(2). Each record must contain the fields applicable to that role. The limited Article 30(5) exception for an enterprise or organisation employing fewer than 250 persons is activity-specific and unavailable where the processing is likely to result in risk, is not occasional, or includes Article 9 or Article 10 data. Relevant controller-record fields include:
Name and contact details of the controller / processor and DPO
Purposes of the processing
Categories of data subjects and categories of personal data
Categories of recipients to whom data is disclosed
Transfers to third countries and the safeguards used
Time limits for erasure of different data categories
General description of the technical and organisational security measures
A processor's Article 30(2) record instead identifies the processor and each controller, the categories of processing carried out for each controller, applicable third-country transfers and safeguards, and a general description of Article 32(1) security measures where possible. Having employees or customers is not, by label alone, the Article 30(5) test; map each activity and role. Maintaining a record can still be a proportionate accountability control where an exception might apply.
DPIAs
Article 35 requires a DPIA before processing likely to result in a high risk to individuals' rights and freedoms. The Cyprus Commissioner's published list is an indicative supervisory-authority list of processing operations subject to DPIA; it supplements the Regulation and EDPB criteria, is not an exhaustive universal 'blacklist', and the absence of an activity from the list is not a whitelist or safe harbour.
Examples that require a fact-specific Article 35 and published-list assessment include:
Systematic monitoring, including workplace CCTV or productivity tools, considering scale, context, vulnerability and combination of criteria
Large-scale processing of Article 9 special-category data or Article 10 criminal-conviction data
Systematic and extensive evaluation or profiling producing legal or similarly significant effects
Biometric identification or other biometric processing where the scale, purpose, context and applicable list criteria indicate high risk
Processing involving children or other vulnerable people where the nature, scale, context and purpose create likely high risk
Innovative technology, including an AI system, only after assessing the actual use, data, decisions, scale and combination of high-risk criteria
A third-country transfer as part of the overall risk assessment; Chapter V transfer compliance and a DPIA are separate duties, so neither SCCs nor a non-adequate destination automatically decides Article 35
Breach Notification — The 72-Hour Clock
Article 33 GDPR requires notification of personal-data breaches to the supervisory authority (Cyprus Commissioner) within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to data subjects. Where notification is later than 72 hours, the reasons for the delay must be provided.
Article 34 requires notification to data subjects without undue delay where the breach is likely to result in a high risk. Exemptions: encryption rendering the data unintelligible; subsequent measures eliminating the risk; or where direct notification would involve disproportionate effort (in which case public communication suffices).
Practical clock
The 72-hour clock starts when the controller has a reasonable degree of certainty that a security incident has led to personal data being compromised. A short investigation may be needed to establish that point, but the controller must investigate promptly and cannot postpone awareness until every fact or consequence is confirmed. Processors notify controllers without undue delay under Article 33(2).
International Data Transfers
Personal data transfers from Cyprus / EU to third countries (non-EEA) require a transfer mechanism under Chapter V GDPR:
A European Commission adequacy decision that is current and covers the destination, recipient and transfer
Standard Contractual Clauses (SCCs 2021 — Commission Decision 2021/914)
Binding Corporate Rules (BCRs) — for intra-group flows
Derogations (Article 49) — narrow, case-specific use
For an Article 46 mechanism such as SCCs, assess the law and practice affecting the particular transfer and whether supplementary measures are needed. Before relying on the EU-US Data Privacy Framework, verify the Commission decision then in force and the recipient's active certification and covered data. Recheck the legal and certification status at the transfer date rather than predicting litigation outcomes.
Cyprus Commissioner Enforcement
The Commissioner can use the corrective powers in Article 58 and, where the legal conditions are met, administrative fines assessed under Articles 83 and 84 and Cyprus law. The two GDPR maximum tiers depend on the breached provision and use the higher applicable fixed amount or worldwide annual-turnover percentage; an actual measure must be effective, proportionate and dissuasive and reflect the Article 83 factors.
Operational review areas—not assertions about a fixed enforcement priority—include:
Cookies and similar technologies: classify what is strictly necessary and apply the current ePrivacy and GDPR rules to consent and subsequent processing
Workplace processing: establish necessity, proportionality, transparency, lawful basis and any special-category or DPIA conditions for CCTV, email or performance monitoring
Direct marketing: apply both GDPR and the applicable ePrivacy rule, including the communication channel, recipient, existing-customer conditions, objection and suppression records; consent is not the only possible GDPR basis and is not universally optional
Cross-border transfers: verify any current adequacy decision—including the United Kingdom where covered—or use an appropriate Article 46 safeguard and case-specific transfer assessment; SCCs are not required for every UK transfer
Data-subject requests: respond without undue delay and in principle within one month; Article 12(3) permits an extension by up to two further months where necessary for complexity or number, with notice and reasons within the first month
90-Day Compliance Roadmap
1Days 1–10: Data mapping. Identify every system / vendor / process that touches personal data. Categorise data subjects (customers, employees, prospects). Build the first ROPA.
2Days 10–25: Lawful basis register. For each processing operation in the ROPA, identify and document the lawful basis. Where it is consent — verify the consent mechanism. Where it is legitimate interests — write the LIA.
3Days 25–40: Privacy notices. Update the website privacy notice, the employee privacy notice, and the candidate privacy notice. Ensure all required Article 13/14 disclosures are made.
4Days 40–55: Security measures. Document technical and organisational measures (encryption, access controls, retention schedules, vendor management). Map against ISO 27001 if relevant.
5Days 55–70: International transfers. List each third-country flow and select the current mechanism that actually covers it—adequacy, an Article 46 safeguard such as SCCs or BCRs, or only where its strict conditions are met an Article 49 derogation. Perform the mechanism-specific assessment and supplementary-measures work where required.
6Days 70–80: DPIA shortlist. Run DPIAs on high-risk processing. Document the analysis.
7Days 80–90: Operationalise. Train the team. Set up the breach response playbook. Subject Access Request response template. DPO appointment if mandatory.
1. Cyprus's national framework
Cyprus Personal Data (Processing) Law 125(I)/2018 transposed national supplements to EU GDPR. Key Cyprus-specific provisions:
Cyprus-specific provisions, restrictions or derogations must be tied to the exact section, processing purpose and GDPR opening clause; a sector label alone does not create a general exception.
Cyprus Data Protection Commissioner (DPC) enforcement powers + procedure.
Cyprus offenses and personal liability — identify the exact statutory offense, prohibited act or omission, required intent or knowledge, responsible person and available penalty; a GDPR infringement does not automatically establish a crime.
Sectoral codes of conduct + certification frameworks.
Cross-border-transfer rules, safeguards and any authority process applicable to the destination, recipient and transfer mechanism.
Processing is by a public authority or body, subject to the Article 37 exception for courts acting in their judicial capacity.
Core activities consist of regular and systematic monitoring of data subjects on a large scale.
Core activities consist of large-scale processing of Article 9 special-category data or Article 10 personal data relating to criminal convictions and offences.
Check whether sector law or a binding measure creates an additional appointment duty; a regulated-sector label alone does not decide Article 37.
Assess 'core activities', 'regular and systematic monitoring' and 'large scale' from the actual processing and current EDPB and Commissioner guidance.
3. Key operational obligations
Lawful basis identification for each processing activity.
Privacy notices + policies in plain language.
Data subject rights handling (access, rectification, erasure, portability, objection).
Records of processing activities where Article 30 requires them, including the limited Article 30(5) exception analysis for an organisation with fewer than 250 persons.
Data Protection Impact Assessment (DPIA) for high-risk processing.
Personal-data breach — notify the competent authority without undue delay and, where feasible, within 72 hours after awareness unless the breach is unlikely to result in a risk to natural persons; communicate to affected data subjects without undue delay where the breach is likely to result in a high risk, subject to Article 34's exceptions.
Cross-border transfers — identify an applicable adequacy decision, Article 46 safeguard or, only where its conditions are met, an Article 49 derogation; record any required transfer-risk and supplementary-measures analysis.
4. Cyprus DPC enforcement
The Commissioner may investigate and exercise the corrective powers available under GDPR and Cyprus law. The measure and any publication depend on the breached provision, gravity, evidence, procedure and final decision.
Article 83(5) and (6) categories can carry a maximum of €20 million or, for an undertaking, up to 4% of total worldwide annual turnover for the preceding financial year, whichever is higher.
Article 83(4) categories can carry a maximum of €10 million or, for an undertaking, up to 2% of total worldwide annual turnover for the preceding financial year, whichever is higher.
Warnings, reprimands, orders, restrictions, bans and fines are distinct Article 58 powers; they are not a mandatory escalation sequence.
Any personal inquiry or liability depends on the legal duty, person's role, conduct, evidence and applicable Cyprus procedure; office alone does not establish liability.
Publication and anonymisation depend on the Commissioner's legal power, decision and applicable confidentiality and data-protection rules.
5. Sector-specific Cyprus considerations
Financial services — apply GDPR and the Commissioner's powers separately from the entity's CySEC or Central Bank duties; regulatory supervision does not merge the legal bases or enforcement powers.
Healthcare and GeSY-related processing — classify controller and processor roles, Article 9 condition, professional-secrecy, access, security, record and sector-law duties for the actual processing.
Marketing — apply GDPR alongside the Cyprus electronic-communications rules to the channel, recipient, consent or other lawful basis and opt-out evidence.
Crypto and fintech — map MiCA, DAC8, AML, transfer-of-funds and sanctions data separately; a regulatory reporting duty supplies only the legal basis and data scope that the applicable rule supports.
Employment and HR — use the actual employment purpose, lawful basis, transparency, monitoring, access, retention and Commissioner guidance rather than a generic employee-consent model.
6. Compliance practical checklist
1Record of processing activities (RoPA) where Article 30 requires it, after documenting any claimed Article 30(5) exception.
2Privacy notices on website + customer onboarding.
3Data subject rights handling procedure.
4Vendor + processor due diligence + Data Processing Agreements (DPAs).
5Cross-border transfer mechanisms documented (SCCs, BCRs, adequacy).
6DPIA for high-risk processing.
7Breach response plan that starts from awareness, documents every breach and applies the Article 33 authority-notification threshold and timing rather than notifying mechanically.
8Role- and risk-appropriate data-protection and security training, refreshed when the processing, incidents or applicable rules require it.
9DPO appointment where Article 37 or another binding rule requires it, with contact details published and communicated to the competent supervisory authority under Article 37(7).
10Personal-data-breach record maintained under Article 33(5), whether or not a notification is required.
Disclaimer: This article is for informational purposes only and does not constitute legal, tax, or financial advice. Tax laws change frequently. Consult a qualified Cyprus adviser for guidance specific to your situation. The information on this page is general guidance only and does not constitute legal, tax, accounting, immigration or financial advice. Specific advice should be obtained based on the facts of each case.
Read each reference alongside the claim it accompanies and check current amendments before relying on it. Editorial maintenance only; no named regulated professional review is attributed..