Integration rules
Keep API keys server-side
Never expose Kivo API keys in client bundles, mobile apps, screenshots, or public repos.
Prefer Enterprise Worker
Keep raw AI outputs, prompts, traces, sources, and embeddings in your environment when data is sensitive.
Scope by project
Use project-scoped keys so accidental cross-workflow access is constrained.
Preserve request IDs
Store Kivo request IDs in your logs so support and audit investigations can trace specific calls.
Review high-stakes outputs
Route consequential outputs to a human reviewer even when Kivo returns a non-blocking status.
Watch limits
Handle 402 and 429 responses explicitly so production workflows fail predictably.
Sensitive data posture
| Area | Guidance |
|---|---|
Raw sources | Treat as sensitive customer data. Prefer Enterprise Worker Deployment for production traces. |
Kivo API Deployment | Use only synthetic, sanitized, or explicitly approved packets. |
Worker events | Send metadata-only status, verdicts, counts, hashes, redacted categories, and opaque storage pointers. |
Logs | Do not log full source text, API keys, secrets, or customer documents. |
Verifier metadata | Store with the review run so claim-report observations are auditable. |
Retention | Follow the retention terms for your Kivo plan and deployment mode. |
Tenancy | Use organization and project context for every review-run read and write. |
Known limitation
Evidence-bounded results
Kivo can only evaluate support against supplied sources. A claim that appears supported by one source may still need additional business, legal, medical, financial, hiring, compliance, or safety review.