🔒 Privacy Policy

Privacy Policy

Last updated: 27 October 2026

TL;DR: We collect only what's needed to run TeleBotBuilder. We never sell your data. Your bot tokens are stored securely. You can delete your account and data anytime (cancel any subscription first).

1 Information We Collect

Account Information: When you sign in with Google, we receive your name, email address, and profile photo. We use this to create and manage your account.

Bot Data: Your Telegram bot token, flows, blocks, connections, contacts, and message history are stored to provide the bot builder service.

Payment Information: We never receive your card details. Purchases in the Android app are processed by Google Play Billing and managed through RevenueCat, which receives your purchase history and your TeleBotBuilder user ID. Purchases on the website are processed by Whop. We store the purchase records these services send us (such as transaction, subscription and membership IDs, amount, currency and the account details included with them) to link purchases to your account.

Images: Images you upload through the Image block are stored on our image hosting (Cloudflare R2) and served from img.telebotbuilder.com. They may be scanned for illegal content. The resulting image links are stored with your flows. Photos that your bot's users send to your bot are not stored by TeleBotBuilder: only a Telegram file reference is kept as part of the conversation record, and the image itself is loaded from Telegram when you view it.

Usage Data: Basic server logs including IP addresses and request timestamps for security and debugging purposes.

2 How We Use Your Data

  • To provide and operate the TeleBotBuilder service
  • To execute your bot flows and deliver messages via Telegram
  • To process payments and manage your subscription
  • To send important service emails (welcome, trial expiry, account updates)
  • To improve our service and fix bugs

We never sell your data, use your bots' or contacts' data for advertising, or share it outside of what's needed to run the service.

3 Data Storage & Security

Your data is stored on secure servers. Bot tokens are stored in our encrypted database and are never exposed to the frontend interface or other users.

All connections to TeleBotBuilder use HTTPS/TLS encryption. We use Cloudflare for additional DDoS protection and security.

Message history between your bot and its users is stored to enable features like live chat and conversation history. This data is only accessible to you (the bot owner).

4 Telegram Integration

TeleBotBuilder connects to Telegram's Bot API using the token you provide. We receive and process messages sent to your bot to execute your configured flows.

We store basic contact information (Telegram ID, first name, last name, username) of users who interact with your bot. This is necessary to operate the contact management and live chat features.

Stars payments. If a bot owner uses Telegram Stars payments, we store a record of each payment for that bot on the owner's behalf: the buyer's display name and username, the buyer's Telegram user id (kept only to process refunds), the product, amount, date, status and Telegram's payment reference. These records are shown only to that bot's owner.

We do not access any Telegram data beyond what is sent directly to your bot.

5 Group Manager

Group Manager lets your bot keep a Telegram group tidy. When your bot is an admin in a group and you have turned Group Manager on for that group, the bot checks the group's messages automatically to apply the settings you chose: the welcome message, the rules, the link, forward and word filters, anti-flood, warnings and the admin commands.

Message content is processed in memory to apply those settings and is not stored. For each group we store the group's Telegram id and title, your settings, the member count Telegram reports for the group, the Telegram user ids of members together with their warning counts, and short-lived timers for messages the bot will remove again (removed after 3 days).

Group data is deleted when you forget the group on the Groups page or when you delete your account.

6 Third-Party Services

  • Google OAuth: Used for authentication. We receive only your public profile information.
  • Telegram Bot API: Used to send/receive messages for your bot.
  • Cloudflare: Used for DNS, CDN, and security services.
  • Cloudflare R2: Stores images you upload through the Image block, served from img.telebotbuilder.com. Uploads may be scanned for illegal content.
  • Google Play Billing: Processes purchases made in the Android app.
  • RevenueCat: Manages Android app subscriptions. Receives your purchase history and your TeleBotBuilder user ID.
  • Whop: Processes purchases made on the website. We never receive your card details.
  • Whop Pixel: Helps us understand how visitors find our website and measure the performance of our ads and checkout (see Analytics below).
  • imgbb: Previously hosted uploaded images. New uploads are no longer sent there, but images uploaded before that change remain hosted on imgbb.
  • OpenAI and Anthropic: AI bot flow generation.

When you use the API block in your flows, requests are made directly from our server to the URLs you configure. We are not responsible for the privacy practices of external APIs you connect.

AI Reply block. If you use the AI Reply block, your context, instructions and your bot users' messages are sent to the AI provider you choose, using your own API key. That provider's terms and pricing apply, and you are responsible for your key and its usage.

7 Analytics

We use the Whop Pixel on our website to understand how visitors find us and to measure the performance of our ads and checkout.

8 Your Rights

You have the right to:

  • Access: View all data we store about you
  • Delete: Delete your account and all associated data at telebotbuilder.com/delete-account.html, or disconnect a bot in Settings to delete its flows, contacts, and messages. Deleting your account does not cancel a subscription: cancel a Google Play subscription in Google Play, and cancel a website subscription from Settings, before you delete your account.
  • Portability: Request a copy of your data by contacting us
  • Correction: Update your information via Google account settings

9 Data Retention

We retain your account data as long as your account is active. When you disconnect a bot, all associated flows, contacts, and messages are permanently deleted. When you delete your account, your account and all associated data are permanently deleted.

Server logs are retained for up to 30 days for debugging and security purposes.

10 AI Bot Generation

When you use the AI Builder to generate a bot flow, the description you write is sent to OpenAI, L.L.C. (United States) or Anthropic, PBC (United States), which we use as processors to generate the flow. Along with your description we send a technical specification of the available building blocks, and the names, scopes and column names of your bot's existing data collections, so the AI can reuse storage you already have. We do not send the contents of those collections, your bot token, your contacts, or any messages your bot has exchanged.

We do not store your description. It is used to make the request and is then discarded; it does not appear in your generation history. The flow that is produced is saved to your account as part of your bot, and you can edit or delete it at any time.

OpenAI does not use data sent through their API to train their models. They may retain the request and response for up to 30 days for abuse monitoring, after which it is deleted, unless they are legally required to keep it longer. Their handling of this data is governed by their own privacy policy.

This means your description is transferred outside your country and processed in the United States.

When a request reaches the AI, we keep a record of it so we can enforce plan limits: the date, the outcome, whether it counted towards your allowance, the AI model used, the number of tokens used, a short technical reason if it failed, and the name of the flow created. This record never contains your description or the generated flow. Requests we refuse before calling the AI, for example when you have no allowance left, are not recorded. The flow name in this record remains after the flow itself is deleted, and is removed when you delete your account.

11 Children

TeleBotBuilder is not meant for anyone under 13, as our Terms of Service say. We do not knowingly collect data from children under 13.

12 Contact Us

For privacy-related questions or data requests, contact us at:

Email: [email protected]

TeleBotBuilder, Dhaka, Bangladesh