Requirements for regulated industries, built to order.
Data residency, CMEK, dedicated shards, and SLAs are available to discuss through the Enterprise program.
Talk to us
When you need a trail that can't be erased.
Legal Hold, GDPR erasure, and 7-year audit log retention (statutory retention, linked to Legal Hold) are available to discuss through the Enterprise program. Tamper-evident audit logs (hash chain) come standard on Business and above.
See audit logs
Invoice billing and MSAs, available on request.
Talk to us about a contract structure that fits your procurement and legal process.
Talk to us
Make every AI interaction auditable. Governable.
A multi-AI workspace spanning Chat / Compare / Debate / Workflow, recording who did what, when, and with which model, deleting data in line with the law, and freezing it when litigation arises. The audit, data sovereignty, and preservation controls your governance team needs are built into the product itself.
The control surface at a glance
Audit, behavior monitoring, erasure, preservation, and data sovereignty—the pillars enterprise governance requires, delivered in a single workspace.
Audit trail
160+ event types, structured and recorded. Tamper-evident.
Behavior monitoring
Detects abnormal usage and auto-locks.
GDPR & erasure
From request to physical erasure and key destruction.
Legal Hold
Freezes deletion during litigation or audit.
Data sovereignty & control
SSO, roles, data residency, allowed models.
Prove what happened, after the fact.
From authentication, permission changes, and deletions to artifact operations and billing, more than 160 event types are recorded in structured form. Compliance-critical events are linked in a hash chain (standard on Business and above); if even a single record is altered or dropped, every subsequent hash breaks, so tampering and deletion surface at verification time (tamper-evident). For Enterprise, statutory 7-year retention and Legal Hold-linked long-term retention requirements are available on request.
Retention split into 3 tiers by purpose
| Tier | Retention | Tamper detection | Main recorded events |
|---|---|---|---|
| Tier 1 | 7 years | hash chain | Login, permission changes, GDPR erasure, Legal Hold ON/OFF, contract changes |
| Tier 2 | 1 yearEnt. anomalies: 7 years | — | Anomaly detection, auto-lock, PII detection/masking, GDPR export, team operations |
| Tier 3 | 90 days | — | Thread creation/close, artifact save/archive, workflow runs |
Detect tampering with a hash chain
Each event incorporates the hash of the one before it. Alter even a single past log entry and every subsequent hash diverges, so tampering and deletion are detected immediately. The trail can serve as evidence submitted to auditors and regulators.
What you can audit
Authentication & access
login_success/failure, session_created/destroyed, token_refreshed. Track when and who signed in.
Permissions & organization
acl_changed, org_admin_granted/revoked, team_member_added, project_granted, entitlement_changed.
Data protection
PII detection/auto-masking, detection of out-of-purpose use, and create/update/delete of your own detection rules.
Compliance
GDPR erasure from request to completion, data export, Legal Hold ON/OFF, and deletion blocked by preservation.
Anomaly & security
anomaly_detected, account_auto_locked/unlocked, approval_sla_breached. Records signs of insider threats.
Business operations
thread_created/closed, artifact_saved/archived, run_completed, usage_counter_updated.
Detect abnormal usage, and stop it.
Usage patterns are evaluated continuously, and access that exceeds a threshold is automatically locked and reported. On detection, the account is suspended, a notification is sent to Slack, and the event is recorded in the audit log. Can be enabled per organization.
* Monitoring covers operation (action) logs and abnormal usage patterns. It does not track the content people view (who read what).
| Detection pattern | Condition (implemented value) | Severity | Automated response |
|---|---|---|---|
| High-frequency access rate | More than 120 requests per minute | Low | Temporary lock (auto-released after 1 hour) |
| Late-night concentrated use time_of_day | More than 30 requests/day during 02:00–05:00 UTC | Low | Temporary lock (auto-released after 1 hour) |
| Probing the admin API endpoint | Non-admin hitting the admin API more than 5 times in 10 minutes | High | Account suspension + re-authentication (manual release by an admin only) |
The "right to erasure," seen through to execution.
We accept erasure requests for personal data and, after a grace period, carry them through to physical erasure. Rather than merely hiding the data, we perform irreversible erasure with an audit trail—including destruction of backup encryption keys (crypto-shredding) and pseudonymization of the billing ledger.
The state transitions to pending_hold and the SLA is paused. After the hold is lifted, the 30 days restart (balancing the preservation obligation with the right to erasure).
If it is uncertain whether the person is an organization employee, we fall to pending_manual_review and require an admin's confirmation (fail-closed).
Physically deleted
- Threads, messages, and artifacts
- RAG knowledge (chunks and vectors)
- Profile and various settings
- Destruction of backup encryption keys backup_keys_shredded
Retained (for legal consistency)
- Data under Legal Hold (until released)
- Billing ledger required for audit → retained after pseudonymization
- The audit trail of the deletion itself (Tier 1, 7 years)
Audit trail: Each stage remains in the audit log as gdpr_deletion_requested / pending_hold / physical_erasure_completed / …_blocked_by_legal_hold, supporting your response to GDPR Article 17 (right to erasure), Article 30 (records of processing activities), and Article 32 (integrity and confidentiality).
When litigation or audit strikes, nothing gets deleted.
"The moment a preservation obligation arises, deletion stops."
When Legal Hold is enabled, the entire tenant (organization) becomes subject to preservation. While the hold is active, physical deletion and purges do not run, and even if a GDPR erasure request arrives it is frozen as pending_hold. After the hold is lifted, the grace period restarts.
Who can use it, and what they're allowed to use.
Unify the entry point with SSO, separate permissions by role, and align data residency and allowed models with your organization's policy.
SSO & access control
Authentication is delegated to Onion, and JWTs are verified via the verify-token API. Permissions are determined by group→role mapping. Emergency break-glass sessions are also audited. SCIM coming soon
| Permission | user | site-admin | system-admin |
|---|---|---|---|
| Chat / Compare / Debate / run Workflows | ● | ● | ● |
| Read audit logs | — | ● | ● |
| Legal Hold ON/OFF | — | ● | ● |
| Team & member management | — | ● | ● |
| All-tenant operations / contract management | — | — | ● |
Data sovereignty & model control
System-wide model catalog and governance are live in production. Per-tenant policy overrides are in development (on the roadmap).
Options you can tailor with Enterprise.
None of the following are included in the standard plans. They are available on request as part of the Enterprise program.
Data residency
Requirements around where data is stored, such as the storage region.
CMEK (customer-managed encryption keys)
Use of encryption keys managed on your side.
Dedicated shard
A configuration for cases that require a dedicated infrastructure environment.
DLP integration
Integration with your existing DLP solution.
7-year audit log retention
Statutory retention and Legal Hold-linked long-term retention requirements.
Invoice billing & MSA
Payment by invoice, signing a master agreement, SLAs, and a dedicated CSM.
How Enterprise differs from Business+.
| Aspect | Business+ | Enterprise |
|---|---|---|
| Payment method | Per-seat billing (credit card, etc.) | Invoice billing available on request |
| Data residency | Standard configuration | Available on request to fit your needs |
| Support | Standard support | A dedicated CSM available on request |
| Contract form | Contract based on the Terms of Service | An MSA (master agreement) available on request |
| Audit log retention | Standard (hash chain) | 7 years and Legal Hold linkage available on request |
Pricing — teams & organizations.
Prices are per seat. A minimum number of seats applies. Enterprise is a custom quote based on your requirements (seats + metered PFC).
| Plan | Team | Business | Business+ | Enterprise |
|---|---|---|---|---|
| Monthly (per seat) | $60 | $95 | $150 | Custom quote |
| Annual (per month) | $50 | $79 | $125 | Seats + metered PFC |
| Minimum seats | 5 seats | 10 seats | 25 seats | Custom |
| Monthly PFC (per seat) | 4,000 | 4,500 | 5,000 | Metered |
| Storage | 15GB | 25GB | 40GB | Custom |
Higher plans include everything in the plans below them (Individual ⊂ Team ⊂ Business ⊂ Enterprise). Enterprise combines options such as data residency, a dedicated shard, 7-year audit retention, SLAs, invoice billing, and an MSA to fit your needs.
Requirements mapped to features.
We've mapped which Prompt Flow Studio features address common regulations and requirements.
| Regulation / requirement | Corresponding feature | Status |
|---|---|---|
| GDPR Article 17 Right to erasure | Erasure request (30-day SLA, physical erasure, backup key destruction, ledger pseudonymization) | Available |
| GDPR Article 30 Records of processing activities | 160+ audit trail types, retained up to 7 years | Available |
| GDPR Article 32 Integrity and confidentiality | Hash-chain tamper detection, PII detection/masking | Available |
| eDiscovery / litigation hold | Legal Hold (tenant-wide, deletion freeze, Tier 1 audit) | Available |
| Fraud & insider-threat detection | Anomaly detection (rate / late-night / admin-API probing), auto-lock, notifications | Available |
| Access management | Onion OIDC SSO, 3 roles, break-glass auditing | Available |
| Data sovereignty / model control | Data-residency policy, allowed models, provider restrictions (per tenant) | Coming soon |
| Automated provisioning | SCIM integration | Coming soon |
* "Available" indicates the feature is implemented and running. The final judgment of legal compliance should be confirmed by your own data protection officer and legal team. We do not currently hold third-party certifications such as SOC 2.
How the conversation goes.
Frequently asked questions.
How long are audit logs retained?
Can tampering with audit logs be detected?
How do you handle personal-data erasure requests (GDPR)?
Can we monitor employee behavior?
Can we sign an SLA? What about pricing?
Do you hold third-party certifications such as SOC 2?
Let's review your governance requirements together.
We'll walk you through an implementation design and demo aligned to your audit, retention, erasure, and preservation policies. We also handle security questionnaires and DPAs.