Global AI Regulation by Country
The useful question isn’t whether a country is strict or relaxed. It is what kind of rule you’re dealing with.
Comprehensive statutes. The EU has a risk-based act, covered above. South Korea’s AI Basic Act has been in force since January 22, 2026. It sets transparency duties for generative AI, obligations for high-impact AI and safety duties for very large models, and applies to foreign providers above certain thresholds (the draft decree used global revenue above KRW 1 trillion, domestic AI revenue above KRW 10 billion or more than one million daily users) that must appoint a local representative. Administrative fines are capped at KRW 30 million, and the ministry has said it will hold off on fines for at least a year. That grace period is an enforcement policy, not something written into the statute. The US International Trade Administration’s guide is a good starting point.
Binding AI-specific rules without a single AI law. China has no comprehensive AI statute but has layered binding rules: the Interim Measures for Generative AI Services (in force since August 15, 2023, with filing and content duties), the Measures for Labeling AI-Generated Content (September 1, 2025), a Cybersecurity Law amendment with an AI clause (January 1, 2026) and Measures on Anthropomorphic AI Interaction Services (July 15, 2026). India has no standalone AI law either. Its AI Governance Guidelines (November 2025) are non-binding. The binding AI-specific rule today is the IT Rules amendment in force since February 20, 2026, which brings synthetic audio and visual content under intermediary due-diligence duties, including labeling. India’s Digital Personal Data Protection Act is on the way, but its core obligations don’t start until May 2027, so the IT Act and its privacy rules govern personal data until then.
Existing laws and sector regulators. The UK has no AI statute. Sector regulators apply principles through their existing powers, and the Data (Use and Access) Act 2025 reworked the UK GDPR’s automated decision-making rules. A dedicated AI bill didn’t appear in the May 2026 King’s Speech, and a private member’s bill on advanced AI, set for second reading on November 13, 2026, has no government backing. Canada’s proposed AI act died with Parliament’s prorogation in January 2025 and has not been replaced. Bill C-36, a privacy bill introduced in June 2026 that would add duties around automated decisions, has only passed first reading. Australia has no standalone AI act and relies on existing consumer, privacy and sector law. Japan has a promotion-oriented AI law without direct penalties, and Singapore leans on voluntary frameworks such as AI Verify.
Pending proposals. Brazil’s AI bill (PL 2338/2023) passed the Senate in December 2024 and is waiting for a committee report in the Chamber of Deputies. Nothing in it has legal effect yet.
What this means across borders: one HR screening tool can be a future high-risk system in the EU, trigger a notice duty in Illinois today, fall under ADMT rules in California and Colorado from 2027, need a bias audit in New York City, and be handled through equality and data protection law in the UK. Classifying the tool once, globally, doesn’t work. Classify it per market.
The G20 and the Carolina Principles
On September 1–2, 2026, the US hosted a G20 Innovation Ministerial in Chapel Hill, North Carolina. Ministers reached consensus on the Carolina Principles for Emerging Technologies, a non-binding framework that calls for investment in foundational research, faster routes to commercialization and trusted adoption, and that favors reserving new AI rules for genuinely novel issues. The US Commerce Department’s announcement has the official summary. G20 leaders are expected to take it up when they meet in December.
The principles are not law anywhere and they don’t replace obligations where you operate. They do show how far apart the major economies are: the US is arguing for less dedicated AI regulation while the EU enforces the framework it built.
What Is Sovereign AI Regulation?
“Sovereign AI” covers several different worries. Data sovereignty is about keeping certain data inside national borders. Infrastructure sovereignty is about where compute physically sits. Model sovereignty asks whether a country can build or access models without depending on a foreign provider. National capability is the industrial and security policy behind all of it.
These concerns show up in export controls, procurement rules that favor domestic hosting and data localization laws. For AI procurement they turn into plain questions: where is the vendor’s model hosted, where is your data processed, and does that create exposure under residency or export-control rules?
AI Regulation and Privacy Law
AI-specific rules sit alongside privacy law, not in place of it. An AI system that processes personal data in the EU can fall under both the AI Act and the GDPR. They ask different questions: the AI Act looks at the system’s risk profile, and the GDPR looks at lawful basis, purpose limitation and individual rights. See our guide to dual AI Act and GDPR compliance.
The same layering shows up elsewhere. In the US, one automated decision tool may need to satisfy a state AI rule and a general privacy law at once, as with California’s CCPA ADMT regulations. In India, personal data in AI workflows will fall under the DPDP Act once its core duties begin in 2027. Data flow mapping, access controls, minimization and documentation support all of these workstreams, and reducing how much sensitive data an AI system sees lowers exposure under each.
What Should Businesses Do About AI Regulation Now?
Waiting for one global rulebook isn’t a strategy, and the direction of travel is more variation, not less. A practical sequence:
Inventory every AI system, including features built into vendor products and tools employees adopted on their own. Ask IT, procurement and business teams, then check SaaS admin consoles and expense reports for anything nobody approved.
Record your role for each system. Under the EU Act that means provider, deployer, importer or distributor. Under US state laws it usually means developer or deployer. Putting your name on a system built on someone else’s model can change your role.
Map each system to places and activities: which countries and US states it is used in, whose decisions it influences and what it is used for.
Check for regulated categories such as employment, credit, education, health, essential services, biometrics, chatbots and synthetic content. Next to each, note whether the rule is in force, scheduled, proposed or only guidance.
Find the data going in: personal, confidential and regulated data entering AI workflows, and what leaves your environment.
Review vendors on data retention, training on your data, subprocessors, processing locations, documentation, audit rights and incident notification.
Keep evidence: a description of each use case, the reasoning behind its classification, testing and bias results, oversight procedures, notices given, and decision logs where relevant.
Name an owner for each system and one for regulatory monitoring. Review on a set schedule, and keep a separate calendar for future deadlines so they aren’t mistaken for duties you already have.