What the public site stores
The public site mainly serves static browsing and routing; ordinary visitors are not asked to create a web account. Character pages only show reviewed, published allowlist details.
Browsing the public site requires no sign-in. Only after you sign up and open your space, or bind Telegram, does the system create a business user and store what conversation continuity needs.
The public site mainly serves static browsing and routing; ordinary visitors are not asked to create a web account. Character pages only show reviewed, published allowlist details.
Once you use your space or Telegram, the system stores account and binding details, conversation history, relationship state and the delivery and audit records it needs, so the experience stays continuous and recoverable.At sign-up it also records the ad attribution values in your sign-up link (such as SID/AID) to measure ad performance; the pages never load fbq or other third-party tracking scripts. Contact us if you want that attribution data deleted.
Conversations are sent to the configured AI models to generate replies, and may be distilled into episode summaries, factual memory and relationship state for later chats. Do not send sensitive information you would not want processed or remembered long term.
The day-to-day operations console shows delivery status, counts and truncated or masked structured information by default; it does not show raw chat text to ordinary support accounts. Administrative actions on data are bound by role permissions and audit records.
These requests have to cover conversations, long-term memory, queued tasks and media files at once. Until a self-service entry ships, pausing a chat will never be described as full deletion; the related capabilities state their processing status and outcome clearly in the Telegram settings.