Records text chat, in the Netherlands

Wetboek van Strafrecht, artt. 139a-139c · Read the law's page

• Do not use a technical device to eavesdrop intentionally on a conversation held in a home, closed premises or yard other than on the instruction of a participant in it, and do not record such a conversation unless you take part in it or record on a participant's instruction (Article 139a(1)).
• Recording with a technical device that is not secretly present and is used on the authority of the person who uses the home, premises or yard is outside Article 139a(1), except in case of manifest abuse, and so is the recording of data processed or transmitted by telecommunication or by an automated work (Article 139a(2)).
• Do not secretly eavesdrop on or record, with a technical device, a conversation held elsewhere than in a home, closed premises or yard, when you act with the intention of eavesdropping or recording, other than on a participant's instruction or without being a participant (Article 139b(1)).
• Do not intentionally and unlawfully tap or record, with a technical device, data that are not intended for you and that are processed or transmitted by telecommunication or by an automated work (Article 139c(1)). Tapping or recording by or on behalf of the person entitled to a connection used for telecommunication is excluded, except in case of manifest abuse (Article 139c(2)).

Implementatiewet richtlijn herziening productaansprakelijkheid, Kamerstuk 36906 · Read the law's page

• The bill excludes free-of-charge and open-source software (gratis en opensourcesoftware) that you develop or supply outside the course of a commercial activity (Art. 6:184a(3)(a)).
• If you develop, manufacture or produce a product, software included, or present yourself as its manufacturer by putting your name or trade mark on it, you answer as its manufacturer for damage a defect in it causes (Arts. 6:184a(1)(b) and (e), 6:187(1)(a)).
• Keep supplying the software updates and upgrades needed to maintain safety while the product is within your control: a defect due to software, a related service or a missing safety update is not excused because it arose after you placed the product on the market (Art. 6:185(2)).
• Meet the product safety requirements that apply to your product, safety-relevant cybersecurity requirements included: they count in deciding whether it is defective (Art. 6:186(1)(f)), and failing a mandatory requirement that protects against the damage suffered presumes it defective (Art. 6:188(2)(b)).
• Account for what your product learns or acquires after release: the effect of any ability to keep learning or to acquire new features is weighed in deciding whether it is defective (Art. 6:186(1)(e)).
• Be ready to give access to the relevant evidence you hold when a court orders it under Articles 194 and 195 of the Code of Civil Procedure; failing to do so presumes the product defective (Art. 6:188(2)(a)).
• If you manufacture outside the Union, the importer, your authorized representative or, where neither is established in the Union, the fulfillment service provider answers for the product alongside you (Art. 6:187(1)(c)).
• If you substantially modify a product outside its manufacturer's control and then place it on the market or put it into service, you are treated as its manufacturer (Art. 6:187(2)).
• If you distribute a product, or provide an online platform that lets consumers conclude distance contracts with traders, name the liable operator established in the Union or your own supplier within one month of the injured person's request, or you answer for the defective product (Art. 6:187(3) and (4)).
• Be able to show when you placed the product on the market or put it into service: you are not liable if you did not, or if it is plausible that the defect did not exist then (Art. 6:185(1)(a) and (c)).