Regions & data handling

Your requests run in the EU, on hardware we own, and nothing you send is kept. This page states exactly where, on what, and what little metadata remains.

Regions

Region	Location	Status
eu-se-1	Stockholm	live
eu-es-1	Málaga	live
More EU regions		in deployment

Region pinning

Every key is pinned to a region. Send the region header with your requests; responses echo it back, so you can verify on every call where inference ran.

$ curl -sD - -o /dev/null https://api.axforge.ai/v1/chat/completions \
  -H "Authorization: Bearer $AXFORGE_API_KEY" \
  -H "x-axforge-region: eu-se-1" \
  -H "Content-Type: application/json" \
  -d '{"model": "qwen3.8-27b-nvfp4",
       "messages": [{"role": "user", "content": "ping"}]}'

HTTP/2 200
x-axforge-region: eu-se-1   # echoed — this is where your request ran

Transport

TLS 1.3, terminated in the EU.

Zero retention

Prompts and completions are processed in memory in the EU — not written to disk, not logged, not retained, and never used to train. This applies to every endpoint: chat, embeddings, images, audio. The commitment in full: axforge.ai/privacy.

What metadata is kept

Request metadata only — token counts, timestamps, and status — retained for billing and operations. Never the content.

Data	Kept?
Prompts, completions, images, audio	No — processed in memory only
Token counts	Yes — billing
Timestamps	Yes — billing and operations
Request status	Yes — operations

The hardware, by name

Inference runs on NVIDIA DGX Spark (GB10) systems that AxForge owns — not resold hyperscaler capacity. Details: DGX Spark and GB10.

Subprocessors

EU-hosted infrastructure; details in the trust centre. Inference itself runs on our own hardware.

Compliance posture

Infrastructure designed for EU data-residency and GDPR-sensitive workloads. Everything your assessment needs is stated plainly on this page: EU regions, zero retention, named hardware, EU-hosted infrastructure. More: GDPR compliance and the sovereignty page.