Hosting and processors
Where Azta stores data, where its models run and where web searches go.
Where data is stored
The privacy policy lists AWS (cloud infrastructure and hosting) in Frankfurt, eu-central-1, and Supabase (database, authentication and file storage) in Frankfurt. The production infrastructure configuration points the database pooler at aws-0-eu-central-1.pooler.supabase.com, an eu-central-1 host.
Where models run and searches go
azta-agentic-core runs its models on OpenRouter's EU route (eu.openrouter.ai, zero data retention), with AWS Bedrock in eu-central-1 as the outage fallback, and sends web searches to Exa (api.exa.ai, US).
The direct Anthropic API is not a processor: no agent uses it in production, as of the production build checked on 2026-10-28.
Processors
The first five rows apply to the API and to the MCP server. The last three apply to the MCP server only.
| Processor | What it does | Where | EU | Applies to |
|---|---|---|---|---|
| AWS | Hosts the application and the engine | Frankfurt, eu-central-1 | Yes | API, MCP |
| Supabase | Database, authentication and file storage | Frankfurt | Yes | API, MCP |
| OpenRouter, via eu.openrouter.ai | Runs the language models, zero data retention | EU route | Yes, per the privacy policy. OpenRouter, Inc. is a US company | API, MCP |
| AWS Bedrock | Runs the models if the primary route has an outage | eu-central-1 | Yes | API, MCP |
| Exa (api.exa.ai) | Web search, when web search is on for your key or account | United States | No, Exa is a US company and requests go outside the EU | API, MCP |
| OpenRouter, global route (openrouter.ai) | Writes the chat title on an MCP turn, with accountiq's own chat-title model | Global route | No, not on the EU route | MCP only |
| Cégadat (api.cegadatapi.hu) | Company lookup, when the user has company lookup on | Not stated | Not established here; see the trust center | MCP only |
| The MCP host you connect | The client you authorize (OpenAI, Anthropic or another vendor) receives the tool results | Set by that vendor | Depends on the vendor; most client operators are outside the EU | MCP only |
Exa processes your request outside the EU when a run uses web search. Web search is switched on for API keys once the account is unlocked.
On an MCP turn, accountiq's own chat-title model adds "accountiq's chat-title model on OpenRouter's global route (openrouter.ai, not EU)". The REST API has no title model.
Binding text
The privacy policy and the trust center hold the binding list of processors and transfer safeguards.