Security & trust
Compliance without compromise.
Our security posture, regulatory frameworks, and transparency guarantees — wired into the router, not the marketing page. The cryptographic receipts come on every response, so you don’t have to ask twice.
Trust
Three contracts your data never breaks.
Each guarantee is verifiable from the response of every call — not a claim on a slide.
Your data does not leave your region.
Every call is auditable.
Compliance
Three honest tiers.
Live at the router, paperwork in flight, or gated on contracts — labeled plainly. We don’t claim a certification we haven’t shipped; what’s dated below is real.
| Framework | Region | What we ship | Status |
|---|---|---|---|
| nFADP | Switzerland | CH-resident PHI inference via Infomaniak and Azure (CH); processor agreements under nFADP. | Live |
| GDPR | European Union | EU-domiciled PHI inference via Scaleway and Azure (EU); DPA available on request. | Live |
| UK GDPR | United Kingdom | EU adequacy honored; processing pinned to EU endpoints. | Live |
| HIPAA BAA | United States | US-resident PHI inference via Azure under a signed Microsoft BAA. (Infomaniak / Scaleway are nFADP/GDPR, not HIPAA.) | Live |
| Edge data-class | phi-cloud router | PHI vs general enforced per request; no payload logging, no application database. | Live |
| SOC 2 Type I | phi-cloud platform | Auditor engaged; observation window begins Q3. Type II to follow. | In progress |
| LGPD | Brazil + LATAM | Privacy policy and DPO appointment in progress; US endpoints under SCCs in the interim. | In progress |
| PIPL | China (PRC) | PRC-domiciled routing requires a local entity + contracts with Alibaba/Baidu/Zhipu. | Roadmap |
| UAE PDPL | Middle East | Partnership with G42 Inception for UAE-resident PHI inference under discussion. | Roadmap |
| DPDP | India | Domestic provider routing and cross-border consent flow on the roadmap. | Roadmap |
| APPI · PIPA · PDPA | Japan · Korea · Singapore | Regional endpoints pending vendor availability in Tokyo, Seoul, Singapore. | Roadmap |
Live = shipping today, verifiable at the router. In progress = dated milestones. Roadmap = needs a local entity or partner contract — talk to us if your deployment depends on one.
Transparency
Three things a curl call already proves.
No vendor portal, no support ticket. The contract surface is the response itself.
Open catalog
Per-call audit
Per-token price
One curl, five audit headers.
Make any call. Inspect the response headers. The resolved (provider, region, model) is right there — no log dive, no support ticket.
curl -i https://phi-cloud.com/api/v1/chat/completions \
-H "Authorization: Bearer phi_live_…" \
-H "X-PHI: true" \
-H "X-Region: CH" \
-d '{"model":"auto","messages":[{"role":"user","content":"hi"}]}'HTTP/2 200
x-phi-routed: gemma-4-31b/CH/phi
x-phi-tier: phi
x-phi-attempts: 1
x-phi-cost-micro: 247
x-request-id: 9c2b…Ready to send the questionnaire?
Spin up a key — the posture above arrives unchanged.
The routing posture is enforced from the first call. Nothing here is a slide; it’s the response of every request.
Free to test · Prepaid credits, no subscription · No data retained