Trust

Trust & Security Review Center

Understand exactly how Privian handles prompts, credentials, providers, retention, and data flow.

Everything on this page is grounded in the current implementation. No invented certifications, no invented customers, no invented metrics.

View Data PathView Security ModelDownload Privian Blueprint (PDF)

Start here

Six questions, six answers

The fastest path through a Privian review. Each card opens the source page.

Security review essentials

Common procurement questions

Short, extractable answers. Use the Learn more link for the full implementation reference.

QuestionShort answerLearn more
What reaches the model?The masked prompt only. Supported entities are replaced with placeholders such as PERSON_1, EMAIL_1 before the outbound provider call.Data path
Do you store prompts?No. Raw prompt bodies and rehydrated response bodies are not persisted. Only sanitized events and aggregate usage are retained.Data handling
Do you train models?No. Privian does not train models on customer prompts or responses. Privian uses deterministic in-process detectors for masking.Data handling
Who owns API keys?You own your Privian gateway API keys (shown once at creation, stored as SHA-256 hash) and your BYOK provider credentials.Credential handling
Can I use my own provider account?Yes. BYOK is the default. Your credential authenticates the upstream provider call; provider-side billing and terms apply to your account.BYOK
What is retained?Account, billing and team metadata; encrypted BYOK credentials; hashed API keys; usage rollups; sanitized observability events.Retention
Do you support self-hosting?Not at this time. Privian is operated as a managed gateway. Self-hosted inference is out of scope today.Security model
Do you support data residency?Region selection is not a contracted feature today. Provider-side region behavior is governed by your relationship with the provider.Subprocessors
What subprocessors are involved?Hosting and managed database, a payments processor, a transactional email provider, and the model provider you select for BYOK.Subprocessors

Enterprise evaluation package

Privian Blueprint

A concise document teams can share internally during security reviews.

Many teams need a concise document they can share internally during security reviews. Privian Blueprint is designed to answer the most common procurement and enterprise AI questions in a single document — data path, retention, credential handling, subprocessors, and the explicit scope of what Privian is and is not.

Download PDFRead the web version

Core trust resources

Read deeper

The pages a procurement or security reviewer will want open in tabs.

Scope

What Privian is not

A deliberate list of things Privian does not do, so you can scope evaluation correctly.

  • Privian is not a self-hosted inference platform.
  • Privian is not a governance platform.
  • Privian is not an audit-log platform.
  • Privian does not claim HIPAA, PCI, SOC 2 or ISO certifications.
  • Privian does not prevent prompt injection or jailbreak attacks.
  • Privian does not control downstream provider behavior, retention, or training opt-outs.

For an explicit list of what is in scope today, see /resources/security.

FAQ

Frequently asked questions

What reaches the model?
Only the masked prompt. Supported sensitive values are detected in-process and replaced with placeholders such as PERSON_1 or EMAIL_1 before any outbound provider call. The provider sees the masked text, never the originals.
What does Privian retain?
Account, billing and team metadata; BYOK provider credentials encrypted at rest with AES-256-GCM; API keys stored as SHA-256 hashes; usage rollups (token counts, request counts, latency aggregates); and sanitized observability events that do not contain prompt or response bodies.
Who owns provider credentials?
You do. BYOK credentials are encrypted at rest, decrypted in process only for the duration of a single request, and discarded afterwards. Plaintext is never written to disk or held in long-lived process state.
Can I use my own OpenAI account?
Yes. Privian is BYOK-first. Provide your OpenAI key and outbound calls are authenticated with your credential. Billing and terms apply between you and OpenAI directly.
Can I use my own Anthropic account?
Yes. The same BYOK model applies. Privian supports Anthropic alongside OpenAI, Google (Gemini) and DeepSeek.
Can Privian prevent employees from sharing sensitive information?
Privian masks supported entity types before prompts reach the provider, which reduces prompt-level exposure. It is not a DLP product, not a policy-management platform, and does not stop a user from intentionally bypassing the gateway. It is a data-path control, not a behavioral one.
Does Privian support regional residency?
Region selection is not a contracted feature today. Provider-side region behavior is governed by your relationship with the model provider under BYOK.
When should I choose self-hosted models instead?
When your threat model requires that prompts never leave your infrastructure under any circumstances, or when regulatory constraints prohibit managed-provider use. Privian reduces exposure at the prompt layer but the BYOK provider still processes the masked request.