Tenant isolation
Tenant identity comes from authenticated context. D1 routing, R2 keys, and hydrated vector results are reauthorized server-side.
Security
Trust controls that describe the product as it exists.
Kiteframe publishes implemented safeguards and avoids unsupported certification claims.
Scoped actions
Read and write scopes remain separate. Sensitive writes require step-up authentication or human approval.
Content minimization
Sensitive content is redacted from logs by default, with retention tiers for traces, attachments, and conversations.
Immutable audit
Membership changes, release promotion, action approval, secret rotation, and exports emit attributable audit events.
Injection defense
Source text is data, tool policy is enforced outside the model, and adversarial tests run before promotion.
Incident readiness
Runbooks cover bad releases, credential compromise, queue backlogs, billing errors, and data-rights failures.
Cloudflare-native boundaries
Workers, D1, R2, Vectorize, Queues, Workflows, and Email Service use bindings instead of embedded platform credentials.
WAF and rate limits
Encrypted transport
Per-environment secrets
Signed webhooks
Hard usage caps
Export and deletion
Report a security issue
Send details to support@kiteframe.xyz with “Security” in the subject.