انتقل إلى المحتوى

Privacy Policy — tgfilebotter Platform

Last updated: 17 April 2026

1. Introduction

tgfilebotter is a multi-tenant platform that enables Telegram bot operators ("Bot Operators") to create and manage Telegram bots for distributing files to their own end users. This Privacy Policy explains what data the platform collects, how it is used, and what rights users have.

This policy applies to:

  • Bot Operators — individuals or organizations who register a Telegram bot on this platform to manage and share files.
  • End Users — individuals who interact with bots created through this platform via Telegram.

By using this platform, you agree to the collection and use of data as described in this policy.

2. Data We Collect

From Bot Operators

When a Bot Operator registers a bot on the platform, the following information is collected and stored:

  • Telegram bot token — the credential that allows the platform to operate the bot on the operator's behalf. Stored securely on our servers with access controls in place.
  • Telegram channel ID — the identifier of the Telegram channel from which files are served.
  • Bot username — the public Telegram username of the bot (e.g. @myfilebot).
  • File metadata — file names, file sizes, and Telegram file IDs for files added to the bot's library. We store references to files, not the file contents themselves. Files are hosted on Telegram's infrastructure.
  • Operator's Telegram user ID — used to verify ownership of the bot and control access to bot management features.
  • Admin settings and configuration — rate limit parameters, whitelist settings, and other bot configuration chosen by the operator.

From End Users

When an end user interacts with a bot powered by this platform, the following data may be collected:

  • Telegram user ID — a numeric identifier assigned by Telegram to each user. Used for rate limiting, ban enforcement, and whitelist matching.
  • Telegram username — only collected if the operator has configured username-based whitelisting for their bot.
  • Message interaction logs — a temporary record of bot interactions retained in memory for operational purposes. These are not written to permanent storage.
  • Rate limit and ban records — stored temporarily to enforce usage limits set by the Bot Operator. Ban records expire automatically after their configured duration.

What We Do NOT Collect

  • File contents — files are stored on Telegram's servers, not ours. We only store references (Telegram file IDs) that allow bots to retrieve and forward files via the Telegram API.
  • Real names, email addresses, or payment information from end users.
  • Location data.
  • Device identifiers, IP addresses from end users, or browser fingerprinting data.

3. How We Use Data

Data collected through this platform is used solely to operate the service:

  • To authenticate Bot Operators and allow them to manage their bots.
  • To operate the Telegram bots registered on the platform (sending files, enforcing rate limits, handling whitelist rules).
  • To enforce usage limits and prevent abuse of the platform.
  • To maintain platform security and integrity.

We do not sell data to third parties.

We do not use data for advertising or marketing purposes.

We do not share Bot Operator or end user data with any third party except as strictly necessary to operate the service (e.g. using the Telegram Bot API, which is operated by Telegram Messenger Inc.).

4. Data Storage and Security

Data is stored on servers located in Germany (European Union).

We try to take the best storage and security measures to our knowledge. However, no data storage or security system is perfectly infallible. Bot Operators are encouraged to regenerate their bot tokens via BotFather if they believe a token may have been compromised, and to notify the platform administrator. Do not use this system to upload personal or sensitive information.

5. Telegram's Role

This platform operates entirely through the Telegram Bot API, provided by Telegram Messenger Inc. All message content, file transfers, and user interactions occur within Telegram's infrastructure and are subject to Telegram's own Privacy Policy, available at telegram.org/privacy.

We are not responsible for how Telegram collects, processes, or stores data. When an end user sends a message to a bot, that message is handled by Telegram's systems before being forwarded to our platform via webhook.

Bot Operators and end users should review Telegram's privacy policy in addition to this one.

6. Data Retention

Bot Operator data is retained for as long as the bot is active on the platform. When a Bot Operator removes their bot, associated data (bot token, channel ID, file metadata, configuration) is deleted within 30 days of removal.

End user data:

  • Rate limit records and ban records expire automatically after the duration configured by the Bot Operator (e.g. a 24-hour ban record is deleted after 24 hours).
  • Telegram user IDs are retained in the database for as long as the associated bot remains active on the platform.
  • Message interaction logs held in memory are discarded when the server process restarts and are never written to permanent storage.

7. Bot Operator Responsibilities

Bot Operators use this platform to build services for their own end users. By operating a bot through this platform, Bot Operators accept responsibility for:

  • Obtaining appropriate consent from their end users before collecting or processing any personal data through the bot.
  • Complying with Telegram's Terms of Service (telegram.org/tos) and all applicable local laws and regulations.
  • Not using the platform to distribute illegal content, malware, or content that violates Telegram's terms or applicable law.
  • Keeping their bot token secure. A bot token gives full control over the bot. If a token is exposed, it must be regenerated immediately via BotFather and the new token updated in the platform.
  • Informing their end users about the data practices described in this policy that may affect them (particularly Telegram user ID collection and rate limiting).

The platform administrator reserves the right to suspend or remove any bot found to be in violation of these responsibilities.

8. End User Rights

End users who interact with bots on this platform have the following rights with respect to data held about them:

  • Right to access — you may request information about what data (if any) is stored about your Telegram user ID.
  • Right to erasure — you may request that your Telegram user ID and associated records be removed from the platform's database.

To exercise these rights, contact the operator of the specific bot you interacted with. If you are unable to reach the bot operator, you may contact the platform administrator using the contact information in Section 10.

Note: because this platform does not collect names or email addresses from end users, requests must be made by providing your Telegram user ID (a numeric value visible in Telegram client settings or through bots such as @userinfobot).

9. Changes to This Policy

We may update this Privacy Policy from time to time. When changes are made, the "Last updated" date at the top of this document will be revised.

Continued use of the platform after changes are posted constitutes acceptance of the updated policy. Bot Operators are encouraged to check this document periodically.

For significant changes affecting how personal data is used, we will make reasonable efforts to notify active Bot Operators.

10. Contact

For privacy-related inquiries, data access or erasure requests, or to report a concern about how data is being handled on this platform:

Platform Administrator Contact: https://t.me/blessed_tree

End users should contact the operator of their specific bot in the first instance. Bot operators should contact the platform administrator using the details above.