What this page is for
It helps users produce a concrete artifact, checklist, or decision note instead of only reading generic advice. The page is written for people comparing options and preparing a real workflow.
US SaaS guide
EU AI Act for US SaaS Companies
A US company can still have EU AI Act exposure when it places an AI system on the EU market, serves EU customers, supports EU deployers, or produces outputs used in the EU. Start with scope, then classify the use case.
Disclaimer: This guide is for general planning by SaaS teams. It is not legal advice and should not be used as a final cross-border compliance opinion.
Scope questions for US teams
| Question | Why it matters |
|---|---|
| Do you offer the AI feature to EU customers or users? | EU market availability can create review needs even when the company is incorporated in the United States. |
| Do EU-based customers deploy the feature inside their workflows? | Your customer may be a deployer, while your company may still have provider or supplier duties depending on the product role. |
| Are AI outputs used in the EU? | Article 2 includes certain providers and deployers outside the EU when output produced by the AI system is used in the Union. |
| Do you control the model, intended purpose, or key product behavior? | Control over intended purpose and system design is important when assigning provider, deployer, importer, or distributor roles. |
| Do you sell through partners, marketplaces, or enterprise resellers? | Distribution channels can add role-mapping and documentation requests. |
Practical readiness checklist
- Create an inventory of AI features, including internal admin tools exposed to EU customer data.
- Record intended purpose, user group, model provider, data categories, and output use for each feature.
- Screen for Article 5 prohibited practices before pilots or beta launches.
- Screen for Article 6 and Annex III high-risk areas when the feature affects access, eligibility, employment, education, public services, safety, or rights.
- Add Article 50-style transparency notices for chatbots, AI assistants, generative media, and other user-facing AI interactions.
- Prepare a short customer-facing AI system note that explains the product role, limitations, oversight options, and support channel.
- Review contracts and product docs so sales claims do not expand the intended purpose beyond what the system was tested to do.
Common SaaS examples to review
| Feature | Review focus |
|---|---|
| AI support chatbot | Transparency notice, escalation to human support, limitation language, and data handling. |
| AI hiring assistant | Employment high-risk signal, human oversight, documentation, evaluation, and vendor role mapping. |
| Lead scoring or fraud scoring | Whether the score affects access, eligibility, pricing, services, or treatment of individuals. |
| Document summarization | Transparency, accuracy warnings, review path, and whether summaries are used for consequential decisions. |
| Generated marketing media | AI-generated content disclosure and deepfake or synthetic media rules where relevant. |
Official sources
Last reviewed: July 3, 2026.
- EU AI Act Article 2: scope
- EU AI Act Article 3: definitions
- EU AI Act Article 5: prohibited practices
- EU AI Act Article 6: high-risk classification
- EU AI Act Article 50: transparency obligations
- European Commission: AI Act regulatory framework
Updated review note
Review and responsible-use note
EU AI Act for US SaaS Companies is maintained as a practical page for AI compliance self-assessment. Use the result to organize internal review, collect evidence, and decide when a qualified legal or compliance specialist should review the system.
What it does not replace
These tools provide operational checklists and first-pass triage, not legal advice, certification, or a guarantee of EU AI Act compliance.
How to verify the result
The highest-risk scenarios on this site are framed as compliance reviews, not as instructions to build or deploy sensitive AI systems. Useful references include EU AI Act official text and European Commission AI Act overview.
Practical value note
How this page supports the site
EU AI Act for US SaaS Companies gives visitors context about AI Compliance Kit, the workflow boundaries, and how the site's AI compliance review pages should be used. It supports trust by explaining purpose, limitations, contact paths, and review expectations.
Who this is for
EU AI Act for US SaaS Companies is written for founders, product owners, compliance teams, and operators preparing AI systems for review. It assumes the visitor wants to complete a practical task, not browse a decorative landing page.
What to save
The useful result should be a checklist, report, policy draft, questionnaire, or review note that can be copied, downloaded, printed, compared, or used as a next-step working document.
What to check
The output is an operational preparation aid. It should be reviewed against the actual system, data flow, jurisdiction, and qualified legal or compliance advice before production use. Keep the original source material and record the assumptions used for the generated result.
Use this page to understand the site before relying on any generated output or publishing a changed file, policy, or technical configuration. If the result affects a public page, customer-facing workflow, policy decision, or uploaded file, review one sample manually before repeating the workflow in bulk.