Trust centre · Pre-release

Trust centre

Where AxForge runs, what we keep, who touches traffic, and how to verify each claim. The summary is one table; the detail is one click away. What is not finished yet is labeled as such.

eu-se-1 · Stockholm eu-es-1 · Málaga More EU regions — in deployment

Get an API key Talk to an engineer Service status: pre-release — API keys are allocated from the waiting list; there is no self-serve signup.

The short version

AxForge in one table

Question	Answer
Who operates the service	AxForge — operations and inference hardware in Sweden. The contracting legal entity's registration details will be published on the legal notice before the first commercial contract.
Service status	Pre-release. API keys are allocated from the waiting list; there is no self-serve signup.
Where processing happens	eu-se-1 · Stockholm and eu-es-1 · Málaga. More EU regions — in deployment. Detail: data residency & sovereignty.
Outside-EEA processing	None — no outside-EEA processing, no outside-EEA failover. If all EEA capacity is unavailable, requests queue or fail — they are never routed outside the EEA.
Prompts & completions	Memory-only; discarded when the request completes. Never written to disk, logged or retained. Detail: retention & deletion.
Training on customer data	Never.
Served models	Model identity is returned on every API response. Catalogue: models; policy: model transparency.
Subprocessors	Two: Hetzner Online GmbH (Germany — EEA edge) and Atom9 (Sweden — console login). Full list: subprocessor register.
Security contact	hello@axforge.ai — one operational mailbox today for operational, privacy and security matters. Dedicated security@ and privacy@ aliases arrive at launch. How to report: incidents & reporting.

In detail

Every trust and legal page

Data residency & sovereignty Security Retention & deletion Incidents & reporting Subprocessor register Model transparency Privacy policy Terms of service Data Processing Agreement (draft) Acceptable use Cookies Legal notice Trust manifest (JSON)

Version 0.1 (launch draft) · Effective 2026-08-26

2026-08-26 — first published version of this page.