# Telegram-Secure-Storage-Bot (mrhlaingbwardev/Telegram-Secure-Storage-Bot)

> It is a secure, privacy-focused cloud storage bot for Telegram: files are stored with PIN protection, burn-after-read access, and anti-leak features, backed by Cloudflare Workers and a D1 database.

- GitHub: https://github.com/mrhlaingbwardev/Telegram-Secure-Storage-Bot
- GitHub.Locker page: https://github.locker/mrhlaingbwardev/Telegram-Secure-Storage-Bot
- Stars: 317
- Language: JavaScript
- Last push: 2026-08-19

## Questions and answers

Written by GitHub.Locker from the README and the repository; check the README below for details.

**Is it a bot app or a server you host?**

A bot backend that runs serverlessly on Cloudflare Workers with Cloudflare's D1 database — there is no traditional server component of your own to run.

**How do I deploy the bot?**

Via Wrangler, the Cloudflare CLI: the project's scripts run wrangler dev for local development and wrangler deploy to publish to Cloudflare.

**What accounts or services does it need?**

A Cloudflare account with Workers and D1 (per the description and wrangler scripts); details such as the Telegram bot token setup are not stated in the README, which is empty in the provided data.

**What security features does it claim?**

Per the repository description: PIN protection, burn-after-read messages, and anti-leak protections for stored content.

**Who is this bot for?**

Telegram users who want private personal cloud storage without handing files to a third-party storage service.

**Where can it be used from?**

From any Telegram client, with the backend running on Cloudflare's edge network.

**Do I need a VPS to run it?**

No — it is built for Cloudflare Workers, a serverless platform, so no VPS is required.

**Does it work offline?**

No — it lives on Telegram and Cloudflare's infrastructure, both of which require connectivity.

**Do I need a GPU for this bot?**

No — it is file storage and messaging logic on serverless infrastructure.

**What do burn-after-read and anti-leak mean here?**

According to the repository description, stored content can be protected with a PIN, set to be destroyed after being read once, and guarded by anti-leak measures — the empty README leaves implementation details unstated.

**What is the storage backend?**

Cloudflare D1, Cloudflare's serverless SQL database, with the bot logic running on Cloudflare Workers.

