Processes personal data, in Lithuania

Regulation (EU) 2016/679, Art. 9 · Read the law's page

• Ground the processing of any biometric identifier of a person in Lithuania, including a faceprint or voiceprint captured for unique identification, on a GDPR Article 9(2) condition such as explicit consent.
• Conduct a data protection impact assessment before processing special categories of personal data, including biometric data, of persons in Lithuania on a large scale, under GDPR Article 35(3)(b).

Regulation (EU) 2016/679, Arts. 12-21 · Read the law's page

• Honor a person's request to access, rectify, erase, restrict, port, or object to processing of their personal data in Lithuania within one month of receipt.

Regulation (EU) 2016/679, Arts. 33-34 · Read the law's page

• Notify VDAI without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in Lithuania, unless the breach is unlikely to risk their rights and freedoms.
• If you process personal data on behalf of a controller, notify the controller without undue delay after becoming aware of a personal data breach (Article 33(2)).
• Notify affected individuals without undue delay where a breach is likely to result in a high risk to their rights and freedoms.

Regulation (EU) 2016/679, Arts. 44-49 · Read the law's page

• Rely on a European Commission adequacy decision, Standard Contractual Clauses with a transfer impact assessment, Binding Corporate Rules, or a narrow Article 49 derogation before moving personal data of a person in Lithuania outside the European Economic Area.
• Allow for a VDAI authorization step of up to 20 working days, extendable once by up to 10 working days, where a transfer relies on safeguards that GDPR Article 46(3) makes subject to authorization, such as ad hoc contractual clauses or administrative arrangements.

Regulation (EU) 2016/679, Arts. 82-83 · Read the law's page

• Compensate any person who suffered material or non-material damage from your infringement, as controller or processor, under GDPR Article 82.

Republic of Lithuania Law No. XIII-1426, in force 16 July 2018 (as amended) · Read the law's page

• Establish a GDPR Article 6 lawful basis before processing personal data of a person in Lithuania, including data collected by crawling.

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).