Publication
Publication
Contacts
Georgiades & Pelides LLC
Galatia Sazeidou
Tel: +(357) 22 88 9000
www.cypruslaw.com.cy
Supervisory Authority
Commissioner for the Protection of Personal Data
National Legislation
Law no. 125(I)/2018 (unofficial translation)
(Please note these links are provided for information only. Any translations may not be accurate and the text may not include amendments to that legislation).
Contributed by Georgiades & Pelides LLC
Last updated June 2026
General | Data Protection Laws
National Legislation
National Supervisory Authority
Scope of Application
Personal Data
Sensitive Personal Data
Data Protection Officers
Accountability and Privacy Impact Assessments
Rights of Data Subjects
Security
Transfer of Personal Data to Third Countries
Enforcement
ePrivacy | Marketing and cookies
National Legislation
Cookies
Marketing by E-mail
Marketing by Telephone
General data protection laws
The General Data Protection Regulation (EU) (2016/679) (“GDPR”).
The EU is currently considering the Digital Omnibus (2025/0360 (COD)). This proposes a number of amendments to the GDPR including: (a) protection from abusive subject access requests; (b) extending the deadline to notify breaches to a supervisory authority to 96 hours and only applying that notification to high risk breaches; (c) codifying the “relative” approach to the concept of personal data; (d) ensuring a consistent approach to DPIAs; and (e) providing an express legal basis for the training of AI systems. However, some changes are controversial, and it is not clear if they will all be adopted.
The law supplementing the GDPR in Cyprus, law no. 125(I)/2018 as amended (the “Data Protection Law”).
Entry into force
The GDPR has applied since 25 May 2018.
The Data Protection Law applies from 31 July 2018.
Details of the competent national supervisory authority
The Commissioner for the Protection of Personal Data is the supervisory authority in Cyprus for GDPR purposes and represents Cyprus on the European Data Protection Board.
Commissioner for the Protection of Personal Data (the “Commissioner”)
15 Kypranoros Street
1061 Nicosia, Cyprus
Notification or registration scheme and timing
There is no obligation to notify regulators of any processing under the GDPR. However, controllers and processors must keep a record of their processing and make it available to their supervisory authority on request (subject to limited exemptions).
Under the Data Protection Law, notification to the Commissioner is required prior to the transfer of sensitive personal data to a third country.
Exemptions to notification
Notification is not required where the transfer is to a whitelisted country.
What is the territorial scope of application?
The GDPR applies to the processing of personal data in the context of the establishment of a controller or processor in the EU.
It also contains express extra-territorial provisions and applies to controllers or processors based outside the EU that: (i) offer goods or services to individuals in the EU; or (ii) monitor individuals within the EU. Controllers and processors caught by these provisions will need to appoint a representative in the EU, subject to certain limited exemptions.
The European Data Protection Board has issued Guidelines on the territorial scope of the GDPR (3/2018).
Is there a concept of a controller and processor?
Yes. The GDPR contains the concept of a controller, who determines the purpose and means of processing, and a processor, who just processes personal data on behalf of the controller.
The European Data Protection Board has issued Guidelines on the concepts of controller and processor in the GDPR (7/2020).
Both controllers and processors are subject to the rules in the GDPR, but the obligations placed on processors are more limited.
Are both manual and electronic records subject to data protection legislation?
Yes. The GDPR applies to both electronic records and structured hard copy records.
Are there any national derogations?
The GDPR does not apply to law enforcement activities which are instead subject to the Law Enforcement Directive. The GDPR also does not apply to areas of law that are outside the scope of Union law, such as national security, and does not apply to purely personal or household activity.
In Cyprus, processing for journalistic or academic purposes or for the purposes of artistic or literary expression is lawful, subject to such processing being proportional in relation to the intended purposes and respecting the data subjects’ fundamental rights and freedoms. The rights of data subjects to be provided with information on and access their personal data under articles 14 and 15 of the GDPR apply to the extent they do not prejudice the right to freedom of expression and the confidentiality of journalistic sources.
Processing for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes precludes the use of personal data for the purpose of decision making which produces legal effects concerning the data subjects or which similarly significantly affects them.
What is personal data?
Personal data is information relating to an identified or identifiable natural person.
This is a broad term and includes a wide range of information. The GDPR expressly states it includes online identifiers such as cookies. This concept has been considered by the CJEU on multiple occasions. This includes deciding that information will not be personal data where the risk of identification appears in reality to be insignificant (OC v Commission, C 479/22 P) and that a “relative” approach should be taken to identification by considering the means reasonably available to the person holding the information (EDPS v SRB, C-413/23 P).
Is information about legal entities personal data?
No. However, information about sole traders and partnerships is likely to be personal data.
What are the rules for processing personal data?
All processing of personal data must comply with all six general data quality principles. Personal data must be: (i) processed fairly, lawfully and transparently; (ii) collected for specific, explicit and legitimate purposes and not processed in a manner incompatible with those purposes; (iii) adequate, relevant and not excessive; (iv) accurate and, where necessary, up to date; (v) kept in an identifiable form for no longer than necessary; and (vi) kept secure.
The processing of personal data must also satisfy at least one condition for processing personal data. These conditions are that the processing is: (a) carried out with the data subject’s consent; (b) necessary for the performance of a contract with the data subject; (c) necessary for compliance with a legal obligation; (d) necessary in order to protect the vital interests of the data subject; (e) necessary for the public interest or in the exercise of official authority; or (f) necessary for the controller’s or a third party’s legitimate interests, except where overridden by the interests or fundamental rights and freedoms of the data subject.
The European Data Protection Board has issued Guidelines on the performance of a contract processing condition for online services (2/2019) and Guidelines on processing of personal data based on Article 6(1)(f)(1/2024).
In Cyprus, the combination of large scale filing systems of two or more public authorities or bodies is permitted only for reasons of public interest and is subject to a number of restrictions (which may include a data protection impact assessment and prior consultation with the Commissioner).
Are there any formalities to obtain consent to process personal data?
The requirements for consent under the GDPR are strict.
To be valid, consent must be in clear and plain language and, where sought in writing, separate from other matters. Consent must be based on affirmative action so pre-ticked boxes are not acceptable. Consent might not be valid if: (i) there is any detriment to the data subject for refusing; (ii) there is an imbalance of power; (iii) consent for multiple purposes is bundled together; or (iv) the consent is a condition of entering into a contract. Finally, consent can be withdrawn at any time.
In practice, other processing conditions should be relied on where possible. Consent will only be an appropriate processing condition if the individual has a genuine choice over the matter, for example, whether to be sent marketing materials.
The European Data Protection Board has issued Guidelines on consent (5/2020).
Data Protection Officers
When must a data protection officer be appointed?
Both controllers and processors must appoint a data protection officer if: (i) they are a public authority; (ii) their core activities consist of regular and systematic monitoring of data subjects on a large scale; or (iii) their core activities consist of processing special category personal data on a large scale (including processing information about criminal offences).
Data protection officers must also be appointed where required by national law. The Data Protection Law provides that the Commissioner may create a list of processing activities and circumstances in which the appointment of a data protection officer is mandatory, in addition to those provided for under the GDPR. The data protection officer is subject to a duty of confidentiality.
What are the duties of the data protection officer?
The data protection officer must be involved in all data protection issues and cannot be dismissed or penalised for performing their role. The data protection officer must report directly to the highest level of management. Details of the data protection officer must be communicated to the relevant supervisory authority.
The Article 29 Working Party has issued Guidelines on Data Protection Officers (WP243).
Is there a general accountability obligation?
The GDPR adds a general accountability obligation under which you must not only comply with these rules, but also be able to demonstrate you comply with them. This means ensuring suitable policies are in place supported by audit and training.
Are privacy impact assessments mandatory?
A data protection impact assessment must be conducted where “high risk” processing is carried out. This includes: (a) systematic and extensive profiling that produces legal effects or significantly affects individuals; (b) processing on a large scale either special categories of personal data or personal data relating to criminal convictions and offences; and (c) systematic monitoring of a publicly accessible area on a large scale (e.g. CCTV). Where the assessment indicates the risk cannot be mitigated, the controller must consult the relevant supervisory authority.
The Article 29 Working Party has subsequently issued Guidelines on Data Protection Impact Assessments (WP 248). It suggests there are nine criteria to consider to determine whether to conduct a data protection impact assessment, and that an assessment should be made if two or more of those criteria are met. This is arguably wider than the criteria set out in the paragraph above.
In Cyprus, the Data Protection Law requires a privacy impact assessment to be conducted in a number of circumstances, including (i) before the transfer of sensitive personal data to a third country pursuant to an individual derogation under Article 49 of the GDPR; (ii) before the imposition of any restrictions on data subject rights or in order to obtain an exemption from the obligation to notify data subjects of a data breach, in the circumstances set out in the Data Protection Law; or (iii) before the combination of large scale filing systems of two or more public authorities or bodies where sensitive personal data or data on criminal convictions or offences are involved or where the identity card number or other identifier of general application will be used.
Privacy notices
A controller must provide data subjects with a privacy notice setting out how the individual’s personal data will be processed. The privacy notice must contain the enhanced transparency information.
The Article 29 Working Party has issued Guidelines on Transparency (WP260).
Rights to access information
Data subjects have a right to access copies of their personal data by making a request to the controller. They are entitled to both a copy of the personal data and information about the context in which it is processed. The initial request is free, though a charge can be made for subsequent requests. Controllers can refuse the request if it is manifestly unfounded or excessive. The right to obtain a copy of personal data should not adversely affect the rights and freedoms of others. The response must be provided within a month, though this can be extended by two months if the request is complex.
The European Data Protection Board has issued Guidelines on rights of access (1/2022). There have been several important CJEU decisions on the right of access. They indicate data subjects have a right to a faithful and intelligible reproduction of their personal data, including underlying documents where essential to exercise their rights effectively (FF, C-487/21) and that a request is only likely to be considered excessive if made with abusive intent (Rottler, C-526/24). In Österreichische Post (C‑154/21), the CJEU decided that details of specific recipients of the personal data must be disclosed unless this is impossible or manifestly unfounded or excessive.
Rights to data portability
Data subjects also have a right to data portability where the condition for processing personal data is consent or the performance of a contract. It entitles individuals to obtain any personal data they have “provided” to the controller in a machine-readable format. Individuals can also ask for the data to be transferred directly from one controller to another. There is no right to charge fees for this service.
The Article 29 Working Party has issued Guidelines on data portability (WP242).
Data controllers may impose restrictions on the right to data portability on public policy grounds in accordance with the conditions of Article 23 of the GDPR. This is subject to a data protection impact assessment and prior consultation with the Commissioner, as well as notification of the relevant data subjects.
Right to be forgotten
A data subject can ask that their data be deleted in certain circumstances. However, those circumstances are relatively limited, for example where the processing is based on consent, that consent is withdrawn and there are no other grounds for processing. Even where the right does arise, there are a range of exemptions, for example where there is a legal obligation to retain the data.
The European Data Protection Board has issued Guidelines on the criteria of the Right to be Forgotten (5/2019).
Data controllers may impose restrictions on the right to notification of erasure on public policy grounds in accordance with the conditions of Article 23 of the GDPR. This is subject to a data protection impact assessment and prior consultation with the Commissioner, as well as notification of the relevant data subjects.
Objection to direct marketing
A data subject can object to their personal data being processed for direct marketing purposes at any time. This includes profiling to the extent related to direct marketing.
Other rights
The GDPR contains a range of other rights, including a right to have inaccurate data corrected. There is also a right to object to processing being carried out in the performance of a public task or under the legitimate interests condition.
Finally, there are controls on taking decisions based solely on automated decision making that produce legal effects or similarly significantly affects the data subject. The Article 29 Working Party has issued Guidelines on Automated Decision Making and Profiling (WP251).
There is also a right to restriction of processing, for example pending verification of the accuracy of the relevant data. Data controllers may impose restrictions on this right on public policy grounds in accordance with the conditions of Article 23 of the GDPR. This is subject to a data protection impact assessment and prior consultation with the Commissioner, as well as notification of the relevant data subjects.
Security requirements in order to protect personal data
The GDPR contains a general obligation to implement appropriate technical and organisational measures to protect personal data.
In addition, controllers and processors must ensure, where appropriate: (i) the pseudonymisation and encryption of personal data; (ii) the ability to ensure the ongoing confidentiality, integrity, availability and resilience of its information technology systems; (iii) the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident; and (iv) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.
Specific rules governing processing by third party agents (processors)
A controller must ensure that any processor it instructs will ensure adequate security for personal data and otherwise meet the requirements of the GDPR.
The controller must have written contracts with its processor containing the enhanced processor clauses.
Notice of breach laws
A personal data breach must be notified to the relevant supervisory authority unless it is unlikely to result in a risk to data subjects. The notification must, where feasible, be made within 72 hours. If the personal data breach is a high risk for data subjects, those data subjects must also be notified.
Notice of breach laws apply to specific industry sectors under other regimes. For example, under EU DORA and under the national laws implementing the Privacy and Electronic Communications Directive and to NIS II.
The European Data Protection Board has issued Guidelines on Personal Data Breach Notification (9/2022) and Examples regarding Personal Data Breach Notification (1/2021).
Under the Data Protection Law, data controllers may be exempt from the obligation to notify the data subjects on public policy grounds in accordance with the conditions of Article 23 of the GDPR (subject to a data protection impact assessment and prior consultation with the Commissioner).
Restrictions on transfers to third countries
The GDPR contains a restriction on transborder dataflows. This restriction does not apply if the transfer is to a whitelisted country (which includes US organisations participating in the EU-U.S. Data Privacy Framework).
Transfers can be made: (i) pursuant to a set of Standard Contractual Clauses; (ii) pursuant to binding corporate rules; (iii) to an importer who has signed up to an approved code or obtained an approved certification; or (iv) where otherwise approved by the relevant supervisory authority. However, following the decision in Schrems II (C-311/18) any transfer made on this basis must be subject to a transfer impact assessment of the laws of the relevant third country and supplemented by supplementary protections where necessary.
The European Data Protection Board has issued Recommendation on European Essential Guarantees for surveillance measures (2/2020) and a Recommendation on measures that supplement transfer tools (1/2020) to help conduct this transfer impact assessment. The European Commission has also issued an FAQ on the new Standard Contractual Clauses.
Transfers are also possible if an individual derogation applies. These derogations allow a transfer if it: (i) is made with the data subject’s explicit consent; (ii) is necessary for the performance of a contract with, or in the interests of, the data subject; (iii) is necessary or legally required on important public interest grounds, or for legal claims; (iv) is necessary to protect the vital interests of the data subject; (v) is made from a public register; or (vi) is made under the so-called minor transfer exemption.
The European Data Protection Board has issued Guidelines on derogations applicable to international transfers (2/2018). Finally, the European Data Protection Board has issued Guidelines on the interplay between Article 3 and international transfers (2/2018) to help identify when a transfer takes place.
In Cyprus, a data protection impact assessment is required in order to be able to rely on an individual derogation for the transfer of sensitive personal data to a third country.
Notification and approval of national regulator (including notification of use of Standard Contractual Clauses)
In general, there is no need for prior approval from a supervisory authority. However, this depends on the justification for the transfer.
For example, there is no obligation to get approval for the use of Standard Contractual Clauses (though it is possible some supervisory authorities may want to be notified of their use). In contrast, it is necessary to get approval to rely on binding corporate rules, and the supervisory authority must be informed of transfers made using the minor transfers exemption.
In Cyprus, transfers of sensitive personal data to a third country other than a whitelisted country must be notified to the Commissioner prior to the relevant transfer. In case of reliance on an individual derogation, a data protection impact assessment and prior consultation with the Commissioner are required. In any of these cases, the Commissioner may impose restrictions for important reasons of public interest.
Use of binding corporate rules
The GDPR places binding corporate rules on a statutory footing. It is possible to obtain authorisation from one supervisory authority (subject to approval through the consistency mechanism) that covers transfers from anywhere in the EU.
Cyprus is already part of the mutual recognition procedure for binding corporate rules.
Fines
The GDPR is intended to make data protection a boardroom issue. It introduces an antitrust-type sanction regime with fines of up to 4% of annual worldwide turnover or €20m, whichever is the greater. These fines apply to breaches of many of the provisions of the GDPR, including failure to comply with the six general data quality principles or carrying out processing without satisfying a condition for processing personal data.
A limited number of breaches fall into a lower tier and so are subject to fines of up to 2% of annual worldwide turnover or €10m, whichever is the greater. Failing to notify a personal data breach or failing to put an adequate contract in place with a processor fall into this lower tier.
There are a number of CJEU judgments on administrative fines. For example, the CJEU has stated that fines can only be imposed where there is an intentional or negligent infringement of the GDPR, see Deutsche Wohnen (C-807/21).
The EDPB has published Guidelines on the calculation of administrative fines (04/2022).
Imprisonment
Breach of various provisions of the Data Protection Law and the GDPR is a criminal offence which is punishable, upon conviction, by imprisonment for up to 5 years and/or by a fine of up to €50,000.
Compensation
Data subjects have a right to compensation in respect of material and non-material damage. This requires more than a mere infringement of the GDPR and there must be actual material or non-material damage. The CJEU confirms there is no minimum threshold of seriousness and even non-material harm such as distress may qualify.
Other powers
Regulators have a range of other powers including investigative and corrective powers such as audits, warnings, reprimands and processing bans.
Practice
ePrivacy laws
Cypriot ePrivacy laws are contained in Part 14 of the Law on the Regulation of Electronic Communications and Postal Services (the “ePrivacy Law”), implementing the Privacy and Electronic Communications Directive.
Conditions for use of cookies
Cookies require user consent under the ePrivacy Law unless strictly necessary.
Regulatory guidance on the use of cookies
Article 29 Working Party guidance (WP194 and WP208) applies.
Conditions for direct marketing by e-mail to individual subscribers
Prior consent is required.
Conditions for direct marketing by e-mail to corporate subscribers
Consent must be declared for legal entities.
Exemptions and other issues
The similar products and services exemption applies with strict rules on identification and opt-out.
Conditions for direct marketing by telephone to individual subscribers
Governed by GDPR principles.
Conditions for direct marketing by telephone to corporate subscribers
Requires prior consent.
Exemptions and other issues
No exemptions apply.
Contents