EU & cross-borderUpdated 22 November 20269 min read

EU AI Act for Indian Companies: Does It Apply to You?

A scoping guide for Indian companies: when Regulation (EU) 2024/1689 reaches you, which role you play, which obligations and dates apply, and what the Digital Omnibus proposal might change.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Regulation
(EU) 2024/1689
In force
1 August 2024
Prohibited practices and AI literacy
From 2 February 2025
GPAI model obligations
From 2 August 2025
Article 50 and Annex III high-risk
From 2 August 2026 (as adopted)
Annex I product-embedded high-risk
From 2 August 2027
Maximum fine
€35m or 7% of worldwide turnover

Quick answer

The EU AI Act applies to an Indian company if it places AI systems or general-purpose AI models on the EU market, or if its AI system's output is used in the EU (Article 2). Prohibitions apply from 2 February 2025, GPAI duties from 2 August 2025, and Article 50 and Annex III high-risk rules from 2 August 2026 under the Regulation as adopted.

  • Article 2 makes the AI Act extraterritorial: Indian providers are covered when they place AI on the EU market or their system's output is used in the EU.
  • Obligations depend on role (provider, deployer, importer, distributor) and risk tier (prohibited, high-risk, transparency, minimal).
  • Non-EU providers of high-risk AI systems and GPAI models must appoint an EU authorised representative.
  • Fines reach €35m or 7% of worldwide turnover for prohibited practices and €15m or 3% for most other obligations.
  • The November 2025 Digital Omnibus is a proposal that would delay some high-risk deadlines; check its adoption status before relying on it.

Who this is for: Indian AI product companies with EU customers, IT services firms building AI for EU clients, Indian foundation model and GPAI builders, Global capability centres of EU groups, Compliance and legal teams

Does the EU AI Act apply to Indian companies?

Yes, in three common situations. Under Article 2, the AI Act applies to:

  1. Providers that place AI systems on the EU market or put them into service in the EU, or place general-purpose AI (GPAI) models on the EU market — regardless of where they are established.
  2. Deployers of AI systems that are established or located in the EU.
  3. Providers and deployers outside the EU where the output produced by the AI system is used in the EU.

The third limb is the one Indian companies most often miss. If an Indian firm runs an AI system in India and sends the results — scores, recommendations, generated content — to a client in Germany who uses them, the Act can reach the Indian firm.

Quick test

QuestionIf yes
Do you sell or license an AI product to EU customers?You are likely a provider in scope
Do you offer a GPAI model (API or weights) to EU users?GPAI obligations likely apply
Is your AI's output used in the EU, even if the system runs in India?You may be in scope as provider or deployer
Do you build AI under contract that an EU client markets under its own name?The client may be the provider; check contract and role
Do you only use AI internally in India with no EU output?Likely out of scope

Being in scope does not mean heavy obligations. Most AI systems fall in the minimal-risk tier with few duties beyond AI literacy and, where relevant, Article 50 transparency.

Which role are you: provider, deployer, importer or distributor?

Obligations attach to roles, so identifying yours is the first job.

RolePlain meaningTypical Indian example
ProviderDevelops an AI system or GPAI model, or has one developed, and places it on the market under its own name or trademarkIndian SaaS company selling an AI product to EU firms
DeployerUses an AI system under its authority in a professional contextEU client using an Indian vendor's tool; an Indian GCC using AI for EU operations
ImporterEU-established entity placing a non-EU provider's system on the EU marketEU reseller of an Indian AI product
DistributorMakes a system available in the EU supply chain, other than provider or importerEU marketplace or channel partner
Authorised representativeEU-based entity mandated by a non-EU providerRequired for non-EU providers of high-risk systems and GPAI models

IT services nuance

Indian IT services firms often build AI systems that an EU client then deploys under the client's name. In that case the client may be the provider and the Indian firm a supplier. But if the Indian firm markets the system under its own name, it is the provider. Spell out roles in the contract and the statement of work.

Changing roles

A deployer that substantially modifies a high-risk system or puts its name on it can become a provider. Fine-tuning a GPAI model can, depending on extent, also shift responsibilities.

Risk tiers and what each requires

The AI Act sorts AI into tiers. Your obligations depend on where each system lands.

Prohibited practices (from 2 February 2025)

A list of practices considered unacceptable, such as certain manipulative techniques, social scoring and specific uses of biometric systems. Check the list in the Regulation; if any product feature is near the line, take legal advice.

High-risk systems

  • Annex III use cases (from 2 August 2026 as adopted) include employment — recruitment, selection, promotion, termination, task allocation and monitoring — and creditworthiness and credit scoring of natural persons (fraud detection excepted), among others.
  • Annex I product-embedded AI (from 2 August 2027).
  • Providers must meet requirements on risk management, data governance, technical documentation, logging, transparency to deployers, human oversight, accuracy and robustness, and conformity assessment. See high-risk rules for HR-tech and credit scoring.

Transparency (Article 50, from 2 August 2026)

Chatbot disclosure, machine-readable marking of generated content, deepfake and emotion recognition disclosures. See the Article 50 checklist.

GPAI models (from 2 August 2025)

Technical documentation, information for downstream providers, copyright policy and a public training-content summary; extra duties for systemic-risk models. See GPAI obligations for Indian model builders.

Minimal risk

No specific obligations beyond AI literacy, though voluntary codes are encouraged.

Key dates and the Digital Omnibus proposal

DateMilestone
1 Aug 2024AI Act enters into force
2 Feb 2025Prohibited practices and AI literacy obligations apply
2 Aug 2025GPAI model obligations apply; GPAI Code of Practice published July 2025
2 Aug 2026Most remaining provisions, including Article 50 and Annex III high-risk
2 Aug 2027High-risk AI in Annex I regulated products

The Digital Omnibus

In November 2025, the European Commission proposed a Digital Omnibus package that would, among other things, delay some high-risk deadlines. It is a legislative proposal; it changes nothing until adopted by the European Parliament and Council and published in the Official Journal.

As of today's date, verify its status yourself on EUR-Lex and the Commission's AI Act page. Until you have confirmed adoption and the final wording, plan to the Regulation's original dates. Being ready early costs little; being late on an obligation that did not move is expensive.

Fines and enforcement

The AI Act sets three main fine ceilings, each the higher of a fixed amount or a percentage of worldwide annual turnover:

InfringementMaximum fine
Prohibited practices€35 million or 7%
Most other obligations (including high-risk and transparency duties)€15 million or 3%
Supplying incorrect, incomplete or misleading information to authorities€7.5 million or 1%

Enforcement is by national market surveillance authorities in each Member State, with the Commission's AI Office responsible for GPAI models.

Practical exposure for Indian firms

  • Customers push obligations down. EU deployers will contractually require you to provide documentation, logs and transparency information.
  • Authorised representatives carry liability. An EU representative will want evidence that you meet obligations before accepting the mandate.
  • Procurement filters. Large EU buyers are adding AI Act questions to vendor due diligence regardless of enforcement timing.

Compare this with India's position: there is no standalone AI law, and MeitY's AI governance guidelines rely on existing laws such as the DPDP Act.

Action plan for Indian companies

  1. Inventory every AI system and model you build, sell or operate, and note EU customers or EU use of outputs.
  2. Assign roles per system: provider, deployer, importer, distributor.
  3. Classify risk: check against prohibited practices, Annex III, Article 50 and GPAI definitions.
  4. Close quick wins: AI literacy training for staff working with AI, chatbot disclosure, output marking.
  5. For high-risk systems: start technical documentation, risk management, logging, human oversight design and conformity assessment planning; appoint an EU authorised representative.
  6. For GPAI models: prepare documentation, downstream information, copyright policy and training-content summary; consider the GPAI Code of Practice.
  7. Update contracts to allocate AI Act roles and information duties.
  8. Align with GDPR and DPDP: the AI Act does not replace data protection. Personal data in training and inference still needs a GDPR basis for EU individuals and DPDP compliance for Indian individuals from 13 May 2027. See selling AI SaaS to Europe.
  9. Monitor the Omnibus and Commission guidance.

Common mistakes

  • Assuming Indian incorporation keeps you out.
  • Forgetting the "output used in the EU" limb.
  • Treating every AI feature as high-risk, or none.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Inventory AI systems with EU exposure

    List systems sold in the EU or whose outputs are used there.

    AI Act Art. 2

  2. Assign an AI Act role per system

    Record provider, deployer, importer or distributor status and the reasoning.

    AI Act Art. 2-3

  3. Screen for prohibited practices

    Check features against the prohibited list and remove or redesign any that come close.

    AI Act (prohibited practices)

  4. Check Annex III use cases

    Identify employment, credit scoring and other high-risk uses.

    AI Act Annex III

  5. Implement Article 50 transparency

    Add chatbot disclosure and machine-readable output marking.

    AI Act Art. 50

  6. Run AI literacy training

    Train staff who build or operate AI on capabilities, limits and risks.

    AI Act (AI literacy)

  7. Appoint an EU authorised representative

    Required for non-EU providers of high-risk systems and GPAI models.

    AI Act

  8. Track Digital Omnibus status

    Confirm adoption and final text before changing any compliance date.

    Digital Omnibus proposal

Key dates

  1. EU AI Act enters into force

  2. Prohibited practices and AI literacy apply

  3. GPAI model obligations apply

  4. Article 50 transparency and Annex III high-risk rules apply (as adopted)

  5. Annex I product-embedded high-risk rules apply

Answers

Frequently asked questions

Does the EU AI Act apply outside the EU?

Yes. Article 2 covers providers placing AI systems or GPAI models on the EU market wherever they are established, and providers and deployers outside the EU where the AI system's output is used in the EU. Indian companies with EU customers or EU-facing outputs are frequently in scope.

Is my Indian chatbot product high-risk under the AI Act?

Usually not. A general customer-service chatbot is typically subject to Article 50 transparency, meaning users must be told they are interacting with AI. It becomes high-risk only if used for an Annex III purpose, such as screening job candidates or assessing creditworthiness of individuals.

When do the EU AI Act obligations start?

Under the Regulation as adopted: prohibitions and AI literacy from 2 February 2025, GPAI obligations from 2 August 2025, Article 50 and Annex III high-risk rules from 2 August 2026, and Annex I product-embedded high-risk from 2 August 2027. A Digital Omnibus proposal may delay some high-risk dates; check adoption.

What is the Digital Omnibus?

A package proposed by the European Commission in November 2025 that would amend parts of EU digital law, including delaying some AI Act high-risk deadlines. It is a proposal until adopted by the Parliament and Council and published. Check its status before relying on any revised date.

Do Indian companies need an EU representative under the AI Act?

Non-EU providers of high-risk AI systems and of GPAI models must appoint an EU authorised representative. Providers of systems that only carry Article 50 transparency duties are not subject to that specific requirement, though GDPR Article 27 may separately require a representative.

What are the AI Act fines?

Up to €35 million or 7% of worldwide annual turnover for prohibited practices, €15 million or 3% for most other obligations, and €7.5 million or 1% for supplying incorrect or misleading information, in each case whichever is higher for most undertakings.

Legal references and sources

  • EU AI Act, Regulation (EU) 2024/1689 — Article 2 (scope) (official text)
  • EU AI Act, Regulation (EU) 2024/1689 — Article 50; Annex III (official text)
  • EU AI Act, Regulation (EU) 2024/1689 — Penalties (fines) (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.