Trains models, in Hungary

2001. évi CVIII. törvény az elektronikus kereskedelmi szolgáltatások, valamint az információs társadalommal összefüggő szolgáltatások egyes kérdéseiről (Ekertv.), 13/A. § · Read the law's page

• Process a service recipient's personal data only for the contract and billing purposes in Section 13/A paragraphs 1 and 2 or because the data are technically indispensable to providing the service (Electronic Commerce Act Section 13/A, paragraph 3).
• Use data about the use of the service for any other purpose, such as targeted advertising or market research, only after defining the purpose in advance and obtaining the recipient's consent (Section 13/A, paragraph 4).
• Let the recipient prohibit that other processing before and during use of the service, and do not link the data to the recipient's identifying data or pass them to a third party without the recipient's consent (Section 13/A, paragraphs 5 and 6).
• Delete data processed for the contract, billing and technical purposes after the contract ends or is not concluded and after billing, and delete data processed for the other purpose once that purpose ends or the recipient so decides (Section 13/A, paragraph 7).
• Do not make a service that is not available from another provider conditional on consent to processing for other purposes (Section 13/A, paragraph 8).
• Let the recipient learn, before and during use of the service, which kinds of data you process for which purposes (Section 13/A, paragraph 9).

1999. évi LXXVI. törvény (Szjt.), 35/A. §, as inserted by 2021. évi XXXVII. törvény 10. § · Read the law's page

• Reproduce a work for text-and-data mining, including AI training, only where you have lawful access to it and the rightsholder has not objected in advance in an appropriate, machine-readable manner for online content, per Szjt. Section 35/A(1).
• Keep any copies made for text-and-data mining only for as long as the mining itself requires.

2025. évi LXXV. törvény az Európai Unió mesterséges intelligenciáról szóló rendeletének magyarországi végrehajtásáról · Read the law's page

• Stop unlawful conduct or restore a lawful state when Hungary's AI market surveillance authority, the minister responsible for business development under Government Decree 344/2025 (X. 31.), so orders under Section 7(1) of Act LXXV of 2025; the same authority may also impose an administrative fine or declare your AI system's use unlawful.
• Where you test an AI system under real-world conditions in Hungary, supply data to the AI market surveillance authority when it requires it and allow its remote or on-site inspections without prior notice, under Section 7(2).

344/2025. (X. 31.) Korm. rendelet az Európai Unió mesterséges intelligenciáról szóló rendeletének magyarországi végrehajtásáról szóló 2025. évi LXXV. törvény végrehajtásáról · Read the law's page

• If you are a conformity assessment body designated for high-risk AI systems in Hungary, send the AI notifying authority, by 31 January each year, a report on the conformity assessment activity you carried out in the previous year (Section 2(5)).

1997. évi XLVII. törvény az egészségügyi és a hozzájuk kapcsolódó személyes adatok kezeléséről és védelméről, 35/A. § (4)-(8) bekezdés · Read the law's page

• Work with EESZT data for AI development only inside the secure processing environment and only with the operator's permit (Section 35/A(4) and (5)).
• Use only anonymous data, and hold the scientific research permit issued by the competent ethics committee of the Health Science Council (Egészségügyi Tudományos Tanács) (Section 35/A(7)(a) and (c)).
• Use what you learn during AI development only for that development, and give adequate safeguards against use outside the permit and for the protection of individuals (Section 35/A(7)(b) and (d)).
• Carry out a data protection impact assessment before AI development starts (Section 35/A(7)(e)).
• Agree with the operator the conditions for using the data and for making the results available (Section 35/A(8)).

2025. évi XCII. törvény a magánjogi tárgyú törvények módosításáról · Read the law's page

• These rules are enacted but do not apply yet: they apply to products placed on the market or put into service after 9 December 2026, and sections 6:550 to 6:559 of the Civil Code now in force keep governing earlier products (Sec. 95(6) of Act XCII of 2025; Sec. 55/A of Act CLXXVII of 2013).
• If you develop, make or have made a product, software included, or present yourself as its manufacturer by your name, trade mark or other distinguishing sign, you answer for damage a defect in it causes (Secs. 6:550(1)(a), 6:552 and 6:554(2)(a)).
• Keep supplying the software updates and upgrades needed to keep the product safe while it is within your control: a defect that arises after you put the product into circulation because of software, an update or upgrade, or a missing update needed to maintain safety is not excused (Sec. 6:557(5)).
• Treat safety-relevant cybersecurity requirements and any recall as part of what decides whether your product is defective (Sec. 6:555(2)(f) and (g)).
• 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 (Sec. 6:555(2)(c)).
• Keep evidence you could produce if a court orders you to make it available: failing to do so presumes the product defective (Sec. 6:556(1)(a)).
• If you are outside the EU, the importer, your authorized representative or, failing them, the fulfilment service provider answers for the product in your place (Sec. 6:550(1)(c)).
• If you distribute a product or run an online platform that lets consumers contract with traders, identify the liable business established in the EU, or your own supplier, within one month of the injured person's request, or you answer for the damage (Sec. 6:550(5) and (6)).
• If you substantially modify a product outside the manufacturer's control and then distribute it or put it into service, you answer as its manufacturer (Sec. 6:550(4)).
• If you build a software component into a product, you have no recourse against a micro or small enterprise that made the software where you waived recourse in the contract (Sec. 6:551).
• Do not rely on a contract term to limit or exclude liability to the injured person, because it is void (Sec. 6:559).
• Free and open-source software developed or made available in the course of a non-commercial activity is outside the chapter (Sec. 6:559/B(2)(b)).