Security Certifications

How to read this page

A gateway's security story has layers, and mixing them up is how vendors overstate their posture. This page keeps the layers separate: the platform AI Reserve builds and operates, the Google Cloud infrastructure underneath it, the software we run inside our own environment, and the upstream providers that perform model inference under their own terms. Each row states who holds the certification.

• ✓ Held — the named organization holds the certification or attestation, per its own published documentation as of the review date.
• In-Process — an examination or recertification is underway per the named organization; no report is claimed until one is issued.
• N/A — not held, not published, or not verified for this matrix as of the review date. It is not a judgment of the organization's security.
• Not published — GDPR column only: we found no GDPR compliance statement or Data Processing Addendum on the organization's public pages as of the review date. It is not a finding about the organization's compliance.

Certification matrix

Frameworks shown: SOC 2 (Type II unless a note or footnote states otherwise), ISO/IEC 27001 (information security), ISO/IEC 42001 (AI management), ISO/IEC 27701 (privacy), and HIPAA (a BAA path or configurable eligible workloads — not a certification; a BAA on offer implies the service is HIPAA-eligible). GDPR is a regulation, not a certification, so the GDPR column shows no certificate. It shows whether the organization publishes a GDPR compliance statement and a Data Processing Addendum: ✓ means we found them published and linked from its trust, legal, or compliance page (each link is recorded in footnote 12); Not published means we found neither; In-Process means the organization itself states that its GDPR work is in progress; N/A marks an organization that never processes customer data as a vendor. Our own row states our position in words, with the evidence in footnote 11, because no GDPR certification scheme exists for us to hold. The last column links to each organization's own trust or compliance page. CSA STAR is not shown as a column — no default-routing provider in our registry records it; Google Cloud's and Alibaba Cloud's CSA STAR registrations are recorded in footnotes 2 and 9.

This page tracks certifications only. The authoritative per-provider data-handling matrix — training posture, retention window, processing region, and DPA role — is the Provider Data Handling page. Media-generation, dedicated GPU-deploy, and data-endpoint routes (fal.ai, Hugging Face Inference Endpoints, WaveSpeedAI, MuleRouter, monid.ai) are documented there as well; no formal attestations for them have been verified into our reviewed registry, so they carry no marks here.

Consent-gated providers

The providers below receive traffic only as the named consent gate permits — the same gates documented in the data-handling matrix. Training-data and data-retention gates are opt-in: those providers are locked for every organization until an administrator enables them. The PRC-server gate blocks traffic whenever it is disabled and is created disabled for every new organization; organizations that predate the gate keep their prior setting until an administrator changes it. They are listed separately so their certifications are never read as part of the default routing posture.

Additional consent- and allowlist-gated media providers (WaveSpeedAI, MuleRouter) and route-dependent serving are documented on the Provider Data Handling page.

Our own program, stated honestly

AI Reserve's SOC 2 Type II examination is in progress — Type I first, with the Type II observation window to follow — and no report has been issued yet, so we do not claim our own certification anywhere. What already operates today: the control set is implemented and documented, compliance automation (Vanta) runs continuous checks against the live environment, and our build pipeline enforces the public claims registries on every change — a page like this one cannot drift from what the code actually does without failing CI.

GDPR. We comply with the GDPR and the UK GDPR as a processor of the personal data our customers send through the platform. GDPR is a regulation we follow, not a certification we hold: no GDPR certification scheme exists for us to hold, and we do not claim one. The commitments are in our published Data Processing Agreement: Standard Contractual Clauses and the UK Addendum for processing in the United States, EU and UK representatives under Article 27, incident notice within 72 hours, a subprocessor list with a thirty-day objection window, and deletion on verified request and at the end of services. Our Article 27 representation is verified by the provider that supplies it: GDPRLocal completed its due-diligence review of Audacity Advisory Corp and granted Article 27 verified status on October 13, 2026 — a representation-provider verification, not a third-party audit. We keep records of processing under Article 30(2). To exercise your data subject rights, contact the organization that holds your account; if a request reaches us directly we notify that organization and help it respond, as the DPA provides. Requests to us go to security@aireserve.com or through our representatives' request portals for the EU and the UK. The evidence behind this statement is listed in footnote 11.

Once a report is issued, our Data Processing Agreement provides that a current report is accepted in lieu of an audit of covered controls; until then we complete reasonable written security questionnaires. Reports, questionnaires, and documentation requests are handled through the Trust Center or your AI Reserve point of contact.

Sources & footnotes

Provider certifications are reviewed against each provider's published documentation (linked per row). Where a provider has a profile in our provider-trust registry — the same registry that powers the data-handling matrix and the in-product provider trust panels — per-provider review dates are maintained there; rows without a registry profile (OpenRouter, ByteDance) state their basis in the footnotes. This page is regenerated to the privacy site with every production deploy.

1. AI Reserve's SOC 2 Type II examination is in progress (Type I first, then the Type II observation window); no report has been issued and no completion date is promised here. Our ISO 27001 readiness program is in progress; we have not yet engaged a certification body and do not claim ISO 27001 certification. The infrastructure layer's ISO 27001 is Google's (row below). See the overview's compliance section.
2. Google Cloud's certifications for the infrastructure layer — not AI Reserve's own. Google Cloud holds SOC 1/2/3 and ISO/IEC 27001, 27017, 27018, and 27701 for in-scope services and offers HIPAA BAAs (our registry records the SOC attestations without pinning the report type — footnote 5); Google additionally documents further programs (including CSA STAR and FedRAMP High for applicable services) on its compliance offerings page — those are not marked in the matrix because our reviewed registry does not yet track them: cloud.google.com/security/compliance/offerings. All AI Reserve production infrastructure runs in Google Cloud region us-east4; physical security of the facilities is delegated to Google and evidenced by these certifications. AI Reserve personnel have no physical access to any data center.
3. LiteLLM is the open-source routing engine inside our gateway. We self-host it inside our own Google Cloud project: BerriAI (the maintainer) never receives or processes customer data, so this row is a software supply-chain attestation, not a data-processor certification. LiteLLM's updated SOC 2 Type II report was issued on September 8, 2026 (report announcement), completing the recertification with Vanta and an independent auditor announced March 2026 (recertification announcement); the ISO 27001 recertification from that announcement remains in process. Status per its trust center at trust.litellm.ai.
4. Anthropic holds SOC 2 Type I and Type II; HIPAA is configurable for eligible workloads per Anthropic's documentation.
5. AWS and Google Cloud hold SOC 1, SOC 2, and SOC 3, plus ISO/IEC 27017 and 27018 (cloud and PII controls) beyond the columns shown. Bedrock and Vertex AI are HIPAA-eligible services with BAA paths via AWS and Google Cloud respectively; processing is pinned to our configured regions. Our provider registry records these SOC attestations without pinning the report type, so the checks on these rows are not a Type II claim by us — the type designation is whatever the vendor's current report states. Gemini API paid-tier prompts and responses are processed under Google's Data Processing Addendum for Products Where Google is a Data Processor, per the linked Gemini API Additional Terms; the marks on that row are Google's platform attestations as recorded in our registry, which tracks the Gemini paid tier alongside Vertex AI.
6. xAI documents a BAA inquiry path but not a standing HIPAA-eligible offering, per its enterprise security FAQ.
7. DeepInfra's SOC 2 attestation is Type I, per its trust center.
8. OpenRouter is a routing aggregator on our default paths for a small set of models; no formal security attestation for it has been verified into our reviewed registry as of the review date. Its no-training posture, metadata-only logging default, and per-route downstream endpoints are documented on the data-handling page.
9. Alibaba Cloud's platform certification portfolio (SOC 2, ISO 27001/17/18/701, CSA STAR) per its trust center; our registry records the SOC 2 attestation without pinning the report type. The operator is under PRC jurisdiction, which is why the PRC-server consent gate applies regardless of certifications.
10. No formal security attestations verified for this matrix as of the review date. Traffic reaches these providers only as the named consent gate permits — see the section introduction for how each gate defaults.
11. GDPR is a regulation, not a certification, so this cell states our position rather than a certificate. AI Reserve complies with the GDPR and the UK GDPR as a processor of the personal data customers send through the platform, and as an independent controller of the limited service data the DPA describes. This is our own assessment: no GDPR certification scheme under Article 42 has been issued to us, and none is claimed. The evidence is published:
    • The Data Processing Agreement sets the processor role and the Article 28 terms (§1, §2, Annex 1).
    • Annex 2 of the DPA places processing in the United States under the EU Standard Contractual Clauses (Module Two or Module Three), the UK Addendum, and Swiss FADP adaptations, with transfer impact assessments (Annex 2, §7).
    • Article 27 representatives are named in Annex 1: Instant EU GDPR Representative Ltd for the EU, GDPRLocal Ltd. for the UK. On October 13, 2026 GDPRLocal completed its due-diligence review of our representation documents and granted Audacity Advisory Corp its Article 27 verified status (a representation-provider verification, not a GDPR certification under Article 42).
    • Records of processing activities are maintained under Article 30(2).
    • Data subject requests follow the DPA's rules (§4 assistance to the customer, §8.1 verified requests). Requests that reach us directly are routed to the customer, and our representatives operate request portals for the EU and the UK.
    • Security incidents affecting personal data are notified without undue delay and in any event within 72 hours of our becoming aware (§3.3).
    • The subprocessor list is published with a thirty-day objection window (§6.3).
    • Stored customer content is deleted within fourteen days of a verified request, and returned or deleted at the end of services (§8).
12. GDPR column sources, as of the review date. A check means we located the organization's own GDPR compliance statement or Data Processing Addendum at the page linked here. Not published means we found neither on the organization's public legal, trust, or privacy pages; it is not a finding about that organization's compliance. Trust centers that render only in a browser were read where accessible; otherwise the organization's public legal page is the source.
    • Google Cloud (infrastructure and Vertex AI): cloud.google.com/privacy/gdpr.
    • ElevenLabs: data-residency page ("Our platform and practices are designed to align with applicable GDPR requirements"; EU data-residency environment available to enterprise customers).
    • Google Gemini API (paid tier): the Google Cloud Data Processing Addendum, per the Gemini API Additional Terms.
    • OpenAI: trust.openai.com (GDPR listed under compliance; DPA under legal documents).
    • Anthropic: Data Processing Addendum.
    • AWS Bedrock: AWS GDPR Center.
    • xAI: Data Processing Addendum (published under the SpaceXAI name, effective September 22, 2026).
    • Perplexity: Data Processing Addendum.
    • Mistral AI: Data Processing Addendum.
    • Together AI: not published. We located no DPA or GDPR statement on together.ai; its privacy policy describes EEA and UK transfers under Standard Contractual Clauses, and its trust center could not be read for this review.
    • Fireworks AI: Data Processing Addendum.
    • DeepInfra: In-Process. Our provider-trust registry records DeepInfra's trust center as stating that its GDPR work is in progress (reviewed September 13, 2026); no DPA located.
    • Novita AI: not published. We located no DPA or GDPR statement on novita.ai, and its trust center could not be read for this review.
    • Baseten: Data Processing Addendum.
    • OpenRouter: DPA published as Exhibit A of its enterprise terms of service and incorporated by reference in its standard terms; signed copies are offered on its enterprise tier.
    • Alibaba Cloud Model Studio: GDPR page and Data Processing Addendum.
    • NVIDIA (hosted NIM catalog): not published for this service. NVIDIA publishes a Cloud Services Data Processing Addendum, but the NIM API trial terms we route under do not incorporate it.
    • DeepSeek: not published. Its privacy policy has an EEA, Swiss, and UK section; no DPA located.
    • Moonshot AI: not published. Its platform privacy policy has an EEA and UK section; no DPA located.
    • ByteDance (BytePlus ModelArk): BytePlus Data Processing Addendum.
    • Higgsfield: not published. Its privacy policy has a GDPR section naming an EU and a UK representative, and its API terms refer to a DPA, but no DPA text is published.
    • Video Rebirth (BACH), Tensormesh, StreamLake, and GMI Cloud: not published. We located no DPA or GDPR statement on their public sites.
    • Venice.ai: not published. Its privacy policy has a European privacy-rights section and an international-transfers statement (U.S. hosting); no DPA located.
13. ElevenLabs — its data-residency page states "ElevenLabs maintains SOC2 certification" and offers HIPAA Business Associate Agreements to qualifying healthcare enterprises only; the report itself is behind the compliance center and was not independently reviewed by AI Reserve, and no BAA covers our account, so the HIPAA cell is N/A. Reviewed October 11, 2026.

Questions, or need a report under NDA: contact your AI Reserve point of contact, security@aireserve.com, or the Trust Center.