Tinfoil — Inference Providers on Stav

Compliance posture

Jurisdiction

US · United States

Data residency

UNKNOWN

CLOUD Act / FISA 702

Exposed

Stav sovereignty level

L0 — Under third-country jurisdiction

Sovereignty ladder · how the level was reached

L0Foreign jurisdictionIndicative

Tinfoil, Inc. is a US-incorporated, US-owned, US-controlled confidential-computing inference provider whose serving infrastructure runs entirely on US hyperscalers (AWS, Cloudflare, GPU cloud) with no EU/EEA region — it cannot reach even L1 on the Sovereignty Ladder. Its genuinely novel enclave architecture (AMD SEV-SNP / Intel TDX + NVIDIA confidential GPUs) creates a substantive technical barrier making AI inference content cryptographically inaccessible even under US legal compulsion, which elevates l2.anti_coercion_measures to partial rather than unmet, but the operator remains a CLOUD Act-subject US entity and no criterion for L1 (data or infrastructure in the EU/EEA) is met. The single blocker above L0 is the entirety of L1: both data residency and serving infrastructure are firmly outside the EU/EEA.

3 criteria from L1: Customer data in the Union, Infrastructure in the Union, No coerced vulnerability silence.

Stav's own assessment against criterion registry 4.0 — indicative, not an official recognition, which only a national authority can confer. Criteria follow the proposed Cloud and AI Development Act and are expected to change. “Union” reads as EU/EEA at every rung.

Verified 9/4/2026About the ladder →

Stav's assessment · serving-side

61/100

Elevated risk

Tinfoil is a US-incorporated operator (Tinfoil, Inc., San Francisco) serving inference exclusively from US-hosted infrastructure (AWS, Cloudflare, Vercel) with no EU/EEA region option, so the serving-residency signal is weak by Stav's standard. Legal exposure is nominally high given US jurisdiction and US-hyperscaler subprocessors, but Tinfoil's core differentiator — hardware-isolated secure enclaves with client-verifiable attestation designed so neither Tinfoil nor its cloud providers nor government requesters can access plaintext prompts/outputs — is a genuine mitigant that Stav credits, without treating it as equivalent to EEA jurisdiction. The strongest dimensions are serving retention (no post-response retention, no training on API content) and security posture (current SOC 2 Type II plus enclave attestation), while the weakest is serving residency, compounded by a contractual posture that leaves enterprise-grade liability, DPA/SCC execution, and regulated-data handling to a separately negotiated agreement rather than standard terms. On balance this composite lands in elevated-risk territory: the confidential-computing architecture is a meaningful technical safeguard, but the absence of EEA infrastructure and the US legal seat mean Stav should treat Tinfoil as routed-only pending a signed DPA/SCC and, for regulated workloads, an explicit derogation rather than default sovereign serving.

Serving residency

All disclosed hosting/CDN subprocessors (AWS, Cloudflare, Vercel) are US-based with no documented EU/EEA inference region, so serving runs outside the EEA by default.

Certifications & legal documents

SOC 2 Type II ↗

Security, availability, and confidentiality · Current

Terms of serviceView ↗

Privacy policyView ↗

Data processing agreement (DPA)not published

Sub-processor listView ↗

Compiled by Stav from the provider's published documentation. Last verified 9/4/2026. Reflects what the provider states — not a Stav guarantee or regulatory determination. Confirm against the provider's own pages before contracting.