Loading the catalogue…
Loading the catalogue…
Compliance posture
Sovereignty ladder · how the level was reached
Stav's assessment · serving-side
xAI is a US-incorporated operator subject to CLOUD Act jurisdiction, serving primarily from a global-routing endpoint with regional (including eu-west-1) options that fall short of a guaranteed EEA-resident default. The composite lands in high-risk territory driven by weak legal_exposure (US parent, no EEA insulation) and serving_residency (no default EEA-bound processing), compounded by a security_posture drag from two distinct 2025 security incidents — a share-link misconfiguration that exposed 300,000–370,000 private conversations (August 2025) and a leaked API key that remained valid for two months and revealed a documented weak vulnerability-disclosure process (May 2025) — despite holding a current but NDA-gated SOC 2 Type II certification. Serving_retention and contractual_posture are comparatively stronger — 30-day encrypted default retention with no training-on-data, plus a published DPA/SCC framework and subprocessor list — but both still require enterprise negotiation (ZDR, BAA) to reach a fully protective posture, and the ongoing X/SpaceX corporate entanglement adds counterparty uncertainty. Given the combination of US jurisdiction, unresolved privacy incidents, and non-default EEA residency, Stav's operational verdict is that xAI does not currently support sovereign EEA serving and should be treated as routed-only, pending a signed EEA-specific DPA, verified ZDR configuration, and independent confirmation of regional data residency guarantees.
xAI offers regional API endpoints (eu-west-1) but defaults to a global auto-routing endpoint, and guaranteed EEA at-rest data residency requires a separate sales engagement rather than being a platform default.
Certifications & legal documents
Endpoints served · 7
xAI is a US-incorporated operator with explicit CLOUD Act exposure and no EEA legal entity or sub-processor insulation identified in the research.
Default retention is 30 days encrypted at rest with no training on prompts, but strict Zero Data Retention requires enterprise negotiation and disables stateful API features, keeping the default posture short of a true opt-out standard.
A single current SOC 2 Type II cert exists but is NDA-gated, and a 2025 misconfigured share-link feature exposed 300k+ private conversations alongside a documented weak vulnerability-disclosure process, indicating unresolved security maturity gaps.
xAI publishes a DPA, SCC framework, and subprocessor list, and offers a gated BAA, but the evolving X/SpaceX corporate structure and NDA-gated compliance evidence leave the contracting counterparty and audit rights only partially clear.
Risk assessment
In 2025 an xAI developer leaked a live API key in a public GitHub repo that remained valid for two months and granted access to unreleased/private internal models; xAI's disclosure process lacked a security.txt, redirected a responsible-disclosure report to its bug-bounty intake, and gave no follow-up updates to the reporting researchers, indicating gaps in incident-response maturity. source ↗
SECURITYxAI publishes regional API endpoints (eu-west-1, us-east-1, us-west-2) and a global default endpoint that auto-routes requests, but guaranteed at-rest regional data residency requires a separate sales engagement rather than being a default platform guarantee. source ↗
DATA_RESIDENCYBy default, all API requests and responses are stored encrypted at rest for 30 days for abuse-monitoring purposes; strict Zero Data Retention is available but disables stateful features (Responses API, Files/Collections, Batch API), creating a functionality/privacy trade-off for regulated customers. source ↗
SERVING_RETENTIONFull SOC 2 Type II report detail and up-to-date certification/data-governance evidence are gated behind an NDA in xAI's Trust Center, limiting independent procurement/security-team verification without a signed agreement. source ↗
SECURITYxAI has only signed the Safety and Security chapter of the EU AI Act GPAI Code of Practice, not the full code, indicating partial rather than complete engagement with EU AI Act governance commitments. source ↗
GOVERNANCEThird-party uptime monitors have logged dozens of Grok/xAI outages over recent months, including a documented history of periodic 'Temporarily Unavailable' incidents through 2026, some occurring without prompt acknowledgement on xAI's own status page. source ↗
RESILIENCEReporting references an ongoing SpaceX–xAI corporate merger alongside the earlier xAI/X (Twitter) combination, indicating an evolving and complex corporate/ownership structure that customers should track for changes in the contracting entity and cross-entity data flows. source ↗
GOVERNANCESafeguards
xAI states it is SOC 2 Type II compliant for its API service. source ↗
xAI does not train on API request/response data by default, and default retention is capped at 30 days with automatic deletion. source ↗
Enterprise customers can enable Zero Data Retention (ZDR) for stricter data handling, at the cost of disabling stateful API features. source ↗
xAI publishes a Data Processing Addendum that defines Standard Contractual Clauses and links to a public subprocessor list. source ↗
xAI offers a Business Associate Agreement (BAA) request process to enable HIPAA-relevant use of its API, gated behind a sales/request form. source ↗
xAI provides regional API endpoints (eu-west-1, us-east-1, us-west-2) in addition to a global routing endpoint. source ↗
Team admins can view an audit log of user interactions via the API console. source ↗
Privacy-policy issues
Public share-link indexing exposed hundreds of thousands of private conversations source ↗
In August 2025, Grok's chat 'share' feature generated publicly indexable URLs without adequate warning, resulting in an estimated 300,000–370,000 conversations (including sensitive medical, personal, and credential data) being crawled and indexed by Google, Bing, and DuckDuckGo.
NDA-gated compliance transparency source ↗
Detailed SOC 2 Type II reports and current certification/data-governance documentation are only available to customers who sign an NDA to access xAI's Trust Center, limiting pre-contract due diligence.
No public security.txt / weak vulnerability-disclosure routing source ↗
xAI's main domain lacks a standard security.txt disclosure contact, and a 2025 responsible-disclosure report was redirected to a bug-bounty intake instead of a dedicated incident-response channel, delaying remediation communication.