Q: Is Telegram cloud storage truly free and unlimited?
A: Yes. Telegram does not charge for file storage, data ingress, or egress. Files posted to private channels or groups remain stored in Telegram's cloud indefinitely as long as your account remains in good standing.
Q: How does the add-on handle files larger than Telegram's 50 MB bot limit?
A: By default, the add-on uses intelligent low-memory stream slicing to divide large databases or archives into safe 45 MB chunks and uploads each part sequentially. When recovering, parts can be reassembled on the server or locally using standard OS tools (such as cat or copy /b).
Q: Can I upload large files (up to 2 GB) without splitting them into chunks?
A: Yes! By pointing the add-on to a local or private instance of Telegram's open-source telegram-bot-api server (available via Docker), the per-file upload limit increases from 50 MB to 2,000 MB (2 GB).
Q: Is my database data safe on Telegram's servers?
A: Yes, provided you configure an Encryption Passphrase. The add-on performs client-side AES-256-CBC encryption on your server using PBKDF2 before transmitting anything. Telegram only receives encrypted binary blobs; without your passphrase, the data cannot be read by anyone.
Q: Should I use a Private Group or a Private Channel?
A: Both work seamlessly. Use a Private Group if you want the visual slash command autocomplete menu (/) and the permanent blue [Menu] button. Use a Private Channel if you prefer a silent, read-only vault strictly for archive storage (Telegram disables slash command autocomplete menus inside channels by design).
Q: Can unauthorized users trigger backups using the bot?
A: No. Every incoming webhook update is strictly validated against your configured Telegram Chat ID and bot secret token. Any message or command from an unauthorized user or group is rejected immediately.