Agefi Luxembourg - novembre 2026

Novembre 2026 45 AGEFI Luxembourg IA & Tech L e Luxembourg House of Fi­ nancial Technology (LHoFT) franchit une nou­ velle étape dans son développe­ ment international avec le premier investissement de son fonds NextFin Asia dans Finfra, une entreprise indonésienne spé­ cialisée dans les infrastructures de financement numérique. Cette opérationmarque une première concrétisation du partenariat entre le LHoFT, la Banque asia­ tique de développement et les au­ torités luxembourgeoises pour soutenir les jeunes entreprises fintech favorisant lʹinclusion fi­ nancière en Asie du SudEst. Finfrabénéficiede ce financement dans le cadredʹuneextensiondesontourdetable de série A, auquel participent ADB Ventures, la branche dʹinvestissement de la Banque asiatique de développement, ainsi que ses investisseurs historiques CentoVentures etAccionVentures. Lesnouveauxcapitauxpermettrontàlʹen­ treprise de renforcer sa plateforme tech­ nologique et dʹaccélérer son expansion vers de nouveauxmarchés. Fondée en 2022, Finfra développe une solution technologique permettant aux établissements financiers et aux entre­ prises deproposer des crédits sans devoir construire leurs propres infrastructures opérationnelles. Sa plateforme centralise notamment lʹoctroi desprêts, lʹévaluation des risques et le suivi des rembourse­ ments. Elle permet également aux entre­ prises dʹintégrer directement des offres de financement dans leurs services numériques. Lʹobjectifestnotammentdefaciliterlʹaccès au crédit pour les petites entreprises et les particuliers qui restent insuffisamment couverts par les circuits financiers tradi­ tionnels. En simplifiant les opérations de financement, la plateforme entend égale­ ment permettre aux établissements prê­ teurs dʹélargir leur clientèle et de réduire les contraintes liées audéveloppement de nouvelles offres de crédit. Lancé en février 2026, NextFin Asia est un fonds destiné aux entreprises ayant participé au programme dʹaccélération Catapult: Inclusion SE Asia du LHoFT. Finfra avait intégré ce programme en 2024. Le dispositif associe accompagne­ ment entrepreneurial et accès au finan­ cement afin de soutenir le développe­ ment de solutions financières inno­ vantes enAsie du SudEst. Audelà du financement, les entreprises sélectionnées peuvent bénéficier demises en relation avec des institutions finan­ cières,desexpertsetdespartenairesrégio­ naux. Cet accompagnement doit faciliter leur développement commercial et leur implantationsurdifférentsmarchés,dans une région où lʹaccès aux services finan­ ciers demeure un enjeu important pour les petites entreprises. PourAlexPanican, directeur général par intérim du LHoFT, ce premier investis­ sement concrétise lʹambition de rappro­ cher une institution de financement du développement et un accélérateur spé­ cialisé dans les technologies financières. Annabelle Fonteneau, responsable des programmes dʹaccélération au LHoFT, souligne également que le parcours de Finfra illustre la complémentarité entre accompagnement entrepreneurial et accès au capital. Avec cette opération, le Luxembourg confirme sa volonté de renforcer les liens entre son écosystème fintech et les mar­ chés internationaux, en mobilisant son expertise financière au service de projets technologiques à impact. Le LHoFT pré­ pare par ailleurs la prochaine promotion de Catapult: Inclusion SE Asia, dont les candidatures sont ouvertes aux jeunes entreprises développant des solutions en faveur de lʹinclusion financière. Cetteinitiativecontribueégalementàdon­ ner une dimension internationale à lʹéco­ système financier luxembourgeois. En facilitant les échanges entre investisseurs, institutions de développement et jeunes entreprises technologiques, le Grand­ Duché renforce son positionnement comme plateforme de coopération et de financement pour des projets fintech au­ delà dumarché européen. Source : LHoFT Le Luxembourg investit dans la fintech indonésienne Finfra ©LHoFT By Aline BLEICHER, Sigrid HEIRBRANT &VincentWELLENS, NautaDutilhAvocats Luxembourg S.à r.l. O n 21October 2026, the Council of the European Union adopted its negotia­ ting position on the European Commission’s proposal for the so­ calledDigital OmnibusVII. The Council supports the objective of simplifying the Europeandigital rulebook, but rejects several of the Commission’smore sweeping changes. The proposed regulatory consolidationhas important conse­ quences for businesses operating underDORA, theDataAct, the GDPR, and the EU’s cybersecurity framework. The file is far from final, it will now, once again, have to go through trilogue negotiations with the EuropeanParliament in Q1 2027.We highlight a couple of principal changes. Aselective approach to repealing legislation The Commission wanted a clean sweep amongst the key digital regulations, but the Council prefers a more surgical approach. Only the Free Flow of Non­ Personal Data Regulation would be repealedinfull.Itscoreprinciples,includ­ ing the free movement of nonpersonal datawithin the EUand the prohibition of data localisation requirements, would be absorbed into the Data Act. The Data GovernanceAct would also cease to exist as a standalone instrument, but its sub­ stance would not disappear. Chapters III toVII (about data intermediaries, compe­ tent authorities anddata transfers)would be integrated into the Data Act, while Chapters I and II (reuse of data) would move into theOpenDataDirective. The PlatformtoBusiness Regulation would be only partially repealed. Provi­ sions considered to overlapwith theDig­ ital Services Act and the Digital Markets Act would be removed, but other impor­ tant rules would remain, including those on terms and conditions, restrictions and suspensions,ranking,differentiatedtreat­ mentandinternalcomplainthandlingsys­ tems. Online platforms should therefore not assume that the PlatformtoBusiness regime is about todisappear. DataAct: stronger protection for trade secrets and clearer supervision TheCommission alloweddata holders to refuse “the disclosure of trade secrets” on a “high likelihood” of serious economic damage.TheCouncilloweredthatthresh­ oldtoamere“likelihood”,whilerequiring any refusal to be clear and proportionate. Thischangewouldstrengthentheposition of data holders, particularly where mandatory datasharing obligations con­ cern commercially sensitive technical in­ formation,knowhoworoperationaldata. TheCouncil alsoprovides auseful clarifi­ cationregardingenforcement.GDPRand EUDPRsupervisoryauthoritieswouldsu­ pervise compliance with the DataAct in­ sofar as personal data are concerned. This is intended to avoid parallel enforcement by different authorities for the same per­ sonal data processing activities. GDPR: targeted changeswith potentially significant effects On the topic of pseudonymised data, the Commission had initially proposed to codify the CJEU case law in the SRB case in the definition of “personal data” (Art. 4(1)a). The Council preferred to clarify in a new Article 25a that “[p] seudonymised data shall not be considered personal data for third party if that third party is unable to iden­ tify the natural person to whom the data relates ”anddeferstotheEDPB’sguidance. This provisions also clarifies that “[w] here a processor processes personal data on behalf of a controller, that data shall be considered per­ sonal data for the processor ”. The approach is intended to reflect the relative nature of identifiability while preserving the con­ trollerprocessor framework and solves one of the most pressing outstanding questions inEUdata protection law. For further processing that is compatible with the initial processing on the basis of Article6(4),themainstreampositionisthat no separate legal basis under Article 6(1) is required. The Council appears to con­ tradictthispositionbyclarifyingthatafur­ ther legal basis for lawful processing underArticle 6(1) is nonetheless required and, for the processing of special cate­ gories of personal data, that a legal basis underArticle 9 is also required. Onthetopicofsolelyautomateddecisions, the Council seeks to clarify that such pro­ cessingmay still be “necessary” for enter­ ing into or performing a contract even whenahumancouldtheoreticallytakethe same decision. Where several equally effective automated solutions are avail­ able, however, the controller shouldselect theleastintrusiveoption.Inaddition,auto­ mated decisions should not be based on special categories of personal data unless the data subject has given explicit consent or the processing is necessary for reasons of substantial public interest. AI development and operationunder theGDPR TheCouncil’spositionexpresslyrecognis­ es that legitimate interests under Article 6(1)(f)GDPRmayprovidealegalbasisfor training and operating AI systems and models. This would not create a blanket authorisation.Relianceonlegitimateinter­ ests would remain subject to a caseby­ case balancing assessment, transparency requirements and the data subject’s right to object underArticle 21. Public authori­ tiesperforming tasks in thepublic interest couldrelyonArticle6(1)(e),whereitscon­ ditions aremet. AproposednewArticle9(2)(k)wouldcre­ ate a narrower derogation for specialcat­ egorydata. Itwouldcover only incidental and residual processing necessary for the development and technical operation of anAIsystem,notitsdeployment.Itwould also require deletion aligned withArticle 17 and a documented accountability assessment. This distinction is important: theCouncilappearswillingtofacilitatethe technical development of AI, but not to establishabroad legal basis forusing sen­ sitive data inoperationalAI applications. Breachnotification, privacy bydesign and abusive requests Thedeadlinefornotifyingapersonaldata breachtothesupervisoryauthoritywould move from 72 to 96 hours. More signifi­ cantly,notificationwouldberequiredonly where a breach is likely to result in a high risk to individuals’ rights and freedoms, aligning the authoritynotification thresh­ old with the existing threshold for com­ municating a breach to affecteddata sub­ jects. This would materially reduce the number of notifications,while theorgani­ sation’s initial risk assessment, reasoning anddocumentation remain as important. TheCouncilwouldextenddataprotection by design and by default obligations underArticle25toprocessors,whilemain­ taining the controller’s sole responsibility for determining the purposes andmeans of processing. The text also clarifies the testformanifestlyunfoundedorexcessive datasubject requests. Recitals identify examples such as repeated requests, requests principally seeking compensa­ tion andmalicious requests generated by AIagentsagainstpublicauthorities.Anew limitation to the Article 13 information duty is alsoproposed for simple, lowrisk relationships. These changes respond to genuine operational concerns. Crossborder tax reporting One quieter but substantial change for crossbordertaxandFATCA/CRSreport­ ing concerns the confirmation that trans­ fers based on the publicinterest deroga­ tions inArticle 49(1)(d) and (f) to (g) need not be nonrepetitive. International exchanges between tax administrations (which include FATCAand CRS report­ ing) areexpresslymentionedas example. The proposal appears designed to avoid some of the questions that are pending before the EU Court of Justice in the AAAB case . Cookies remainwithin the ePrivacyDirective The Commission had proposed moving the rules onaccess toandstorageof infor­ mationonterminalequipment,common­ ly referred to as the cookie rules, from Article 5(3) of the ePrivacy Directive into the GDPR. The Council rejects that approach. The regime would remain in the ePrivacyDirective, with an expanded list of consentfree carve outs. The pro­ posed exemptions include anonymous aggregated audience measurement for a provider’s own use, certain mediaaudi­ encemeasurement underArticle24of the European Media Freedom Act, strictly necessary technical security, contextual advertisingmeasurement without profil­ ing (!), besides the current network trans­ missionandservicefunctionalitygrounds. The Council would also introduce a sin­ gleclick refusal button and a fourmonth coolingoff period before consent may be requested again. The competent GDPR supervisory authority would oversee Article 5(3). Acommon entrypoint for incident reporting TheCouncilsupportsfurthercoordination of incident reporting under NIS2, the GDPR, DORA, eIDAS and the CER Di­ rective.EachMemberStatewouldoperate its own “national entry point” to support and facilitate reporting of such incidents. ENISAwould coordinate harmonisation of thresholds and templates, crossborder routingbetweennationalentrypointsand the development of an opensource re­ porting solution. For organisations facing overlapping notification duties, particu­ larlyfinancialinstitutions,cloudproviders, trustservice providers and operators of critical infrastructure, a coordinated entry pointcouldreduceproceduralcomplexity. It will not necessarily eliminate the sub­ stantive differences between the regimes, including their respective deadlines, ma­ teriality thresholds and addressees. Inter­ nal incidentresponse procedures will thereforestillneedtomapeachapplicable legal obligation. What happens next? The Council’s position is an important step, but not the end of the legislative process. The European Parliament must finalise its position, after which the insti­ tutions will seek a common text in tri­ logue. Several politically and legally sen­ sitiveissuesmaystillchange.Thepractical valueofthosechangeswilldependonthe finalcompromisewiththeEuropeanPar­ liament and, ultimately, onwhether con­ solidation on paper produces simpler compliance in practice. The existing rules remain meanwhile in force. Nevertheless, organisations can already identify where the proposal may affectfuturecompliancearchitecture,con­ tracts, incidentresponse procedures, AI governance anddatasharing strategies. Digital Omnibus VII: What may change for data, privacy and cybersecurity compliance

RkJQdWJsaXNoZXIy Nzk5MDI=