Prizmal

Trust

Your data is not ours

Runs in Prizmal's environment or yours. One key, one ledger, one kill switch. What follows is not a values statement; it is how the system is built, and each article is a contract term.

The doctrine

Five articles. Each one falsifiable. Referenced from the Terms.

  • D-01
    Non-usage

    We do not train on your data. Not our models, not anyone's. No exceptions, no toggles, no anonymized carve-outs.

  • D-02
    Retention

    We do not retain beyond your window. Retention clocks are yours to set; expiry is enforced, not scheduled.

  • D-03
    Access

    We do not look. Human access to customer content requires your authorization, is time-boxed, and is itself written to the ledger.

  • D-04
    Context

    Context never crosses tenants. Escalation hands off the minimum reasoning context required, on your keys, under your account. Caches are tenant-keyed; a token computed for you is never served to anyone else.

  • D-05
    Departure

    You leave with everything. Ledger, configuration, and content export on demand; departure is a base-URL swap.

Chain of custody

Who holds it, for how long, under whose key.

C-01
Prompt
Holder:
Customer
Window:
Origin
Key:
Customer
C-02
PrizmalSwitch
Holder:
Prizmal, transit
Window:
TLS only, no persistence
Key:
Customer
C-03
Model class
Holder:
Open: our env or yours. Frontier: your account
Window:
Per request
Key:
Customer
C-04
Completion
Holder:
Customer
Window:
Returned, not stored by us
Key:
Customer
C-05
Ledger
Holder:
Customer-readable
Window:
Customer-configured
Key:
Tenant-keyed

Metadata ledger is immutable. Content retention is customer-configured, default minimal. Prompts are never stored by default.

The escalation clause

When the doubt gate routes a request to a frontier provider, the minimum reasoning context for that request crosses the boundary, under your frontier credentials, against your account. Preserving your context across the open fleet is our job. Sharing it is not a feature we offer anyone, including ourselves.

Crosses
  • Minimum reasoning context for this request
  • Your frontier credentials
  • Your account, your invoice
Never crosses
  • Other tenants' context
  • Your prior requests beyond this one
  • Cache entries from any tenant

Isolation postures

Choose per workload, not per contract. Warden policy can pin a data class to a posture.

P-4
Shared
Multi-tenant cloud. Tenant-keyed encryption; isolation enforced at storage and cache layers.
P-3
Dedicated
Single-tenant cloud. Dedicated control plane and storage within the Prizmal environment.
P-2
Your VPC
Customer network. Prizmal control plane operates inside the customer VPC; data path stays in the customer account.
P-1
Sovereign
On-prem. Air-gappable. Customer jurisdiction. Both control plane and data path customer-owned.

Compliance posture

Status, not aspiration.

SSO / SCIM
Identity federation, role provisioning, lifecycle automation. Shipped, via Warden.
EU AI Act
Risk tier mapping, transparency obligations, log retention.
ISO 27001 / 27701 / 42001
Information security, privacy information management, and AI management system control mappings.
SOC 2 Type II
Security, availability, and confidentiality controls. Program underway with an independent auditor.
Sovereign / on-prem
Self-hosted control plane, customer-owned datapath. Deployment models: shared, dedicated, VPC, sovereign.
Access and verification
  • Least-privilege roles, scoped API keys, just-in-time elevation with expiry
  • Administrative actions written to the customer-readable ledger
  • Immutable ledger export on demand; controls matrix on request
  • Independent penetration test: 2026 Q3 target

Coordinated disclosure to security@prizmal.ai. Acknowledgment within 48 hours. Safe harbor for good-faith research. The full subprocessor list ships from the SOC 2 program package and is shared under NDA with active customers and audit prospects.

This page is maintained by Prizmal to answer common security and privacy questions. It describes current practices and enabled controls. It is not an independent certification.

Proof over posture

The R/E Audit runs in shadow mode, read-only, reversible at every step. See the controls on your own traffic.

See Warden