Data, Identity & Compliance UX Knowledge Base

Guides on identity data, GDPR product decisions, document capture, data minimization, audit trails and user experience in compliance SaaS.

Biometric AI: no standards means a mandatory notified body

Article 43(1) of the EU AI Act (Regulation (EU) 2024/1689) gives providers of biometric AI systems — Annex III point 1 — a choice between the lighter Annex VI internal-control route and the notified-body route under Annex VII, but only where harmonised standards or common specifications have actually been applied. None have been cited in the Official Journal yet. The choice the Act promises doesn’t exist in practice right now, and the fallback it leaves you with — a notified body — is itself in short supply.

The mechanism, in three steps

This is the whole article, so it’s worth stating plainly before anything else. The choice between Annex VI and Annex VII is conditional on applied harmonised standards or common specifications. That condition is currently unmet. Therefore Annex VII — third-party assessment by a notified body — is mandatory, not optional, for biometric AI providers today.

Why there are no standards, and where they actually stand

The Commission’s original deadline for CEN-CENELEC to deliver harmonised standards was 30 April 2025. It was missed, and the Commission formally pushed it to 31 August 2025 — which also came and went without publication. By late 2025, CEN-CENELEC’s own Joint Technical Committee 21 had moved into what multiple accounts describe as crisis mode: an “exceptionality” measure that would let a small drafting group finalise the most delayed drafts and skip the normal Formal Vote stage where a public Enquiry produced a positive result. Senior figures within JTC 21 pushed back on the measure even as its chair defended it as necessary to avoid signalling weakness at a politically sensitive moment.

As things actually stand: prEN 18228, covering the risk management system required by Article 9, is still in Public Enquiry, with that stage due to close at the end of July 2026 — essentially now. prEN 18286, the quality management system standard supporting Article 17, has moved further: its Enquiry closed in early 2026 and it’s currently out for Formal Vote by national standards bodies, apparently without the Formal-Vote skip that was floated for other drafts. prEN 18284, covering the data and dataset governance requirements of Article 10, is progressing alongside them. None of the three has been cited in the Official Journal, which is the only event that actually triggers a presumption of conformity — a draft standard, however advanced, confers nothing on its own.

One more standard is worth naming precisely, because a common but imprecise claim conflates it with the others: a dedicated standard for the conformity assessment process itself is still described by JTC 21’s own work programme as “in active drafting,” meaningfully behind risk management, quality management and data governance in maturity. And even once finished, a procedural standard governing how an assessment is conducted wouldn’t itself carry a presumption of conformity the way the substantive standards do — presumption of conformity attaches to meeting the essential requirements in Articles 9, 10, 15 and 17, not to the assessment methodology used to check them.

The Article 41 fallback, and why it doesn’t rescue you

The Act does have a backstop for exactly this gap: common specifications adopted by Commission implementing act under Article 41, usable where harmonised standards don’t exist or don’t fully cover the requirements. But it’s built as an exceptional, temporary measure that sunsets once the equivalent harmonised standard arrives, not a parallel permanent track. A provider that doesn’t comply with an applicable common specification has to justify why, and Member States retain the right to challenge a common specification they think doesn’t adequately meet the underlying requirements. It fills a gap; it doesn’t make the underlying uncertainty disappear.

Can you even get a notified body?

Member States had until 2 August 2025 to designate both a market surveillance authority and a notifying authority — the office responsible for authorising and overseeing notified bodies in the first place. As of the most recent tracking, nine Member States have designated both; twelve have partial arrangements or pending proposals; six have designated neither. The models vary widely — Cyprus centralised the role in a single Commissioner acting as notifying authority, market surveillance authority and single point of contact together, while Finland spread it across existing sectoral regulators including its Energy Authority, Transport and Communications Agency, and Medicines Agency.

Designating the authority is not the same as having an operational notified body. Even where a notifying authority exists and is functioning, it still has to run a specific conformity assessment body through the full designation process before that body can actually assess AI systems — a separate, further step. When you check a candidate notified body, check three things specifically: its identification number and notifying Member State in the NANDO database, the precise scope of activities it’s been notified for, and — critically — whether that scope actually covers AI Act conformity assessment, rather than only the other Union product legislation the same organisation may be notified under.

What the queue costs

The designation mechanics themselves take real time. A notified conformity assessment body can only start operating once the Commission and other Member States have raised no objection — within two weeks of notification if it’s based on an accreditation certificate, or two months if based on other documentary evidence instead. Once operating, a notified body needs appropriate liability insurance for its assessment activities, unless national law already covers that liability or the Member State itself takes direct responsibility. And if it subcontracts specific tasks, it needs the provider’s consent first, keeps full responsibility regardless, and has to retain the subcontractor qualification records for five years after the subcontracting arrangement ends. None of this is unique to AI — it’s the same structural pattern that has made notified-body capacity a persistent bottleneck under the Medical Devices Regulation for years, and there’s no reason to expect AI Act capacity to scale faster.

What to do with the extra time

Annex III obligations now apply from 2 December 2027 rather than 2 August 2026, under the Digital Omnibus reform. It’s worth being precise about what that extra time actually is. Reporting on the Commission’s original proposal describes it as deferring the high-risk obligations until measures to support compliance — harmonised standards, common specifications, Commission guidelines — were actually available, which would have tied the deadline to real-world readiness. The final agreement between the co-legislators didn’t keep that conditional structure; it settled on fixed calendar dates instead. That matters: if the standards and notified-body capacity gaps described above are still open in December 2027, the obligations apply anyway, calendar first.

What the time is genuinely useful for: inventory and classification work that doesn’t depend on any of this being resolved, and — if you’re a biometric provider — starting a conversation with a notified body now rather than waiting, given how constrained current capacity already is. What it isn’t for is assuming the standards gap will have quietly closed itself by the time the date arrives.

Frequently asked questions

Can we use a notified body established outside the EU?

No. A notified body has to be constituted under the law of a Member State and hold legal personality there — an organisation established outside the EU or EEA can’t itself hold that status, whatever other credentials it carries elsewhere.

Can we use a body that’s already an MDR notified body?

Only if that same body has separately gone through designation for AI Act conformity assessment specifically. Being notified under the Medical Devices Regulation doesn’t automatically extend to AI Act scope — check the NANDO entry for that specific activity listing rather than assuming an existing sectoral relationship carries over.

How long is an Annex VII certificate valid?

Up to four years for Annex III systems, renewable for further periods of the same length following reassessment. Annex I product systems get a slightly longer five-year ceiling instead.

What happens if a standard is finally published while our assessment is already under way?

The Act doesn’t spell out a specific transition mechanic for this exact situation, and treating it as settled would overstate what’s actually written down. In practice, this is a question to put directly to your notified body, since it’s the one applying whatever technical baseline is current at each stage of the assessment.

Does the Digital Omnibus fix the notified-body supply problem?

No — it buys time for the supply problem to resolve on its own, on a fixed calendar rather than one conditioned on the standards and capacity gaps actually closing. That’s a meaningfully different thing from fixing it, and it means providers still carry the risk that December 2027 arrives with the same shortage this article describes.

Posted by admin in Data, Identity & Compliance UX Knowledge Base

AI Act deepfake labelling: artistic and editorial carve-outs

Article 50(4) of the EU AI Act (Regulation (EU) 2024/1689) requires deployers to disclose when image, audio or video content is a deepfake, and when text has been artificially generated or manipulated for publication on matters of public interest. Two carve-outs sit inside that duty — a lighter disclosure for content that is “evidently” artistic, creative, satirical or fictional, and no disclosure at all for text that passed through genuine editorial control. Both sound generous on a first read. Neither is as wide as it looks, and the European Commission’s draft guidelines, published 8 May 2026, spend more time narrowing them than most summaries let on.

Which content counts as a deepfake under Article 50(4)?

The duty sits with the deployer, not the provider — whoever publishes or puts the content in front of people, not whoever generated it. It applies to AI-generated or manipulated image, audio or video content that constitutes a deepfake under Article 3(60): content resembling existing persons, objects, places, entities or events that would falsely appear to a person to be authentic or truthful.

The Commission’s draft guidelines read that definition wider than most people assume. Three clarifications matter:

  • Intent is irrelevant. Whether the content falsely appears authentic doesn’t depend on whether the deployer meant to deceive anyone. An absence of fraudulent intent doesn’t defeat the labelling duty.
  • “Existing” is read broadly. A realistic synthetic depiction of a fictitious but natural-looking person can still be a deepfake, even where no identifiable real person is implicated — it’s enough that the subject resembles someone or something that could exist, or could once have existed.
  • Not every edit counts. Routine adjustments — lighting, colour correction, noise reduction, sound cleanup — normally don’t turn content into a deepfake, because they don’t meaningfully affect how truthful it appears. More substantial changes that alter meaning or context, such as edits to a photograph used in journalism, can. The guidelines treat this as a case-by-case judgment rather than a bright line.

The artistic, creative, satirical and fictional carve-out

Where a deepfake forms part of a work or programme that is artistic, creative, satirical, fictional or similar in nature, Article 50(4) is satisfied by a lighter disclosure: making known that the content exists in generated or manipulated form, in a way that doesn’t hamper the display or enjoyment of the work — a credit rather than an overlay stamped across the frame.

The word doing the real work in that sentence is one most summaries drop. The original text requires the work to be evidently artistic, creative, satirical or fictional — not arguably, not defensibly, but obviously so. That’s not loose paraphrasing: it’s the actual qualifier in the operative text, and the Commission’s draft guidelines lean on it directly, treating it as a threshold the content has to clear plainly rather than a label a deployer can assert after the fact.

That threshold has teeth, and the clearest illustration is political satire — the case that looks safest on paper. A deepfake of a real politician, shared on social media to mock a decision they made, looks like a textbook fit for the satirical carve-out. Commentary on the draft guidelines gives exactly this example and reaches the opposite conclusion: the exception doesn’t apply, because the same content also touches public discourse on a matter of public interest. Satire and public-interest commentary aren’t mutually exclusive categories under Article 50(4) — they can describe the same clip, and where they do, the more consequential reading controls, not the more convenient one.

The Code of Practice on Transparency of AI-Generated Content addresses this carve-out too, in the section covering deployer labelling of deepfakes and public-interest text. It’s a voluntary compliance tool, not a substitute for reading the exception correctly — signing it demonstrates a method, it doesn’t relax the “evidently” test underneath.

The text carve-out and its two cumulative conditions

Article 50(4)’s second limb catches AI-generated or manipulated text published to inform the public on matters of public interest. It doesn’t catch text that isn’t public-interest text in the first place — an AI-drafted product description or an internal memo was never in scope, carve-out or not.

For the text that is in scope, disclosure drops away entirely, but only where two conditions are both met: the content has undergone a process of human review or editorial control, and a natural or legal person holds editorial responsibility for publishing it. Both, not either. A generative system that drafts news summaries with nobody reviewing them, and nobody named as accountable for what goes out, gets neither condition and has to label every piece.

“Editorial control” is doing more work here than a quick skim suggests. The guidelines and the underlying text point toward an actual review process tied to an identifiable person or role who could be held to account for the publication — not a general policy that content is “monitored,” and not a single glance before hitting publish. A newsroom with a named editor who reviews AI-assisted copy before it runs has a real claim to both conditions. A platform that auto-publishes AI summaries with a disclaimer buried in the terms of service has neither.

Why “obvious” means something narrower here than in Article 50(1)

Article 50(1)’s chatbot-disclosure exception and Article 50(4)’s deepfake exception both turn on how a reasonable person would perceive the content — but they’re not the same reasonable person, and the draft guidelines are explicit about the gap.

Article 50(1) asks whether it would be obvious to a reasonably well-informed, observant and circumspect member of the system’s target audience that they’re dealing with AI. Article 50(4)’s deepfake assessment asks something broader: it has to account for the actual, potentially more varied audience the content is likely to reach, including foreseeable exposure to children, older people, or audiences with less digital or AI literacy than the primary audience the deployer had in mind. A deployer who tests disclosure against their core audience’s media literacy and stops there has answered the wrong question if the content is likely to circulate further than that audience — which most social content is.

The EU icon and the taxonomy nobody has finished building

The Code of Practice’s Section 2 covers Article 50(4) and 50(5) labelling specifically, distinct from the Section 1 marking obligations under Article 50(2). Alongside it, the Commission has floated a standardised visual label for AI-generated content — an “AI” mark, localised as “KI” in German or “IA” in French — together with a taxonomy that would distinguish “fully AI-generated” content from “AI-assisted” content and attach different disclosure requirements to each. Neither the icon nor the taxonomy is settled law; both are proposals moving alongside the Code rather than requirements written into Article 50 itself. Whether to sign the Code at all is a separate decision with its own trade-offs, worth working through on its own terms.

What’s left over

The law enforcement exception applies here as it does throughout Article 50: use authorised by law to detect, prevent, investigate or prosecute criminal offences falls outside the disclosure duty. Open-source licensing doesn’t help elsewhere — Article 2(12) exempts free and open-source AI systems from large parts of the Act, but the exemption specifically carves out Article 50, so a deepfake or text-generation system released under an open licence is fully subject to the labelling duties described here. And none of this shifted in the Digital Omnibus reshuffle: Article 50(4) applies from 2 August 2026 regardless of what happened to the high-risk timeline.

Frequently asked questions

Does a satirical deepfake of a real politician escape labelling?

Not reliably. If the content also bears on public discourse about that person’s decisions or conduct, it’s simultaneously public-interest content, and the guidelines’ worked example treats that overlap as defeating the satire carve-out rather than being resolved in the deployer’s favour. Political content aimed at a real, identifiable person is the case to assume you can’t rely on the exception, not the case to assume you can.

Does someone glancing at AI output before publishing count as editorial control?

That’s a thin claim to either condition. The stronger reading requires an actual review process and a person who holds editorial responsibility for the publication — not evidence that a human technically looked at the text. If you can’t name who is accountable for what goes out, you likely don’t meet the second condition regardless of the first.

Does an AI-written product description count as a matter of public interest?

No. The text limb of Article 50(4) only reaches content published to inform the public on matters of public interest — news, safety information, and similar categories. Commercial copy was never in scope, so the editorial-control carve-out is irrelevant to it; there was never a disclosure duty to carve out of.

Do you need both a visible label and machine-readable metadata?

Generally yes, and they’re not substitutes. Article 50(2) machine-readable marking is a provider duty attached to the output itself; Article 50(4) labelling is a deployer duty attached to how the content is published or presented to people. A provider marking its model’s output doesn’t relieve the deployer of disclosing a deepfake to its actual audience.

Who has the labelling duty — the agency that made the content or the client that published it?

Article 50(4) attaches to the deployer — whoever puts the content in front of the public — not necessarily whoever operated the generative tool. An agency producing a deepfake on a client’s behalf isn’t automatically who Article 50(4) is speaking to if the client is the one publishing it; that allocation is worth fixing in the contract rather than assuming.

Posted by admin in Data, Identity & Compliance UX Knowledge Base

When you don’t have to label your chatbot as AI

AI Act chatbot disclosure: when you don’t need a label

Article 50(1) of the EU AI Act (Regulation (EU) 2024/1689) requires providers to design AI systems that interact directly with people so those people are told they are dealing with an AI — “unless this is obvious from the point of view of a natural person who is reasonably well-informed, observant and circumspect, taking into account the circumstances and the context of use.”

That phrase is not new drafting. It is the average consumer benchmark from EU consumer law, almost word for word, and it has been litigated at the Court of Justice since 1998. Which means the question “do we need a disclosure banner?” has an answer with thirty years of case law behind it — and it is not the answer the compliance-banner vendors are selling.

What Article 50(1) actually requires

Providers — not deployers — must ensure that AI systems intended to interact directly with natural persons are “designed and developed in such a way that the natural persons concerned are informed that they are interacting with an AI system.” It is a design obligation, discharged at build time, and it sits with whoever puts the system on the market under their own name.

In practice the deployer inherits it. If you buy a chatbot and drop it on your checkout page, the provider owes the design duty, but you are the one whose customers see the result — and the exception turns on your circumstances and context of use, which the provider never saw. That gap is the reason contract terms on this matter more than most people assume.

The exposure is not theoretical: Article 99(4)(g) places breaches of Article 50 in the tier of up to €15,000,000, or 3% of total worldwide annual turnover for the preceding financial year if the offender is an undertaking, whichever is higher. Article 50 applies from 2 August 2026 and the Digital Omnibus did not defer it.

Systems in scope

White & Case’s EU AI Act Handbook reads the category as covering chatbots, voice assistants and robo-services — anything intended to interact directly with individuals. It explicitly does not include AI systems designed to interact exclusively with other AI systems or other non-human systems.

That exclusion is narrower than it sounds. An agent that calls your supplier’s API all day is out. An agent that calls your supplier’s switchboard and talks to a person is in, because the person on the other end is a natural person interacting directly with an AI system. The test is who is on the other end, not what your architecture diagram says.

The three exceptions, in order of usefulness

Article 50(1) can be switched off three ways. Only one of them is a live question for most businesses.

  • The “obvious” exception. No disclosure where it would be obvious to a reasonably well-informed, observant and circumspect person, taking into account the circumstances and the context of use. This is the one you will actually argue about.
  • Law enforcement. The obligation does not apply to AI systems authorised by law to detect, prevent, investigate or prosecute criminal offences, subject to appropriate safeguards for the rights and freedoms of third parties — unless the system is available for the public to report a criminal offence. White & Case gives the worked example: a chatbot on a law enforcement authority’s website. Public-facing crime-reporting bots get no exemption.
  • Out of scope entirely under Article 2. Chiefly individuals using AI systems in the course of a purely personal, non-professional activity. This is not an exception you can invoke as a business.

How far does “obvious” go?

The standard is contextual, not absolute — the Act says so, twice, with “taking into account the circumstances and the context of use.” So there is no such thing as a system that is obviously AI. There are only surfaces on which it is or isn’t obvious, and the same model can be on both sides of the line in the same company.

The reference person is where the argument gets decided, and the Act imported that person rather than inventing them. In Gut Springenheide (Case C-210/96), decided on 16 July 1998, the Court of Justice held that a national court assessing whether a description is misleading must take into account the presumed expectations of “an average consumer who is reasonably well-informed and reasonably observant and circumspect.” That formula became Recital 18 of the Unfair Commercial Practices Directive (2005/29/EC) and the default benchmark across EU consumer law. Article 50(1) reproduces it with one word dropped.

Three things follow, and none of them help a provider hoping for a bright line.

Nobody has defined it, deliberately. When the UCPD was negotiated, the definition of the average consumer was removed from the operative text — the European Parliament’s legislative record explains that a fixed definition was dropped precisely so the concept could keep evolving with the Court’s jurisprudence. The AI Act repeats the pattern: the formula appears in Article 50(1) and again in Recital 132, and is defined in neither. If you were waiting for the legislature to tell you what obvious means, it has told you it isn’t going to.

The reference person is not a rational maximiser. The Court has kept moving. In Compass Banca (Case C-646/22) it accepted that the average consumer’s assessment can be affected by cognitive bias — the benchmark is a notional typical consumer, not a perfectly rational market actor. A provider arguing “anyone would have realised” is arguing against a standard that has been explicitly loosened away from that assumption.

The reference person shifts when your audience does. Recital 132 says that in applying the obligation, account must be taken of the characteristics of people belonging to vulnerable groups due to their age or disability, insofar as the AI system is intended to interact with those groups too. This mirrors the UCPD, which makes specific provision for vulnerable consumers. Build a homework helper for teenagers and the person deciding what’s obvious is a teenager.

Apply that to two real surfaces. A support widget on your own site, opened by a user who clicked a button labelled “Chat”, staffed by a bot called AI Assistant, answering instantly at 3am: a decent argument that disclosure adds nothing a reasonably observant person doesn’t already have. An outbound call to a customer’s mobile in a synthetic voice: not obvious, ever. The recipient did not choose the channel, has no context, has one second of audio to work from, and the entire history of the average consumer test runs through cases about people being misled in exactly that posture.

White & Case’s own advice is to treat the exemption with caution, on the reasoning that a court or regulator may read the level of information a reasonably well-informed user is deemed to have more narrowly than a provider would like. One more reason for caution is on the calendar. The Commission is obliged under Article 96(1)(d) to develop guidelines on the practical implementation of Article 50, and its published FAQ confirms those guidelines will address AI interaction specifically, that a public consultation on the draft has closed, and that the final version will be published before the obligations start to apply. The guidelines can narrow the exception. They cannot widen it beyond the text.

What the Code of Practice does not cover

Worth knowing before you go looking: the Code of Practice on Transparency of AI-Generated Content is no help on this question. Article 50(7) directs the AI Office to facilitate codes of practice on the detection and labelling of artificially generated content — that is Article 50(2) and (4). When the Commission issued its opinion on 8 July 2026, it concluded the Code adequately covers Articles 50(2), (4) and (5). Article 50(1) is not on that list. There is no code to sign that demonstrates your chatbot disclosure is adequate.

Form and timing you can’t negotiate away

If the exception doesn’t apply, Article 50(5) governs how you tell people, and it is short enough to quote in full: the information “shall be provided to the natural persons concerned in a clear and distinguishable manner at the latest at the time of the first interaction or exposure. The information shall conform to the applicable accessibility requirements.”

Four consequences:

  • Clear and distinguishable. Distinguishable from what surrounds it. A line in the terms of service is not distinguishable; a greyed-out footer under the input box is a bad bet.
  • At the latest at first interaction. White & Case reads this as akin to the point-in-time notice requirements under the GDPR — the notice attaches to the moment, not to a document you have somewhere. You cannot disclose on turn three.
  • Accessibility requirements. Recital 132 adds that the information must be provided in a format accessible to persons with disabilities. A purely visual badge on a voice product fails this on its face.
  • Vulnerable users. This one is Recital 132, not Article 50(5) — worth knowing, because summaries routinely present it as an operative requirement. It shapes how the obligation and the exception are applied rather than adding a fifth element to the form rules.

Why the obligations stack

Article 50(6) says paragraphs 1 to 4 “shall not affect the requirements and obligations set out in Chapter III, and shall be without prejudice to other transparency obligations laid down in Union or national law for deployers of AI systems.” Chapter III is the high-risk regime. So clearing Article 50(1) tells you nothing about Articles 13 and 26, and nothing about the GDPR notice you already owed.

The general-purpose AI overlap is real but comes from elsewhere — Article 50(2) applies to providers “of AI systems, including general-purpose AI systems”, and Chapter V imposes its own model-level duties. White & Case reads the whole set as applying cumulatively. A conversational assistant built on a general-purpose model, deployed in a high-risk context, can owe disclosure under 50(1), marking under 50(2), instructions for use under Article 13 and model documentation under Chapter V, all at once. They are not alternatives and satisfying one is not a defence to another.

Frequently asked questions

Does a bot name count as disclosure?

Calling it “AI Assistant” is evidence that the fact was obvious, not compliance with the disclosure duty. The two are different arguments: one says the exception applies so no notice was owed, the other says notice was given clearly and distinguishably at first interaction. If you are relying on the name, you are relying on the exception — write down why, in context, before a regulator asks.

Does the exception apply to voice?

Not to outbound voice, realistically. The recipient did not initiate the interaction, has no visual context and no prior expectation, and synthetic speech is now good enough that “reasonably observant” does not get you there. Inbound voice on a line the caller dialled knowing it is automated is a different and better argument.

Who is liable, the provider or the deployer?

Article 50(1) puts the design duty on the provider. But the exception depends on the circumstances and context of use, which the deployer controls — so a provider who ships without disclosure on the assumption that deployment will be obvious has made a bet on someone else’s product decisions. Allocate it in the contract: who decides whether the exception is relied on, and who evidences it.

What about an AI agent that calls a customer?

In scope of Article 50(1), and the exception almost certainly does not apply. See outbound voice above. This is the single clearest case in the whole provision.

Does this apply to internal-only tools?

Yes, if the tool interacts directly with natural persons — the Act does not distinguish between customers and employees here. The Article 2 carve-out covers individuals using AI in a purely personal, non-professional activity, which is the opposite of an internal work tool. Whether disclosure is obvious to a trained employee using a named internal assistant is a much easier argument than the customer-facing case, but it is still the argument you have to make.

Posted by admin in Data, Identity & Compliance UX Knowledge Base

EU AI Act Article 50 deadline: what didn’t get delayed

Article 50 of the EU AI Act (Regulation (EU) 2024/1689) applies from 2 August 2026. The Digital Omnibus on AI deferred the high-risk rules — stand-alone Annex III systems to 2 December 2027, systems embedded in regulated products under Annex I to 2 August 2028 — and left the transparency obligations exactly where they were. One piece moved: the Article 50(2) machine-readable marking duty for systems already on the market, which gets until 2 December 2026.

So the headline everyone read — the EU delayed the AI Act — describes a deferral that skipped the obligation closest to landing. If you ship a chatbot, a generative feature, or anything that produces synthetic images, audio, video or text into the EU, your deadline did not move.

What actually applies on 2 August 2026?

Four transparency obligations apply in full and unchanged from 2 August 2026. They sit in Article 50 and they split across providers and deployers:

  • Article 50(1) — AI interaction disclosure. Providers must design systems that interact directly with people so those people are informed they are dealing with an AI system, unless it would be obvious to a reasonably well-informed, observant and circumspect individual.
  • Article 50(3) — emotion recognition and biometric categorisation notice. Deployers must inform the people exposed to the system and process their personal data in line with data protection law. Recital 18 confines “emotion” to states such as anger, satisfaction or shame — it excludes physical states like pain and fatigue.
  • Article 50(4) — deepfake and public-interest text labelling. Deployers must disclose artificially generated or manipulated image, audio and video content, and AI-generated text published to inform the public on matters of public interest.
  • Article 50(5) — how the notice is given. Clear and distinguishable, at the latest at the first interaction or exposure, conforming to accessibility requirements, and accounting for vulnerable people.

Article 50(6) makes these cumulative with the high-risk and general-purpose AI transparency duties rather than an alternative to them. And the exposure is real money: Article 99(4)(g) puts breaches of Article 50 in the tier of up to €15,000,000, or 3% of total worldwide annual turnover for the preceding financial year if the offender is an undertaking, whichever is higher. For SMEs and start-ups, Article 99(6) inverts that — the cap is the percentage or the fixed amount, whichever is lower.

The one thing that moved

Article 50(2) — the provider duty to mark synthetic output in a machine-readable format and make it detectable as artificially generated — now applies from 2 December 2026 for systems placed on the market before 2 August 2026. Systems placed on the market from 2 August 2026 comply on placing. There is no relief for new products.

Here the sources contradict each other, and the contradiction starts at the top. The Council’s press release of 29 June 2026 says the regulation “reduces the grace period for providers to implement transparency solutions for artificially generated content from 6 months to 3 months, with the new deadline set on 2 December 2026.” Both halves of that sentence cannot be right: 2 August to 2 December is four months. Law firm summaries have repeated the three-month figure because they were reading the press release. The date is the operative fact and the date is 2 December 2026 — write that in the plan, not the arithmetic.

There is a second wrinkle worth checking against the final text. The Commission’s FAQ on the Code of Practice on Transparency of AI-Generated Content describes the transitional period as covering AI systems in scope of Article 50(2) and (4) placed on the market before 2 August 2026. The Council press release describes it narrowly, as a grace period for providers implementing marking. The narrow reading is the safer one to plan against.

What the Omnibus did defer

The deferrals are real, they are substantial, and none of them touch Article 50(1), (3), (4) or (5). Taken from the Council’s own record of the adopted regulation:

Obligation Original date New date
Stand-alone high-risk AI systems (Article 6(2), Annex III) 2 August 2026 2 December 2027
High-risk AI embedded in regulated products (Article 6(1), Annex I) 2 August 2027 2 August 2028
National AI regulatory sandboxes established by competent authorities 2 August 2026 2 August 2027
Article 50(2) marking, systems on the market before 2 August 2026 2 August 2026 2 December 2026
New Article 5 prohibition on AI-generated NCII and CSAM — December 2026

That last row is the tell. This package was not a retreat. It added a prohibition on generating non-consensual sexual imagery and child sexual abuse material — the “nudifier” ban — into Article 5, alongside the deferrals. Marilena Raouna, Cyprus’s Deputy Minister for European Affairs, framed the adoption this way: “by banning AI-generated or manipulated sexual deepfakes and AI-generated child sexual abuse material, we are sending a clear message that technological progress must always go hand in hand with the protection of our fundamental values.”

The regulation also clarifies the AI Office’s supervisory competence over AI systems built on general-purpose AI models by the same provider, while leaving national authorities competent in law enforcement, border management, judicial authorities and financial institutions. Products covered by the Machinery Regulation ((EU) 2023/1230) are exempted from the AI Act’s direct applicability, and a new mechanism lets the Commission limit AI Act requirements by implementing act where sectoral law — medical devices, toys, lifts, watercraft — already imposes similar ones.

Is the Omnibus actually law yet?

As at 16 July 2026, no. The European Parliament endorsed the text on 16 June 2026 and the Council gave its final green light on 29 June 2026, closing procedure 2025/0359(COD). But the Council’s own next-steps note says the act “will be published in the EU’s official journal shortly and will enter into force on the third day after this publication.” No publication has been confirmed at the time of writing.

Until entry into force, the original calendar in Article 113 is the law. That is not a technicality — it is the difference between a plan and a hypothesis. The arithmetic is tight: with entry into force three days after publication, the regulation has to reach the Official Journal by 30 July 2026 to be in force before the 2 August 2026 date it is meant to displace. The co-legislators know this, which is why the Council said it treated this part of the package with “utmost priority.”

You can check the position yourself against the adopted text (PE-30-2026-INIT) and the EU Law tracker entry for procedure 2025/359 rather than against a summary. If you are reading this after publication, the dates in the table above are binding; before it, they are a forecast with very good odds.

What this means for your roadmap

An Article 50 programme cannot be re-baselined to 2027. Marking, labelling and first-interaction notice are engineering and design work against a fixed date, and the Omnibus gives you nothing on any of them except the legacy marking window.

The concrete pieces to have in place:

  • Inventory by Article 50 paragraph, not by risk tier. Article 50 catches minimal-risk systems. A support chatbot that will never be high-risk is still in scope of 50(1).
  • Marking for generative output across every modality — audio, image, video, text — for anything placed on the market from 2 August 2026, and by 2 December 2026 for what is already out there.
  • A decision on the Code of Practice. The Code of Practice on Transparency of AI-Generated Content was published on 10 June 2026; the Commission concluded on 8 July 2026 that it adequately covers Articles 50(2), (4) and (5), and the AI Board adopted its adequacy assessment the following day. Signing is voluntary and severable — the provider section and the deployer section can be signed independently. It is also not conclusive evidence of compliance, in the Commission’s own words.
  • Watch for the Commission’s Article 50 guidelines, which the Commission has said will be published ahead of 2 August 2026 and which will settle scope questions the Code deliberately leaves alone — including how far the “obvious” exception in Article 50(1) actually reaches.

The reasonable read of the last twelve months: the EU deferred the obligations that depend on infrastructure it hasn’t built — harmonised standards, notified bodies, designated national authorities — and kept the ones that depend only on you.

Frequently asked questions

Did the EU delay the whole AI Act?

No. The Digital Omnibus on AI deferred the high-risk obligations under Article 6(2) and Annex III to 2 December 2027, and those under Article 6(1) and Annex I to 2 August 2028, plus the national sandbox deadline to 2 August 2027. The Article 5 prohibitions (in force since 2 February 2025), the general-purpose AI rules (2 August 2025) and the Article 50 transparency obligations (2 August 2026) were not deferred.

Do I need watermarking by August 2026?

If the system is placed on the EU market from 2 August 2026, yes — Article 50(2) machine-readable marking applies at the point of placing, with no transitional period. If the system was already on the market before that date, the marking duty applies from 2 December 2026.

What if my system shipped in 2025?

It gets the Article 50(2) marking extension to 2 December 2026. It does not get an extension on Article 50(1) interaction disclosure, Article 50(3) emotion recognition notice or Article 50(4) deepfake labelling — those apply from 2 August 2026 regardless of when the system shipped.

Are the prohibitions delayed?

The existing Article 5 prohibitions have applied since 2 February 2025 and were never in scope of the deferral. The Omnibus adds a new prohibition on AI-generated non-consensual intimate imagery and CSAM, which the Council says takes effect in December 2026.

When will the Omnibus be in the Official Journal?

Not confirmed as at 16 July 2026. The Council said on 29 June 2026 that publication would follow “shortly,” with entry into force on the third day after. Working back from 2 August 2026, publication needs to happen by 30 July 2026 for the new dates to displace the old ones in time.

What is the fine for breaching Article 50?

Article 99(4)(g) sets the ceiling at €15,000,000 or 3% of total worldwide annual turnover for the preceding financial year, whichever is higher. For SMEs and start-ups, Article 99(6) reverses the test: the cap is whichever of the two is lower.

Posted by admin in Data, Identity & Compliance UX Knowledge Base

So what are we gonna do about Internet ID verification?

The digital world is buzzing with a question that feels both futuristic and alarmingly close: should we have a mandatory “Internet ID”? The idea, a form of digital passport to navigate the web, is no longer a fringe concept. It’s a debate seeping into the mainstream, fueled by a growing desire to hold people accountable for their online actions. While some see it as a silver bullet for the toxicity and chaos of the internet, others view it as a catastrophic step towards a surveillance state, a digital leash that could choke the very freedoms the internet was meant to champion.

The argument for a verified digital identity is, on its surface, compelling. Proponents, like many voices in a recent online discussion on the topic, paint a picture of a cleaner, safer internet. Imagine a web where anonymous trolls can no longer hide behind fake profiles to spew hatred and abuse. Consider a landscape where the industrial-scale spread of disinformation is crippled because every voice is tied to a real person. The appeal is a sense of order, a system where actions have consequences, and the dark corners of the web are finally illuminated. Some users believe this is the only logical step to combat everything from cyberbullying to large-scale criminal enterprises that exploit anonymity to thrive.

However, for every argument in favor, a dozen alarms bells seem to ring. The core of the anxiety lies in the immense power such a system would create. Who would hold the keys to this universal database of online activity? The immediate fear for many is government overreach. A mandatory Internet ID could become the ultimate tool for monitoring citizens, tracking every click, every conversation, every dissenting opinion. The potential for this data to be used to silence opposition, enforce conformity, or create a “social credit” system similar to those seen in authoritarian states is a chilling prospect for many. What starts as a tool to stop trolls could easily become a tool to stop protestors.

Even if one trusts the government, the technical reality of such a system is a nightmare in itself. A centralized database containing the personal information and online history of every citizen would be the most attractive target for hackers in the history of the internet. A single breach wouldn’t just be an inconvenience; it would be a societal catastrophe, potentially exposing the private lives of billions to criminals, foreign states, and black market data brokers. As many have pointed out, it’s not a question of if it would be breached, but when.

The discussion then naturally pivots to alternatives. What if the system wasn’t centralized? Ideas like decentralized identity verification, using blockchain or other cryptographic methods, are often proposed. In this model, users might control their own identity and only reveal the necessary information for any given transaction. This sounds promising, but it’s not without its own perils. A decentralized system is complex and may still be traceable. Furthermore, it could create a new digital divide, excluding those who are not tech-savvy enough to manage their own cryptographic keys or those without access to the necessary technology.

The debate over an Internet ID is more than a technical squabble; it’s a fundamental conflict of values. It pits the desire for security against the right to privacy, the wish for order against the fear of control. While the problems of the anonymous web are real and deeply felt, the proposed solution of a mandatory digital identity feels, to many, like a cure that is far worse than the disease. The conversation reveals a deep-seated unease about the future of online freedom. There is no easy answer, no perfect system. The path forward remains shrouded in a fog of uncertainty, and the question hangs in the air, leaving us to wonder what price we are willing to pay for a safer internet, and what we might lose in the bargain.

Posted by admin in Data, Identity & Compliance UX Knowledge Base, What happened with...

Why people don’t care about their privacy?

In an age where our lives are increasingly played out online, a curious paradox has emerged: while the chorus of warnings about data breaches, surveillance, and the erosion of personal privacy grows louder, a significant portion of the population appears to be tuning it out. A recent, and surprisingly lively, discussion on the popular online forum Reddit, specifically on the subreddit r/privacy, delved into this very issue, attempting to unravel the complex reasons behind this widespread apathy. The conversation, sparked by a user asking why people don’t seem to care about their privacy, revealed a fascinating, and at times unsettling, tapestry of resignation, calculated trade-offs, and a fundamental misunderstanding of what is truly at stake.
One of the most prevalent sentiments echoed throughout the discussion was the infamous “I have nothing to hide” argument. Many users, it seems, operate under the assumption that since they are not engaged in any illicit activities, the prying eyes of corporations or government agencies are of no concern. “Why should I care if someone knows what I search for on Google? It’s not like I’m a criminal,” one might argue. However, as many participants in the online debate were quick to point out, this line of reasoning is a dangerous oversimplification. Privacy, they argued, is not about hiding wrongdoing; it is about having the autonomy to control one’s own information, to maintain a personal space free from unwanted intrusion, and to prevent the creation of a detailed personal profile that could be used against them in unforeseen ways. The fear, as one commenter articulated, is not that the data will be used to prosecute them for a crime they didn’t commit, but that it will be used to manipulate them, to limit their opportunities, or to create a society where dissent is subtly, and automatically, suppressed.
The allure of convenience was another powerful theme that emerged from the digital discourse. In the modern world, a certain level of data sharing is the price of admission to a vast array of services that have become deeply integrated into our daily lives. From the personalized recommendations on streaming services to the seamless navigation provided by mapping applications, we are constantly making small, almost unconscious, trade-offs between our privacy and the ease and efficiency that these technologies offer. The problem, as highlighted by the more concerned voices in the Reddit thread, is that these transactions are rarely transparent. The true cost of “free” services is often obscured, buried in lengthy and unreadable terms of service agreements. What appears to be a simple exchange for a more convenient life is, in reality, a far more complex and potentially exploitative relationship where the user is the product, and their data is the currency.
Perhaps the most disconcerting reason for this growing indifference, however, is a pervasive sense of helplessness. Many individuals feel that the battle for privacy is already lost. The sheer scale and complexity of the data collection apparatus, with its intricate web of trackers, cookies, and data brokers, can feel overwhelming. The sense that powerful, faceless corporations and government entities are already in possession of vast swathes of our personal information can lead to a feeling of resignation. “What’s the point of fighting it?” some seem to ask. This sentiment is further compounded by a lack of immediate, tangible consequences. Unlike a physical threat, the harm caused by privacy violations is often abstract and delayed. It is a slow, creeping erosion of personal freedom, the full impact of which may not be felt for years to come.
As the threads of the online conversation unraveled, a chilling picture began to form: a society so enamored with the baubles of technology, and so resigned to the perceived inevitability of surveillance, that it is willingly, if not always consciously, sacrificing a fundamental human right. The question that lingers, long after the last comment has been posted, is what the future holds for a world where privacy is no longer a societal norm but a luxury for the few who are willing, and able, to fight for it. Are we, as some of the more anxious voices in the online forum suggested, sleepwalking into a future where our every move is monitored, our every preference is cataloged, and our every decision is subtly influenced by forces beyond our control? The discussion on Reddit may not have provided any easy answers, but it served as a stark reminder that the conversation about privacy is not just a niche concern for the paranoid, but a critical issue that will define the very nature of our society in the years to come.
Source: Reddit

Posted by admin in Data, Identity & Compliance UX Knowledge Base, What happened with...

How is the UK going to fine a company for not running age checks?

In the sprawling, often anonymous landscape of the internet, a persistent question bubbles to the surface: if laws exist to punish harassment, why does the threat of “doxing”—the act of publishing someone’s private information, like their home address—still carry such a palpable sense of menace? A discussion online grapples with this very issue, exploring whether the legal frameworks in place are a sturdy shield against harassment or a paper-thin barrier, easily torn by the realities of the digital age.

The core of the argument for the effectiveness of these laws is straightforward. Publishing an address, in itself, is not typically a crime. The crime occurs when that act is followed by a pattern of behavior that causes a person to reasonably fear for their safety. This could be a flood of unwanted deliveries, threatening letters, or people showing up at their home. As one commenter puts it, the law isn’t about the initial act but the consequences: “The publication of the address isn’t the harassment. The hundreds of pizzas being delivered to their house is.” In this view, the law acts as a deterrent. A potential harasser must weigh the fleeting satisfaction of their actions against the very real possibility of a restraining order, fines, or even jail time. The legal system, though reactive, is seen as a powerful tool to punish those who cross the line from sharing information to inciting fear.

However, a chilling counter-argument quickly emerges from the discussion, casting a shadow of doubt over this sense of security. The problem, many argue, lies not in the text of the law but in its practical application. The digital world allows for a scale and anonymity of harassment that legal systems are ill-equipped to handle. The “lone wolf” theory is a prominent source of anxiety: it only takes one determined, unhinged individual from a sea of thousands to ignore the legal deterrents and pose a genuine physical threat.

Furthermore, the burden of proof becomes a significant hurdle. Who, precisely, is the harasser? Is it the individual who first posted the address? Is it the online mob that “likes” and shares the post, amplifying its reach? Or is it the anonymous user who actually sends the threat or shows up on the doorstep? As one user points out, “The person who originally posted the address isn’t the one doing the harassing. It’s the thousands of people who see it and decide to act on it.” This diffusion of responsibility makes it incredibly difficult for law enforcement to build a case. An investigator is faced with a tidal wave of digital noise, often originating from jurisdictions across the globe, making the task of identifying and prosecuting any single individual a near-impossible feat.

This leads to a larger, more unsettling question: do the authorities have the resources, or even the will, to pursue such cases? In a world of limited police resources, online harassment, especially when it hasn’t escalated to physical violence, can be dismissed as a low-priority issue. Victims may be told that little can be done until a “real” threat materializes, leaving them in a state of perpetual fear, waiting for the digital menace to manifest on their physical doorstep.

The conclusion drawn from this digital discourse is a disquieting one. While criminal harassment laws offer a theoretical backstop against the dangers of doxing, their practical effectiveness in the internet age is deeply uncertain. The system is built to address singular, identifiable threats, not the decentralized, crowd-sourced harassment that defines modern doxing. The law may exist on the books, but the anonymity, scale, and jurisdictional chaos of the internet create a fog of war that makes enforcement a monumental challenge. This leaves individuals, particularly public figures, in a precarious position, protected by a legal shield that may be more illusion than reality. The fear isn’t just that someone will post their address; it’s that the system designed to protect them is fundamentally unprepared for the anonymous, borderless mob that might see it.
Source: Reddit

Posted by admin in Data, Identity & Compliance UX Knowledge Base, What happened with...

How to delete biometric data?

In an age where our digital and physical identities are increasingly intertwined, the question of data ownership has taken on a new, more personal dimension. We unlock our phones with our faces, access our workplaces with our fingerprints, and consent to biometric scans for a growing number of services. But what happens when we want to reclaim that data? What is the process for deleting something so intrinsically tied to our being? A recent discussion online delved into this very issue, revealing a landscape of uncertainty, anxiety, and a distinct lack of control.
The conversation, sparked by a user’s simple question on how to have their biometric data deleted by a company, quickly highlighted a fundamental fear: that it may not be possible at all. The core of the anxiety stems from the nature of biometric data itself. Unlike a password or a credit card number, it cannot be changed. Your fingerprint, your iris, your unique facial geometry are yours for life. Once that information is handed over, is it truly ever gone?
Participants in the discussion raised the unsettling possibility that companies may not honor deletion requests, or may not be technically capable of doing so completely. Data gets backed up, archived, and sometimes sold or shared with third parties. A request to the frontline company might be honored, but where else has that data traveled? This creates a sense of digital permanence that is deeply unnerving. The data’s lifecycle is opaque, leaving the individual with little more than a company’s assurance that it has been deleted – a promise that many are hesitant to trust. “The only winning move is not to play,” one commenter suggested, a sentiment that resonated throughout the thread, pointing to a growing belief that prevention is the only viable form of control.
The legal framework surrounding this issue is a complex and often confusing battleground for the average person. While laws like the Biometric Information Privacy Act (BIPA) in Illinois provide consumers with some of the strongest protections in the United States, including a private right of action, such robust legislation is not the norm. This patchwork of regulations means that an individual’s rights can vary dramatically depending on their location and the location of the company holding their data. For many, the prospect of navigating this legal maze is daunting, if not impossible. The discussion suggests a power imbalance where individuals are left with few practical resources to enforce their rights against corporations with vast legal teams.
The dialogue ultimately circles back to a series of troubling questions that hang in the air for the modern consumer. Who is the ultimate custodian of our most personal data? Do we truly own our biometric identities once we’ve used them as a key? The consensus from the online discourse seems to point to a sobering conclusion: in the current digital ecosystem, the ability to truly and permanently delete one’s biometric data is, at best, an illusion. The act of giving consent, even for a seemingly innocuous service, may be an irreversible step into a world where our most unique identifiers are no longer exclusively our own. The conversation serves as a stark reminder that in the rush for convenience, we may be trading away something far more valuable, and far more permanent. The final thesis, as echoed by the concerned voices in the discussion, is one of caution. In the digital age, the most powerful tool for protecting your biometric data isn’t a deletion request; it’s the ability to say no in the first place.
For those interested in the original discussion, you can find the thread on Reddit: https://www.reddit.com/r/privacy/comments/1m9dfb3/how_to_delete_biometric_data/
Source: Reddit

Posted by admin in Data, Identity & Compliance UX Knowledge Base, What happened with...

Data privacy assessment frameworks

In an age where personal data is the new currency, the frameworks designed to protect it remain surprisingly opaque to the public eye. A recent discussion initiated on the popular online forum Reddit brings a critical question to the forefront: are we placing too much faith in a single standard for data privacy? The conversation began with a simple query from a user who, like many professionals in the field, defaults to the frameworks provided by the National Institute of Standards and Technology (NIST). “NIST has been and is my go to,” the user stated, before asking a pivotal question to the community: “wondering if folks have used or like others?”

This question, while seemingly straightforward, peels back a layer of the complex world of data protection, revealing a potential over-reliance on a handful of established, yet not universally understood, guidelines. The very act of seeking alternatives suggests a latent concern that a single framework, no matter how robust, may not be a panacea for the multifaceted challenges of digital privacy. It prompts a deeper inquiry: what are these other frameworks, and why are they not more prominent in the public discourse surrounding data security? The silence that often follows such questions in open forums can be unsettling. Does it signify a widespread consensus around a single standard, or does it point to a more troubling lack of accessible, alternative solutions for safeguarding our digital lives?

The reliance on a framework like that from NIST is understandable. As a non-regulatory agency of the United States Department of Commerce, NIST provides a gold standard for many industries, offering a pathway to structured, risk-based privacy management. Its guidelines are thorough, widely respected, and offer a clear methodology for organizations to follow. However, the digital world is not a monolith. It is a global, interconnected ecosystem. This raises the question of whether a U.S.-centric framework can adequately address the diverse legal, cultural, and ethical landscapes of data privacy around the world. As data flows seamlessly across borders, the search for more universal or adaptable frameworks becomes not just an academic exercise, but a pressing necessity.

The absence of a vibrant, public debate comparing various data privacy assessment frameworks could be interpreted in several ways. On one hand, it might imply that the existing standards are so effective that they leave little room for improvement or competition. On the other, more anxious hand, it could suggest a dangerous monoculture. When an entire ecosystem leans heavily on a single pillar for support, any undiscovered crack or structural flaw in that pillar threatens the integrity of the entire structure. What happens if a sophisticated, state-level actor finds a systemic vulnerability in the most commonly used framework? The consequences could be catastrophic, precisely because of the lack of widely adopted alternatives.

Ultimately, the quest for different data privacy assessment frameworks is not merely about finding a substitute for NIST; it is about building resilience through diversity. The initial question posed on Reddit should not be seen as a simple request for a list, but as a call to action for a more transparent and multifaceted approach to data protection. The strength of our collective privacy shield will not be determined by the rigidity of a single standard, but by our ability to foster, discuss, and implement a variety of frameworks that can adapt to the ever-changing digital frontier. The disquieting truth may be that our current sense of security is based on a foundation that is less diverse and more fragile than we realize, leaving the door open to risks we have yet to even consider.
Source: Reddit

Posted by admin in Data, Identity & Compliance UX Knowledge Base, What happened with...