Trust Center
Security posture, framework status, and legal documents.
Current framework status, data-protection controls, and self-serve legal agreements in one place.
Framework posture.
Status comes from one source of truth: active, in progress, or available on request.
SOC 2 Type II
SOC 2-aligned security, availability, and confidentiality controls. Formal Type II audit in progress.In progressISO/IEC 27001
Information security practices aligned to ISO/IEC 27001 Annex A controls. Certification planned.In progressGDPR
EU GDPR compliant with a Data Processing Agreement, Standard Contractual Clauses, and EU residency.ActiveHIPAA
HIPAA-eligible workloads with a Business Associate Agreement and in-path PII redaction.AvailablePCI DSS
All payments processed by Stripe (PCI DSS Level 1). Card numbers never reach our servers.AvailableData residency
US East (Virginia) by default, with EU, UK, Canada, Australia, Singapore, and India on request.Active
Core security posture.
Enforced across every request and tenant account.
Tenant isolation at the database.
Postgres Row-Level Security scopes every tenant table by organization so cross-tenant reads return zero rows.
Zero payload retention.
Prompts and completions pass through memory for routing and guardrails and are never written to disk.
Virtual keys for inference.
Customer LLM calls authenticate with SHA-256 hashed virtual keys carrying per-key budgets and rate limits.
Contractual uptime target.
Backed by managed Azure Container Apps and managed Postgres with service credits defined in the SLA.
99.9%
Self-serve legal documents.
Published directly with no gate or sales call.
Data Processing Agreement
Standard DPA covering EU/EEA processing, Standard Contractual Clauses, and the security exhibit./legal/dpaService Level Agreement
99.9% uptime target with service credits for missed minutes, plus custom Enterprise SLA terms./legal/slaSubprocessor list
The third parties involved in delivering nRouter, with 30-day advance notice before additions./legal/subprocessorsAcceptable Use Policy
What you can build on nRouter, what is not permitted, and how policy violations are handled./legal/aupPrivacy Policy
What operational data we collect, why we collect it, retention windows, and data-subject rights./privacyTerms of Service
The master agreement governing self-serve pay-as-you-go and organization accounts on nRouter./terms
Go deeper.
Engineering architecture, framework scope, live health, and contact channels.
Security architecture
Request flow, Postgres Row-Level Security, virtual keys, guardrails, and reserve-and-settle credit safety.Compliance frameworks
Framework-by-framework scope, status, and the data-protection control catalog for auditors.Service status
Live component health across the gateway, dashboard, authentication, billing, and model providers.Press room
Official company announcements, security and compliance milestones, and verified media assets.Security team
Vulnerability disclosures, vendor security questionnaires, and controls walkthrough requests.security@nrouter.ai · < 48 hoursLegal team
Counter-signed DPAs, Business Associate Agreements, custom MSAs, and subprocessor questions.legal@nrouter.ai · < 2 business days
FAQs
Is nRouter SOC 2 certified?
Not yet — and we will not claim otherwise. nRouter implements SOC 2-aligned controls today: encryption, access control, audit logging, change management, and tenant isolation, enforced continuously by tests and Row-Level Security rather than periodic audit cycles. Our underlying cloud infrastructure (Microsoft Azure) and managed database services are independently SOC 2 Type II certified. A formal nRouter-level SOC 2 Type II audit is in progress; until it completes, customers who need a formal report can request a controls walkthrough or a completed vendor questionnaire from security@nrouter.ai.
Does nRouter store or retain LLM prompts and completions?
No. nRouter operates under a strict zero data retention policy for LLM inference payloads. Prompts and completions pass through volatile memory for routing, guardrails, and provider streaming, and are never written to disk, persistent databases, or object storage. Only operational metadata (model, tokens, cost, latency, timestamps) is recorded for billing and observability.
How does nRouter handle HIPAA compliance and PHI?
nRouter supports HIPAA-eligible workloads on Enterprise. We execute Business Associate Agreements (BAAs), and when an input redaction rule is enabled, PII and PHI are redacted in-path before payloads reach upstream model providers.
How do I get a DPA, SCCs, or your subprocessor list?
The DPA, SCCs, AUP, and subprocessor list are published and linked directly from this page with no gate and no sales call. Request a counter-signed copy of the DPA from legal@nrouter.ai if your procurement process requires an executed document.
Can you complete our security questionnaire?
Yes. Email your CAIQ, SIG, or custom questionnaire to security@nrouter.ai or legal@nrouter.ai.
Where is customer data stored, and can I pin a region?
All customer data lives in managed Postgres with at-rest encryption, replicated within a single region. United States is the default footprint. EU residency is available on Enterprise; the UK, Canada, Australia, Singapore, and India are available on request on Enterprise for residency-sensitive workloads. We do not move tenant data across regions without an explicit migration request.
What happens if a virtual key leaks?
Virtual keys are tenant-scoped, rate-limited, budget-capped, and observable. Revocation is immediate from the dashboard or API, and cache invalidation propagates within seconds. Keys are hashed in the database. The plaintext is shown exactly once. The blast radius of a leak is the budget on that single key, not your account.
How do I report a security vulnerability?
Email security@nrouter.ai with details. We acknowledge in < 48 hours and follow coordinated disclosure — crediting reporters in our changelog when permitted.