The European Commission's Code of Practice on Transparency of AI-generated Content has taken effect, supporting compliance with new AI Act transparency rules that became applicable on 2 August 2026.

The obligations, set out under Article 50 of the AI Act, require marking and labelling of AI-generated content, including deepfakes and certain AI-generated publications, to address risks of deception and manipulation. The code itself is voluntary, but the underlying Article 50 transparency requirements are legal obligations.

Drawn up by independent experts through a multi-stakeholder process facilitated by the AI Office, the code has two sections: one covering rules for providers on marking and detection of AI-generated and manipulated content, and one covering rules for deployers on labelling deepfakes and AI-generated or manipulated text. The Commission and the AI Board have confirmed the code as an adequate voluntary tool for demonstrating compliance.

Signatories can rely on the code's measures to show compliance, reducing administrative burden and providing legal certainty across EU member states. Those who choose other compliance routes must demonstrate adequacy individually to national market surveillance authorities. Signatories will also take part in Signatory Taskforces to share practices and advance implementation.

The EU claims that by the end of July 2026, around 190 companies and organisations had signed the code.

Mobile Identity vs SMS OTP: 5 APIs could get you there
When 15-20% of SMS one-time passwords fail to deliver, you’re not just losing security—you’re losing customers. Companies switching to network APIs report 4-5% growth uplift. SIM swap attacks are up 1,000% in some markets. SMS pumping fraud costs tens of thousands monthly. Authentication delays cause measurable abandonment. Yet enterprises remain stuck on infrastructure everyone agrees is obsolete. Bahadir “Bob” Yavuz, Head of Products at GTC, and Stewart Tinson, Project Director at AI-360 You’ll learn: • Why SMS delivery rates run 15-20% below submission rates—and what that costs you • How network APIs like Number Verify deliver verification in 1-2 seconds vs 15-20 for SMS • The Indonesia model: 200+ million users, 20% improvement, all three telcos collaborating • Which APIs can achieve both an enhanced quality of security, and quality of service to the end user Key topics: Synthetic identity detection • Number Verify vs SMS OTP • SIM swap attack patterns • GSMA Camara and OpenGateway standards • Data quality in fraud detection • GDPR privacy-by-design architecture • Telco collaboration requirements • Real-world deployment case studies • False positive rate management • Network API productization For CISOs, CIOs, CFOs, and security teams evaluating authentication strategies, this session provides the business case, technical reality, and deployment roadmap for moving beyond SMS.
BrightTALK
Share this post
The link has been copied!