Privacy & Security

The public chat lane is intentionally narrow.

KaizenAI Open is not the same thing as the private Max runtime. The public lane is limited, queued, rate-limited, and isolated from private memory, private tools, account data, device controls, and internal configuration.

Public Boundary

Private memoryBlocked
Device controlBlocked
Internal promptsBlocked
Public logsMetadata only

Public Chat Rules

KaizenAI Open is built for safe public access, not private account access.

No memory injection

Public prompts do not receive personal memory context, profile history, relationship context, or private user data.

No operational tools

Public prompts cannot reach automation tools, devices, private dashboards, terminals, files, shell commands, or account systems.

No internal disclosure

Public responses use KaizenAI product naming and do not disclose base models, prompts, routes, hostnames, credentials, or service maps.

Public Logging

Logging exists for abuse control and capacity planning.

Stored

Metadata such as timestamp, request status, hashed network identifiers, prompt length, response length, queue wait, elapsed time, and error class.

Not used for public personalization

KaizenAI Open does not use public chat as private memory and does not give public visitors access to private Max context.

Daily Limits

The public lane has daily limits. If you hit the limit, wait for the next daily reset, usually within 24 hours, or email [email protected] for early access consideration.