Privacy and Data Handling

This page explains what data is required to run the bot, how it is processed, and what data is not stored long-term.

What data is used

Telegram user ID is used for quota, balance, and subscription checks.
Balance, subscription status, and payment-related information.
Technical events required for stable service operation and abuse prevention.

What is not stored long-term

Full chat history is not stored as a persistent message database.
Prompt and model response texts are not stored as a long-term archive.
Conversations do not create permanent chat history on the service side.

Short-lived context

To keep coherence, the current request can include the last two messages.
This context is used only for request processing and sent to Grok API without long-term storage on our side.
Messages are not stored as permanent chat history.
New Chat clears active context and starts a new dialogue.

Processing and security

Requests are routed through the bot backend to the official Grok API.
Access to internal systems is restricted to authorized personnel.
Diagnostic logs do not contain full message texts.