Rules may be delayed. Responsibility cannot.
The regulatory calendar has shifted. Contractual, data protection, cybersecurity and management responsibility has not been put on hold.
Eventaisummitbudapest.hu
AI Summit Budapest 2026 · Future Lab · House of Music Hungary · 7 September, 09:20
Two important AI Act dates have been pushed back. Meanwhile models are updated, data moves, dependence on vendors grows, and the company is taking decisions today that it must be able to defend later.
Counsel, Head of the IT, Data & Cyber practice · Taylor Wessing Budapest · The Legal 500: Leading individual 2025 (Taylor Wessing profile, opens in a new tab)

Beside each slide you will find its main claim, the speaker’s outline, a practical explanation and sources you can check. The slides are shown in Hungarian, as presented.
← → browse · space play · swipe on mobile
The regulatory calendar has shifted. Contractual, data protection, cybersecurity and management responsibility has not been put on hold.
Hover over a keyword or tap it: the outline lights up where it was said.
The central question of these twenty minutes is simple. If one of the company’s AI decisions were challenged tomorrow, could we show which system version was running, on what data, with what access rights, who approved it and how it could be overridden?
An authority is not the only one that may ask. Customers, insurers and investors want the same answer, and so does the court in any later dispute.
Two double-sided decision sheets for executives: one for before an AI product is released, one for before a company puts AI into use. Each has its own checklist with status boxes to mark. Those who build and deploy use both. Both sheets are in Hungarian.
Taking an AI product to market: legal role, classification and the responsibility you take on. An eight-point checklist for the release decision, with status boxes to mark.
↓ Download | PDF, 2 pages, in Hungarianv2.0 · 14 October 2026 · General professional information, not legal advice on any individual matter.
Bringing AI into the company: actual use, vendor dependencies and operational control. An eight-point checklist for going live, with status boxes to mark.
↓ Download | PDF, 2 pages, in Hungarianv2.0 · 14 October 2026 · General professional information, not legal advice on any individual matter.
In the first conversation we take one specific AI system, procurement or development. Together we find the three questions that need an answer before the next decision.
For executive decisions: what actually runs, who is responsible for it, and which control does the approval depend on?
For deployment and procurement: do the technical operation, the contract and the decision audit trail fit together?
For developers: is the product ready for the customer questionnaire, change management and market entry?
The packages in detail on the Advisory page
A free orientation conversation at Taylor Wessing’s Budapest office; it does not by itself create a lawyer-client relationship. Details and terms: Advisory
The full recording of the talk (20:44, in Hungarian) was published on AI Summit Budapest’s official channel on Indaplay. One click opens it in a new tab.
▶Watch the recording (Indaplay, opens in a new tab)Indaplay · AI Summit Budapest 2026 · Future Lab · 20:44
The recording opens in a new tab on Indaplay, an external site, on AI Summit Budapest’s official channel; Indaplay’s own privacy and cookie rules apply there. This page does not embed an external player.
If any of them lacks a specific, documented answer, the use case is not yet ready for approval.
Besides the approved systems, count the features built into existing software, individual use and agents that can act on their own.
A model swap, a new data source, a plug-in or a new access right can change the system so that the earlier review no longer covers the same operation.
Technical access rights must not be broader than the business authorisation. It must be clear what the system may do on its own and where a genuine human decision is required.
A provider calling its own operation compliant does not by itself protect the deploying company. Change notification, data boundaries, liability and exit must also appear as enforceable commitments.
After the event, what counts is whether the model, the version, the data used, the control applied and the human decision can be identified. A log of the output is not always enough on its own.
The figures reflect the position on 7 September 2026. Detailed sources are given under the related slides.
I gave this talk in Hungarian, on the Future Lab stage of AI Summit Budapest on 7 September 2026, and the slides on this page are shown as presented, in Hungarian. Their claims, outlines, practical notes and sources are given here in English; the recording and the PDFs remain in Hungarian. The original page is in Hungarian at drkj.hu/aisummit.
The material of the talk is also available as in-house training, with your organisation’s own questions. Request in-house training
Content. This page provides general professional information and is not legal advice on any individual matter. References and deadlines reflect the position on 7 September 2026.
Use of AI. I also used AI-based tools to prepare the talk materials and this page. The texts and images went through human professional review and editing, and I bear editorial and professional responsibility for the content; for the texts, this is the human review and editorial responsibility referred to in the second subparagraph of Article 50(4) of the AI Act.
Reuse. Short quotations may be used with attribution. Republishing the full material, or any self-contained part of it, requires prior consent.
Design and recording. The colours and typography of this page refer to the visual identity of AI Summit Budapest 2026; the event was organised by Economx and IndaEvents, and the recording is published by Indaplay. This is my own professional page, independent of the organiser.