Compliance

Compliance status and controls, on the record.

nRouter's SOC 2 Type II audit is in progress — it is not yet certified. Today it operates SOC 2-aligned security, availability and confidentiality controls: encryption, access control, change management, audit logging and tenant isolation. Its infrastructure substrate, Microsoft Azure and managed database services, is SOC 2 Type II certified, and a Data Processing Addendum is available for signature.

What we ship per framework.

The controls and agreements supporting each compliance program.

SOC 2 Type II (audit in progress).

SOC 2-aligned controls run continuously in production while the Type II observation period is underway.

  • AES-256 encryption at rest and TLS 1.2+ with HSTS in transit
  • Postgres Row-Level Security on every tenant table
  • Append-only audit trail with actor, IP, and diff on admin actions
Controls walkthrough

GDPR.

EU data protection terms, cross-border transfer mechanisms, and zero inference payload retention.

  • Published Data Processing Agreement with Standard Contractual Clauses
  • Data-subject access, erasure, portability, and restriction rights
  • Prompts and completions are never persisted to disk
Read the DPA

HIPAA.

Healthcare workloads supported with a Business Associate Agreement and in-path PII redaction.

  • Business Associate Agreement available for Enterprise workloads
  • Output PII redaction on buffered responses plus optional pre-call rules
  • Audit logging across administrative and key management events
Request a BAA

PCI DSS (delegated to Stripe).

Payment processing is delegated to Stripe, a PCI DSS Level 1 certified service provider.

  • Zero raw cardholder data stored or processed on nRouter servers
  • Client-side tokenization via Stripe Elements on every checkout
  • Webhook signature verification and idempotency on Stripe events
How payments work

Data protection controls.

Measure-by-measure controls enforced across the platform.

Encryption in transit and at rest.

TLS 1.2+ (HSTS preloaded) for all network traffic and AES-256 across Postgres, Redis, and object storage.

Database tenant isolation.

Row-Level Security is enabled on every tenant table so queries are isolated to a single organization.

Key hashing and authentication.

Virtual keys are SHA-256 hashed with plaintext shown once. Dashboard sessions use JWT-based authentication.

Reserve and settle billing.

Credits are reserved prior to dispatch and settled atomically at the served model’s exact list price.

Inference payload retention.

Zero retention by default: prompt and completion text is processed in memory and never written to disk.

Operational and financial retention.

Request metadata logs auto-purge after 7 to 30 days. Financial billing records are retained for 7 years.