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
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.
Communications Boundary
SMS, email, voice-call alerts, and push notifications are treated as authenticated operational channels, not public chat features.
Known users only
Max SMS replies and call-capable workflows require a phone number mapped to an approved Kaizen user profile. Unknown senders may be recorded for security but do not receive model replies or call access.
Consent and keywords
STOP, START, and HELP are handled deterministically before model routing. SMS consent and phone mapping remain separate from public web chat.
Delivery records
Operational messages and call events keep delivery status, provider identifiers, timestamps, and contact mapping for auditability and troubleshooting.
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.
KaizenAI transactional messaging
KaizenAI may use email, SMS, voice-call alerts, or push notifications for account security, password reset, service status, audit alerts, reminders, delivery confirmations, and other operational updates requested by or relevant to registered users.
Mobile information and messaging consent will not be shared with third parties or affiliates for marketing or promotional purposes. Message delivery providers are used only to deliver the requested transactional communication. SMS message frequency varies based on account activity and service status. Message and data rates may apply.
Users can opt out of SMS notifications by replying STOP and can request help by replying HELP or contacting [email protected].
KaizenAI SMS is not used for marketing, affiliate promotion, lead generation, or third-party promotional messaging. Public KaizenAI Open users do not get SMS access unless they are separately approved and mapped as an SMS-enabled or call-enabled Kaizen profile.
SMS Consent, Delivery, and Retention
How INTRAC.NET / KaizenAI records consent evidence and processes operational messaging.
Mobile information collected
Kaizen may retain the submitted mobile number, affirmative-checkbox state, consent source and method, UTC timestamp, disclosure and policy versions, privacy-safe request evidence, carrier message identifiers, delivery metadata, and STOP, START, HELP, and administrative consent events.
Why it is collected
This information supports consent verification, delivery and troubleshooting, opt-out enforcement, security review, carrier compliance, and authorization of operational alerts or user-requested responses. Consent history is append-only through normal Kaizen application APIs.
STOP and START
STOP and equivalent opt-out keywords immediately suppress future application messaging. START may restore consent only for a known, otherwise authorized contact under Kaizen policy. A profile synchronization or public form submission cannot silently override STOP or administrative disablement.
Service authorization
Phone-number consent is separate from Kaizen profile authorization. An unknown phone may have a consent request recorded without receiving Max access, and changing a profile phone number does not transfer consent from the previous number.
Sharing and telecommunications providers
Mobile opt-in information is not sold and is not shared with third parties or affiliates for marketing or promotional purposes. Twilio, Telnyx, wireless carriers, and necessary telecommunications subprocessors may process message content, routing information, phone numbers, and delivery metadata only as required to provide, secure, troubleshoot, and document the messaging service.
Protection and retention
Consent evidence is kept in the controlled Communications system of record. General-purpose logs use redacted numbers, hashes, event identifiers, bounded error details, and status metadata instead of raw carrier payloads or full message bodies. Records are retained only as needed for service operation, security, consent history, compliance, and dispute resolution, subject to applicable obligations.
Privacy questions and requests
For questions about mobile information, consent history, retention, correction, or deletion requests, contact [email protected]. Some consent or delivery records may need to be retained when required for security, compliance, or evidence of an opt-out request.
SMS privacy section version: sms-privacy-2026-07-11-v1.
