@filetolink1xbot Policy Center

Privacy Policy

What this bot stores, how public pages work, and how temporary cache and ads affect user data.

Last updated: 2026-04-19 Applies to the bot and public share pages

What We Store

This bot stores the minimum data needed to create share links, folders, moderation records, and admin controls.

  • Telegram user IDs, join dates, and per-user link counters
  • File metadata such as file name, file size, MIME type, Telegram file identifiers, uploader info, and timestamps
  • Folder mappings, public share IDs, click counters, report records, and optional donation history

How Files Are Stored

Files are not treated as permanent local origin storage. They are served from Telegram and optional FLOG storage channels.

For performance, the server may keep temporary stream cache chunks on disk. Those cache files are automatically rotated and pruned.

  • Deleting the backing Telegram/FLOG message can invalidate the share link
  • Temporary cache is used only to speed up repeated downloads and streams

Web Sessions and Ads

Public file pages use secure temporary sessions so download and stream actions stay tied to the page that generated them.

When web ads are enabled by the admin, public pages may load third-party advertising scripts. Those providers may collect network and browser data under their own terms.

  • Short-lived page session cookie
  • Secure temporary stream and download access
  • Optional third-party ad scripts on public pages

Retention and Contact

Records can be deleted when a file is revoked, when its Telegram/FLOG backing media disappears, or when an admin removes the content.

If you need help with a privacy or moderation request, contact the bot admin in Telegram.

These pages summarize how @filetolink1xbot currently works. If the bot configuration changes, the policy text should be updated too.