What the bot stores
The bot stores operational data needed to make the workflow function. This can include Telegram user identifiers needed for bot usage, connected channel identifiers, channel profile memory, generated draft metadata, usage and subscription state, and selected configuration values.
What channel data is stored
The bot can store information about the connected channel, including channel ID, title or description when available, structured channel profile fields, and real sample posts provided through channel activity or /teach. This exists so the bot can write closer to the real voice of the channel.
How the Groq key is stored
The user's Groq API key is not meant to be stored as plain text in the database. The product uses encrypted storage backed by a server-side master encryption key.
Third-party APIs
Depending on the workflow and configuration, the bot may use third-party services such as Groq for AI generation, Telegram Bot API, Supabase/PostgreSQL for persistence, Render or another host for runtime, visual search providers such as Pexels or Pixabay, and selected factual data or research integrations when supported.
What is not the goal
The bot is not intended to become a full private archive of everything in a channel. It stores only the operational context needed for the product workflow.
Practical privacy summary
- The bot stores enough data to generate, refine, and publish posts
- User AI keys are intended to be stored securely
- Third-party providers are part of the workflow
- Production secrets must never be committed publicly