EU AI Act Article 50 · Transparency
AI Provider Transparency
Understanding how Arch Agent uses AI
We publish this page because you have a right to know exactly what AI providers process your development context - and because EU AI Act Article 50 requires us to disclose it.
Arch Agent is a BYOK (Bring Your Own Key) platform. Your AI provider API keys are your own, and requests to the providers you configure are sent to your own provider accounts. Two platform-owned paths are the exception: Google embeddings for semantic search, and Cloudflare Workers AI (Jev) for lightweight content classification, both processed on Arch's own credentials. We're responsible for documenting the full provider chain and ensuring every provider available to EU customers has an active EU AI Act compliance program, an executed Data Processing Agreement, and Standard Contractual Clauses in place.
This page lists every provider, their compliance status as of our last review, and what each status means.
AI Provider Disclosures
The table below lists every AI provider that Arch Agent may invoke on your behalf. Providers are only called when you have configured an integration for them. Providers marked Context Format Only are not invoked via API - they are used solely to generate configuration files for your local AI coding tool.
Important: Providers with DPA Status Pending must not receive EU customer data until their Data Processing Agreements are executed.
Failed to load provider data: ["public-ai-providers","list"] data is undefined
| Provider | Models | Purpose / Surface | Data Processing | EU AI Act Compliance | DPA Status | Disclosure |
|---|
Compliance Status Key
| Status | Meaning |
|---|---|
Verified | Provider has an active EU AI Act compliance program and an executed Data Processing Agreement with Standard Contractual Clauses in place. Available to all customers including EU. |
In Progress | DPA negotiation or compliance assessment is ongoing. Provider must not receive EU customer data until DPA is executed. |
N/A | Provider is context-format-only - no API calls are made, no data is transmitted. No DPA required. |
Surface Definitions
| Surface | Description |
|---|---|
analysis | AI examines your context files and returns quality scores, rule violations, or insights |
improvement | AI rewrites or enriches your context files based on analysis findings |
generation | AI produces new context files, skills, or agents from templates or user prompts |
metadata | AI extracts structured metadata (tags, summaries) from existing files |
Agent Chat (Archat) | Conversational interface where AI answers questions and executes read/write tools against your workspace |
Frequently Asked Questions
Arch Agent does not instruct any AI provider to use your data for model training. Whether a provider uses API request data for training purposes depends on that provider's data processing agreement (DPA) and your organization's agreement with them. Enterprise API plans from Anthropic, OpenAI, and Google typically opt out of training by default. Review each provider's DPA for authoritative terms.
The provider that processes a specific request is the one your organization has configured for that workflow surface (analysis, improvement, generation, etc.). You can view and change your active provider integrations from the Settings → AI Providers page. Arch Agent will never silently fall back to a different provider - if your configured provider is unavailable, the request will fail with an explicit error.
To request deletion of data held by an AI provider, contact that provider directly using their data subject rights (DSR) process. Because Arch Agent sends requests using your organization's API key, you have a direct relationship with each provider under their terms of service. To delete data held within Arch Agent itself (context files, chat history, usage records), use the Settings → Data & Privacy page or contact support.
Within Arch Agent, content generated or improved by AI is surfaced with appropriate indicators in the UI (generation source metadata, AI suggestion labels). Arch Agent does not automatically embed machine-readable provenance markers into exported files. For EU AI Act Article 50 compliance, users are notified at the session level before AI features are activated.
Legal Disclaimer
This page is maintained in compliance with EU AI Act Article 50 transparency requirements. Users of Arch Agent's AI-powered features are notified at the point of first use and must acknowledge that their data will be processed by the third-party AI providers listed above before AI features are enabled.
AI providers are called exclusively using API keys supplied by your organization. Arch Agent does not share your data with providers under its own account.
Last updated: 2026-04-23