Records calls, in Lithuania

73 straipsnio 1-3 dalys, Lietuvos Respublikos elektroninių ryšių įstatymas Nr. IX-2135 · Read the law's page

• Do not listen to, record, store or otherwise intercept the content of messages or traffic data carried over public electronic communications services, or become acquainted with them, without the consent of the actual users of the services, except where the law lawfully allows it under Articles 77, 78 and 96 of the Electronic Communications Law.
• Do not disclose the content of messages carried over electronic communications networks, or the related traffic data, and do not make it possible to learn them, without the users' consent, except in cases set by law.
• Before you record information and related traffic data in lawful business practice to provide evidence of a commercial or other business transaction that may have legal consequences, inform the users of the recording and its purpose, and keep the recorded content and traffic data no longer than the period during which the transaction can be legally challenged.
• If you provide electronic communications networks or services, take appropriate organizational and technical measures to ensure the confidentiality of communications, and give the State Data Protection Inspectorate the conditions to carry out its control.

Lietuvos Respublikos civilinio kodekso šeštosios knygos III dalies XXII skyriaus ketvirtojo skirsnio ir priedo pakeitimo įstatymas Nr. XV-1080 · Read the law's page

• These rules are enacted but do not apply yet: they apply from 9 December 2026, and the Civil Code rules in force until 8 December 2026 keep governing products placed on the market or put into use before then (Art. 3 of Act No. XV-1080).
• If you develop or make a product, software included, or present yourself as its manufacturer by putting your name, trade mark or another distinguishing sign on it, you answer as its manufacturer for damage a defect in it causes (Arts. 6.292(1) and 6.293(1) point 1 and (2)).
• Keep supplying the software updates and upgrades needed to keep the product safe while it is within your control: you keep control if you integrate or supply a component or can supply updates or upgrades yourself or through a third party, and a defect caused by software, by an update or upgrade, or by a missing update needed for safety is not excused because it arose after you placed the product on the market (Arts. 6.292(3) and 6.298(1) point 1).
• Treat safety-relevant cybersecurity requirements and any recall or other corrective action as part of what decides whether your product is defective (Art. 6.294(1) points 6 and 7).
• Allow for what the product learns or acquires after it is placed on the market, because the effect of that ability is weighed in deciding whether it is defective (Art. 6.294(1) point 3).
• Keep evidence you could produce if a court orders you to disclose it: failing to disclose relevant evidence the claimant requested presumes the product defective (Art. 6.297(1) point 1).
• Meet the product-safety requirements that apply to your product: failing a requirement that protects against the risk of the harm suffered presumes it defective (Art. 6.297(1) point 2).
• If you are outside the EU, your importer or authorized representative established in the EU answers for the product in your place, and where there is neither, the fulfilment service provider answers (Art. 6.292(4)).
• If you distribute a product, or run an online platform that lets consumers conclude distance contracts with traders where the conditions of Article 6(3) of Regulation (EU) 2022/2065 are met, name the manufacturer, importer, authorized representative, fulfilment service provider or your own supplier within a month of the injured person's request, or you answer for the damage (Art. 6.292(5)).
• If you substantially modify a product outside the manufacturer's control and then place it on the market or put it into use, you answer as its manufacturer (Art. 6.292(2)).
• If you build a software component into a product, you have no recourse against the maker of a defective software component that was a micro or small enterprise when it placed the component on the market, where you waived recourse in your contract with it (Art. 6.296(2)).
• Free and open-source software developed or supplied outside commercial activity is outside these rules (Art. 6.299(2)).
• A claim must be brought within three years of the day the injured person learned, or should have learned, of the damage, the defect and who the liable operator is, and the right to sue is extinguished ten years after the product was placed on the market or put into use, or 25 years where a court finds that a later-revealed injury prevented suit within ten (Art. 6.300).