Deploys a chatbot, in Cyprus

Law 112(I)/2004, art. 99(1)-(4) · Read the law's page

• If you provide a publicly available electronic communications network or service, take all due technical and organizational measures to secure the confidentiality of any communication carried over it and of the related traffic data, and make sure your employees do the same (Article 99, paragraph 1).
• Do not listen to, tap, store, interfere with or otherwise monitor communications or the related traffic data unless you are one of the users communicating with each other, the users concerned have consented, or paragraph 3 allows it. A recording of conversations and traffic data that the law permits in the course of lawful business practice, to provide evidence of a commercial transaction or other business communication, is left outside that prohibition (Article 99, paragraphs 2 to 4).

Regulation (EU) 2024/1689, Arts. 5, 50 — directly applicable in Cyprus as EU Member State

• Do not place on the market, put into service, or use an AI system for social scoring.
• Do not use real-time remote biometric identification in publicly accessible spaces for law enforcement purposes, except within narrow exceptions the law allows.when it serves a public body
• Do not place on the market, put into service, or use an AI system that exploits individuals' vulnerabilities.
• Tell users, before or at the start of an interaction, that they are communicating with an AI system.
• Mark generated image, video, audio and text output in machine-readable form that identifies it as artificially generated.

Ο περί της Ευθύνης λόγω Ελαττωματικών Προϊόντων Νόμος του 2026 (Liability for Defective Products Bill) · Read the law's page

• This bill is not law: the consultation draft was posted on 25 February 2026, and it would apply to products made available on the market after 9 December 2026 (draft Articles 3(1) and 18(1)).
• If you develop, make or produce software, have it designed or made, or put your name or trade mark on it, you answer as its manufacturer; free and open-source software developed or supplied outside a commercial activity is outside the draft (draft Articles 2 and 3(2)(a)).
• Keep supplying the software updates and upgrades needed to keep the product safe while it is within your control; a defect from software, an update or upgrade, a missing safety update, a related service or a substantial modification is not excused on the ground that the defect arose after you placed the product on the market (draft Article 10(2)).
• Judge safety against all the circumstances, including cybersecurity requirements, any ability of the product to keep learning or acquire new features after it is placed on the market, and any recall (draft Article 6(2)).
• Keep documents you could produce: when a claimant shows facts and evidence supporting a plausible claim, the court can require you to disclose the documents in your possession or control, and failing to produce the relevant evidence presumes the product defective (draft Articles 8(1) and 9(2)(a)).
• Meet the mandatory safety requirements, national or EU, that protect against the harm suffered: a claimant who shows that a product does not meet them gets a presumption of defect (draft Article 9(2)(b)).
• If you are the importer, the authorized representative or the fulfilment service provider of a manufacturer established outside the EU, you answer in the manufacturer's place; a distributor, or an online platform that lets consumers conclude distance contracts with traders, answers too if it does not name an operator or its own supplier within one month of the request (draft Article 7(1)(c), (3) and (4)).
• If you substantially modify a product outside the manufacturer's control and then make it available on the market or put it into service, you answer as its manufacturer (draft Article 7(2)).
• Do not rely on a contract term or national law to be released from liability to the injured person (draft Article 14).
• Be ready to prove an excuse: that you did not place the product on the market or put it into service, that the defect probably did not exist then or appeared afterwards, that it results from complying with legal requirements, that the objective state of scientific and technical knowledge did not allow it to be discovered, or the component and modification excuses (draft Article 10(1)).
• If you integrate a software component made by someone else into a product, you cannot sue the component's manufacturer where it was a micro or small enterprise when it placed the component on the market or you agreed by contract to waive that right (draft Article 11(2)).
• Keep the claim periods in view: three years from the day the injured person learned or could reasonably have learned of the damage, the defect and the liable operator; ten years from the day the defective product was placed on the market or put into service; 25 years where latent personal injury prevented a claim (draft Articles 15 and 16).