What reaches the model
The masked prompt — supported sensitive values are replaced with placeholders before any outbound provider call.
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.
Start here
Six questions, six answers
The fastest path through a Privian review. Each card opens the source page.
Enterprise review becomes faster when every claim maps to a specific data-path boundary, retained record or documented limitation.
Framework
Enterprise evaluation sequence
- 01
Trace the data path
Identify what enters, leaves and reaches the model.
- 02
Review retention
Separate request-scoped memory from persisted records.
- 03
Review access
Confirm who can see each form of data.
- 04
Validate controls
Check masking, BYOK, routing and observability boundaries.
- 05
Confirm limitations
Match explicit exclusions to your requirements.
What does not reach the model
Detected entities, the per-request placeholder map, and your decrypted provider credential.
What is retained
Account and billing data, AES-GCM-encrypted BYOK credentials, hashed API keys, usage rollups, sanitized events.
What is not retained
Raw prompt bodies, rehydrated response bodies, the per-request entity map, and decrypted provider keys.
Who can access data
Row-level scoped to your organization. Provider credentials are decrypted in-process per request and discarded.
How BYOK works
Your provider credential authenticates the upstream call. Billing and provider-side terms apply to your account.
Quick answers
What enterprise buyers ask first
The six questions that come up in every security review.
What reaches the model?
Only the masked prompt. Supported entities are replaced with placeholders before any outbound call.
Reference →What is retained?
Account data, AES-GCM-encrypted BYOK credentials, SHA-256 hashed API keys, usage rollups, sanitized events.
Reference →BYOK?
Yes. Your provider credential authenticates the upstream call. Billing stays on your provider account.
Reference →Subprocessors?
Hosting, managed database, payments, transactional email, and the BYOK model provider you select.
Reference →Self-hosted?
Not at this time. Privian is operated as a managed gateway today.
Reference →Regional residency?
Region selection is not a contracted feature today. Provider-side region behavior follows your provider account.
Reference →Security review essentials
Common procurement questions
Short, extractable answers. Use the Learn more link for the full implementation reference.
| Question | Short answer | Learn 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.
Core trust resources
Read deeper
The pages a procurement or security reviewer will want open in tabs.
Enterprise Trust Package
Single URL to forward to security and procurement teams.
Compliance Roadmap
Implemented controls, in-progress work, planned attestations — dated.
Blueprint Guide
How founders, security and procurement use the Blueprint.
Data Path
What reaches the model, what stays, what is logged.
Security
Privian's security model, retention and credential handling.
Architecture
How the gateway is built end-to-end.
Subprocessors
Operational providers and the BYOK boundary.
GDPR & LLMs
Reducing prompt-level exposure under GDPR.
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.