Data handling
Keep the runtime where your prompts live. Decide separately where the console is allowed to live.
The runtime evaluates prompts, outputs, and tool payloads inside your environment on every plan. The hosted console is a separate operating surface, and Growth is designed around operational metadata by default rather than prompt and response bodies.
| Plan | Runtime location | Console location | Hosted visibility by default | Notes |
|---|---|---|---|---|
| Starter | Customer infrastructure | No console | Not applicable | Runtime-only onboarding with local policy files. |
| Growth | Customer infrastructure | Hosted by ZNYX | Trace id, decision, detector summary, latency, and scope metadata | Hosted console designed around metadata-first operational visibility by default. |
| Enterprise | Customer infrastructure | Hosted by ZNYX or customer infrastructure | Deployment-dependent | Use self-hosted console when private operations are required. |
What the hosted console is designed to retain by default
- Trace identifier
- Allow, block, redact, or warn outcome
- Detector summary and policy scope
- Latency and operational status
- Project or environment metadata
Hosted visibility note
Growth is metadata-first by default. If you need the console to live entirely inside your own boundary, that is an Enterprise deployment - not a hidden default of Growth.
Legal and procurement follow-through
The privacy and DPA pages cover roles, retention, and contractual handling at a high level. Executed agreements control the specifics of data processing for commercial customers.