About TG Drive
TG Drive is a premium cloud storage interface designed to transform your Telegram experience into a professional file management system. It utilizes your personal Cloud Storage space to host and organize files of any type.
By connecting directly to the official Telegram servers, the app ensures that your data is always available across all your devices without the typical subscription costs associated with traditional cloud providers.
What's New in Version 3.5.0 (Build 2700)
- Zero-Knowledge End-to-End Vault (E2EE): Military-grade client-side encryption using AES-GCM 256-bit and memory-hard Argon2id key derivation (96 MB, 4 passes for new vaults; 64 MB, 3 passes). Credentials and files are encrypted before leaving your browser.
- Dual-Channel OTP Password Recovery: User-selectable choice between personal Telegram Saved Messages (direct MTProto, 0% bot ban risk) and Telegram Bot for 6-digit recovery codes with session-preserving PIN reset.
- Automatic Multi-Device Cloud Sync: Zero-touch background synchronization of cryptographic salt and canary tokens via Telegram Saved Messages (
#TG_DRIVE_VAULT_CONFIG#) with real-time active status indicators across all devices. - Android Native Biometric Unlock: Native fingerprint and facial recognition integrated directly with the Android Hardware Keystore for lightning-fast, secure vault access on mobile.
- Responsive Modular Profile Interface: Streamlined preferences, modular vault controls, and stealth blur protection across all device sizes.
- Background Legacy File Migration: One-tap background engine to scan and encrypt older unencrypted files into the AES-256 vault, with optional Wi-Fi only restriction to preserve mobile data.
- Hardened Multi-Salt Session Recovery: Dual-tier encrypted session storage in IndexedDB with automated fallback resolution across legacy salt structures, preventing accidental logouts.
- Smart Pause & Resume & SW Streaming: High-speed MTProto streaming pipeline with chunk-level persistence, enabling pause, resume, and direct streaming to the browser's native download manager.
- Zero-PII Anonymous Telemetry: Complete user identity isolation. No Telegram User IDs, phone numbers, usernames, session keys, bot tokens, or personal file data are ever transmitted to Firebase. Analytics operate purely on non-reversible daily aggregate counters (
stats/daily/YYYY-MM-DD).
Premium Features
Multipart Architecture
Upload and download massive files efficiently by splitting them into safe, high-speed MTProto chunks.
Pause & Resume
Interrupt and continue downloads seamlessly with chunk-level persistence, saving data and time on large transfers.
Deep Nesting
Unlimited folder depth with lightning-fast smart indexing stored directly in your Telegram cloud.
Local Persistence
Utilizes IndexedDB (idb-keyval) for high-speed local caching and instant app responsiveness.
Zero Server Storage
No data is stored on our servers. Pure peer-to-peer communication via GramJS MTProto.
Bank-Grade Privacy
Leverages Telegram's native encryption and your personal API credentials for absolute security.
Android Native Application
TG Drive is available as a fully optimized, native Android Application built with Capacitor. Experience desktop-grade performance, persistent background downloads, biometric security, and stealth blur protection natively on mobile.
- Native Performance: Smooth 60fps animations with zero browser frame lag.
- Background Tasks: Transfers continue even when the app is minimized.
- Hardware Biometrics: Fingerprint & Face unlock backed by Android Keystore.
- Push Alerts: Native alerts on download completion and transfer status.
System Policies & Limits
2.0 GB Max
Strict 2.0 GB maximum file size policy enforced for all uploads to align with Telegram standard limits.
100 Files
Select and queue up to 100 files at once with automated chunk scheduling and progress tracking.
3 Concurrent
Managed smart queue limits parallel downloads to 3 simultaneous transfers to eliminate FLOOD_WAIT errors.
Setup Guide (Step-by-Step)
Obtain API Credentials
Visit my.telegram.org, log in with your Telegram account, click "API development tools", and create an application to obtain your API ID and API Hash.
Create a Bot Token
Message @BotFather on Telegram, send /newbot, and copy your newly generated Bot Token. This acts as a high-speed metadata gateway and optional OTP recovery channel.
Authorize Your Account
Enter your phone number in the TG Drive login screen. Enter the official Telegram verification code received in your Telegram app. Your session string is stored strictly in client-side IndexedDB.
Start Organizing
Your Telegram "Saved Messages" chat is now your infinite, private cloud drive. Create folders, upload batches, and access your files anywhere.
Storage System: Smart Hybrid Architecture
TG Drive employs a Smart Hybrid Storage engine that automatically routes data based on file size, transfer speed, and privacy requirements:
MTProto Direct (High Privacy)
- • Handles files up to 2.0 GB.
- • Peer-to-Peer GramJS connection.
- • Chunks stored in personal Saved Messages.
- • Zero middleman, absolute privacy.
Bot API Gateway (Metadata & Fast Sync)
- • Fast thumbnail and profile picture fetching.
- • Fallback routing for files under 20 MB.
- • Secondary OTP delivery channel.
- • Reduces main MTProto connection strain.
How It Works: Virtual File System (VFS)
TG Drive acts as an intelligent client-side bridge between your browser and Telegram. It builds a Virtual File System (VFS) by tagging messages with structured JSON-serialized metadata prefixes:
// VFS Message Tagging Structure
{
"prefix": "#TG_DRIVE_FILE#",
"meta": {
"fileName": "Project_2026.zip",
"parentId": "root_vault",
"totalSize": 2147483648,
"isMultipart": true,
"parts": 4,
"encrypted": true
}
}
When downloading, TG Drive fetches the raw MTProto chunks via GramJS to reconstruct the file in-flight, streaming directly to disk through our Service Worker.
Storage Logic & Quota Breakdown
TG Drive utilizes a visual 9999 TB Quota in the dashboard to represent the virtually unlimited nature of Telegram's Saved Messages storage.
The real-time donut chart categorizes your cloud files into five distinct groups: Images, Videos, Apps & Zips, Documents, and Others.
Transfers Manager & Concurrency Queue
Aggregate Progress Bar
A floating progress pill at the bottom calculates overall transfer percentage, total data volume, and active speed across all active transfers.
Detailed Queue Management
View real-time upload and download speeds (MB/s), estimated completion times (ETA), chunk progress, and granular cancel/pause controls.
100-File Batch Uploads
Queue up to 100 files simultaneously. Chunk streaming ensures smooth background execution without UI freeze.
3-Download Concurrency Limit
Downloads are managed by an automated 3-concurrency limiter, preventing Telegram FLOOD_WAIT errors and browser memory crashes.
Real-Time Cloud Synchronization
Any action performed in TG Drive—uploading, moving, renaming, or deleting—instantly syncs with Telegram cloud history via MTProto update listeners.
Stateless Auto-Recovery: Clearing browser cookies or logging in from a new machine requires zero manual backups. All files, tags, and folder trees auto-recover within seconds.
Favorites & Trash: Star favorite files for instant access, or recover deleted items from the virtual Trash container with a single tap (or Alt + R).
Frequently Asked Questions (FAQ)
Is TG Drive safe?
Yes. TG Drive runs 100% client-side using official MTProto 2.0 protocols. Your credentials, session keys, and files never pass through any intermediate server.
What is the maximum file size?
A strict 2.0 GB per-file upload limit is enforced, adhering to Telegram's standard document size boundaries.
Why do I need a Bot Token?
The Bot Token handles high-speed metadata querying, profile avatar fetching, and optional OTP code delivery without burdening your personal MTProto session.
How does Master PIN / Password Recovery work?
Clicking "Forgot Password" lets you choose between Saved Messages MTProto delivery (0% bot ban risk) or Telegram Bot. Entering the 6-digit OTP resets your vault PIN while keeping your Telegram session active.
How does Multi-Device Sync work?
Zero-touch automated sync. Vault salt and canary tokens are published to #TG_DRIVE_VAULT_CONFIG# in Telegram Saved Messages. Secondary devices detect this automatically on login—entering your Master PIN unlocks the vault immediately.
What are the concurrency and batch upload limits?
Up to 100 files can be uploaded per batch, and downloads are limited to 3 simultaneous transfers to eliminate Telegram FLOOD_WAIT rate limits.
What is Privacy & Stealth Shield?
Independent client-side frosted blur toggles for your Telegram username, phone number, and media thumbnails. Hovering reveals them instantly, keeping account details confidential in public.
How do Desktop Right-Click Menus and Drag-and-Drop work?
Right-click any file card to download, star, rename, view info, or trash. Right-click blank space for folder options. Drag files directly from your desktop into the browser for batch uploads.
Why does TG Drive ask for my Old PIN after logging out and re-logging in instead of creating a New PIN?
When you log out from TG Drive and log back in to the same Telegram account, TG Drive immediately requests your existing (old) Master PIN rather than asking you to set up a new PIN. This behavior is a core safeguard of TG Drive's decentralized zero-knowledge architecture:
- Saved Messages Cloud Anchor: Your vault config (salt, canary token, and device slots) is anchored directly in your personal Telegram Saved Messages under
#TG_DRIVE_VAULT_CONFIG#. - Logout Only Wipes Local Cache: Logging out purges local browser storage (IndexedDB, Dexie VFS DB, RAM keys) and revokes that single MTProto session. It does NOT delete your Telegram account, files, or the
#TG_DRIVE_VAULT_CONFIG#message in Telegram. - Protecting Existing Files (Key Continuity): All previously uploaded files were encrypted with a 256-bit AES-GCM key derived from your Old PIN + Cloud Salt. If TG Drive let you create a "New PIN" upon re-login, it would derive an entirely different key. That new key would fail decryption tags on every existing file—making all your previous photos, videos, and documents permanently unreadable and corrupted!
- Automatic Vault Detection: Upon re-login, TG Drive scans Saved Messages, discovers
#TG_DRIVE_VAULT_CONFIG#, and prompts for your Old PIN to unlock your existing cryptographic envelope. - What if you forgot the Old PIN? Click "Forgot PIN / Recover Vault" on the unlock modal, enter your 12-Word Recovery Phrase, and set a new PIN (6-8 digits). Recovering is key-preserving: it verifies the phrase, then keeps the existing vault file key so your previously uploaded files stay readable, re-enrolls this device under a fresh random device seed, and purges the old PIN/legacy slots (the old PIN can never unlock again) while leaving every other device's seed slot intact. A Confirm / Cancel warning is shown first.
What is High E2E Encryption?
High E2E Encryption is TG Drive's client-side End-to-End Encryption tier:
- High E2E Encryption (Standard E2EE): Client-side AES-256-GCM envelope encryption using a per-device key derived from your Master PIN via memory-hard Argon2id (96 MB, 4 passes for new vaults; 64 MB, 3 passes; PBKDF2 100,000-round fallback for legacy vaults). Offers flexible recovery options including the 12-word recovery phrase AND dual-channel 6-digit OTP resets (Saved Messages / Bot). Coexists smoothly with standard MTProto features. Displays a blue "Encrypted" badge with Lock icon.
How does Device Sharing work in High E2E Encryption across my phone and laptop?
High E2E Encryption provides seamless, zero-touch device sharing across multiple devices (Android smartphone, laptop, desktop browser, tablet):
- Decentralized Cloud Anchor: When you enable High E2E Encryption on Device A, TG Drive publishes your public salt and verification canary into your private Telegram Saved Messages under
#TG_DRIVE_VAULT_CONFIG#. Private keys and PINs are never uploaded. - Zero-Touch Cross-Device Discovery: When you open TG Drive on Device B (laptop or tablet) and log in with the same Telegram account, TG Drive automatically detects the vault config and prompts for your Master PIN.
- Local Key Derivation: Entering your Master PIN on Device B derives the exact same 256-bit AES-GCM master key locally in RAM. All encrypted files uploaded from Device A instantly decrypt, stream, and download on Device B.
- Bidirectional Sync: Any file uploaded or encrypted on Device B is immediately readable and decryptable on Device A.
What are the critical security warnings for High E2E Encryption?
#TG_DRIVE_FILE# (file chunk pointers) or #TG_DRIVE_VAULT_CONFIG# (salt & canary) messages inside your official Telegram app's "Saved Messages" chat.
Does TG Drive leak personal info or Telegram data to Firebase?
Absolutely NOT. TG Drive guarantees 100% data isolation between Telegram and Firebase:
- No PII Transmitted: Your Telegram User ID, phone number, username, bot token, session string, file names, file contents, encryption keys, and recovery phrases are NEVER sent to Firebase.
- Zero-PII Daily Aggregates: Firebase only receives anonymous counters (e.g. daily active user counts, country code, browser family) using random non-reversible hashes. No IP address or user identifier is ever stored.
- Complete Offline Operation: Even if Firebase is completely blocked or disabled, TG Drive works at 100% capability directly over Telegram MTProto.
Secure Vault & Zero-Knowledge E2EE Architecture
Complete Cryptographic Architecture & Lifecycle Documentation
TG Drive enforces strict Zero-Knowledge End-to-End Encryption (E2EE). All sensitive credentials, session keys, and files are encrypted client-side inside device memory before touching any network connection or cloud server.
Cryptographic Technical Specifications
| Parameter | Standard / Value | Security Benefit |
|---|---|---|
| Cipher & Mode | AES-256-GCM | Authenticated encryption; detects tampering and bit-flipping. |
| Key Derivation (KDF) | Argon2id (PBKDF2 legacy fallback) | Memory-hard KDF that starves GPU/ASIC cracking; older vaults keep PBKDF2 for byte-identical key continuity. |
| KDF Cost Parameters | 96 MB / 4 passes (new vaults) | Scales down automatically on low-RAM devices instead of weakening the algorithm. |
| Entropy Salt | 128 bits (16 bytes CSPRNG) | Prevents rainbow table pre-computation across different accounts. |
| Initialization Vector (IV) | 96 bits (12 bytes unique/chunk) | Zero IV reuse guarantee across every single encrypted file and session payload. |
| Authentication Tag | 128 bits (16 bytes) | Guarantees cryptographic integrity before ciphertext is unpacked. |
| Canary Token | "TG_DRIVE_VAULT_TEST" | Enables 100% reliable instant PIN validation without corrupting data state. |
| Cloud Sync Anchor | Telegram Saved Messages | Zero external databases; config stored as #TG_DRIVE_VAULT_CONFIG#. |
| Vault Config Integrity | HMAC-SHA256 | Config is signed and verified on every unlock, so injected slots or a swapped recovery verifier are detected as tampering. |
| Device Seed Wrap | Argon2id (96 MB for new vaults) + throttle | The never-published per-device seed is protected with memory-hard Argon2id and an exponential attempt lockout. |
| Sealed Metadata | AES-256-GCM under an HKDF-SHA256 key | File names, MIME types and folder membership are encrypted (envelope v1.<base64url>, AAD-bound to account + item + key epoch); the real filename is not written to the caption or document attribute. |
| Device Pairing | Ephemeral ECDH P-256 + SAS | A new device is enrolled from an unlocked device over a real-time push approval or a one-time, expiring handshake; the raw file key never travels. |
The 13 Cryptographic Lifecycle Phases
- Phase 1: Entropy & Salt Generation: Generates a cryptographically strong 16-byte random salt using
crypto.getRandomValues(new Uint8Array(16)). - Phase 2: Argon2id Key Derivation: Derives a 256-bit AES-GCM CryptoKey using memory-hard Argon2id (96 MB memory, 4 passes for new vaults; 64 MB, 3 passes for older ones). Because every guess must allocate 96 MB of RAM, GPU/ASIC brute-force farms lose their parallelism advantage. Vaults created before this hardening have no
kdftag and keep deriving with PBKDF2-HMAC-SHA256 (100,000 rounds), so existing PINs and files work unchanged. - Phase 3: Canary Verification Token: Encrypts
TG_DRIVE_VAULT_TESTwith a unique 12-byte IV into vault config for deterministic PIN validation. - Phase 4: Session Credentials Hardening: Encrypts MTProto session string, API ID, API Hash, and Bot Token with AES-256-GCM into IndexedDB (
tg_vault_data) and purges plain text. - Phase 5: Automatic Cloud Sync via Saved Messages: Dispatches tagged message
#TG_DRIVE_VAULT_CONFIG#to Saved Messages. Master keys and PINs are NEVER sent. - Phase 6: Zero-Touch Multi-Device Cross-Unlock: Secondary devices discover the cloud config automatically upon login, unlocking immediately with the same Master PIN. A device without a matching PIN can instead be enrolled over a real-time device-pairing push (the new device sends a request; Phase 1 exchanges the locator short code / QR, then Phase 2 begins only after the unlocking device performs ECDH and publishes its ephemeral public key — the new device then leaves the QR screen for a Verify Code screen showing the identical 6-digit SAS, and the key is released only by Confirm Match / Authorize; a rejection fails the new device's login immediately) or a one-time QR / short-code handshake (ephemeral P-256 ECDH + a compared SAS code that must be confirmed). Delivery also falls back to an active Saved-Messages poll every ~2.5 s while the listener is active, so a dropped socket across networks cannot hide the request. Up to 5 devices can be linked at once (Connected Devices shows a used/5 counter); linking a 6th drops the oldest slot, so that device must be re-linked or recovered.
- Phase 7: File Encryption & Sealed Metadata: File contents are encrypted with a fresh 12-byte IV per chunk. File names, MIME types and folder membership are sealed with AES-256-GCM under a dedicated HKDF-SHA256 metadata key (envelope
v1.<base64url>, AAD-bound to account + item + key epoch), and the real filename is no longer written to the message caption or the Telegram document attribute. Byte size, upload timing and folder names remain visible. - Phase 8: Streaming Chunk-Level Encryption & Decryption: Files are split into 512 KB chunks with individual AES-GCM tags, streaming through Service Worker to disk with RAM usage under 50 MB.
- Phase 9: Android Hardware Biometric Keystore: Integrates with Android BiometricPrompt and Secure Hardware Keystore for fingerprint and facial authentication.
- Phase 10: 12-Word BIP39 Root Seed & Disaster Recovery: A standardized 12-word cryptographic seed enables vault recovery and a Master PIN (6-8 digits for new PINs) reset. Recovery is key-preserving (Confirm/Cancel gated): it keeps the existing vault file key so previously uploaded files stay readable, re-enrolls this device under a fresh random device seed, purges the old PIN/legacy slots, and leaves every other device's seed slot intact.
- Phase 11: Session Termination Watchdog & Safe Logout Safeguard: Intercepts Telegram session revocations, preserves the 12-word phrase in emergency buffer, and enforces two-step confirmation before wiping local caches.
- Phase 12: Config-Leak-Safe Device Seed & Authenticated Config: The shared file key is wrapped by a random 256-bit per-device seed that is never published; the seed is stored locally under memory-hard Argon2id with an exponential attempt throttle (and is never destroyed), while legacy PBKDF2-wrapped seeds keep loading. The published
#TG_DRIVE_VAULT_CONFIG#envelope is HMAC-SHA256 authenticated and verified on every unlock, so an injected slot or swapped recovery verifier is detected as tampering. New device slots never publish a PIN-wrapped file key. - Phase 13: Secure Device Pairing (Two-Phase, ECDH P-256): A new device is enrolled from an already-unlocked device without the recovery phrase. Phase 1 exchanges a locator short code / QR; Phase 2 begins only after the unlocking device performs an ephemeral ECDH exchange and publishes its public key, so the new device derives the identical 6-digit SAS and leaves the QR screen for a Verify Code screen. The key is released only by Confirm Match / Authorize (a Reject fails the new device instantly). Delivery is self-healing (timeout-bounded RPCs, backoff, reconnect, immediate search on reconnect, plus the ~2.5 s Saved-Messages poll). Up to 5 devices per vault; a 6th drops the oldest slot.
High E2E Encryption Architecture
Client-Side Envelope Encryption with Balanced Recovery
High E2E Encryption
Standard E2EEClient-side envelope encryption using AES-256-GCM. Derives per-device keys from your Master PIN via memory-hard Argon2id (96 MB, 4 passes for new vaults; 64 MB, 3 passes for older ones) with a 16-byte random salt. Legacy vaults fall back to PBKDF2 (100,000 rounds) for byte-identical key continuity. The never-published per-device seed that wraps the file key is likewise protected with Argon2id plus an exponential attempt throttle, and the published #TG_DRIVE_VAULT_CONFIG# is HMAC-SHA256 authenticated so tampering is detected on unlock.
- • Dual-Channel Recovery: 12-word seed phrase + OTP reset (Saved Messages / Bot).
- • Seamless Coexistence: Runs smoothly alongside all standard features.
- • Visual Badge: Blue "Encrypted" badge with Lock icon.
Multi-Device Sharing Architecture (Device Sharing in High E2E)
High E2E Encryption is engineered specifically for seamless multi-device workflows (Android native APK, laptop, desktop web, and tablet) without centralized key servers:
Your vault configuration (16-byte random salt, canary verification token, and device slots) is published to Telegram Saved Messages under #TG_DRIVE_VAULT_CONFIG#. Private keys and PINs are never transmitted or saved in Telegram.
Logging into TG Drive on a second device automatically scans Saved Messages, detects #TG_DRIVE_VAULT_CONFIG#, and displays the PIN Unlock prompt without any manual key exports or config transfers.
Entering your Master PIN on Device B derives the identical 256-bit AES-GCM file key in local RAM. All files uploaded from Device A immediately unlock, preview, and download on Device B.
Critical Security Warnings & Best Practices
Never manually delete messages tagged with #TG_DRIVE_FILE# (chunk pointers) or #TG_DRIVE_VAULT_CONFIG# (cryptographic salt and canary) inside your official Telegram Saved Messages chat.
Logging out and re-logging into the same Telegram account always demands your Old Master PIN to maintain key continuity. Setting a new PIN on login is blocked to prevent permanent file corruption.
When setting up TG Drive on a new phone, desktop browser, or tablet, always input the exact same Master PIN configured on your primary device for immediate cross-device unlocking.
Re-Login Cryptographic State Preservation (Why Old PIN is Demanded After Logout)
When you log out from TG Drive and log back into the same Telegram account, TG Drive immediately requests your existing (old) Master PIN rather than asking you to set up a new PIN:
- Decentralized Cloud State Anchor: TG Drive does not use external databases. Vault config (salt, canary token, device slots) lives in Telegram Saved Messages under
#TG_DRIVE_VAULT_CONFIG#. - Logout Scope: Logout purges only local storage (IndexedDB, Dexie VFS DB, RAM keys) and revokes that single session. It does NOT delete your Telegram account, files, or Saved Messages.
- Preventing Permanent Data Corruption (Key Continuity): All existing files were encrypted with a key wrapped by
KDF(Old PIN, Salt)(Argon2id for new vaults, PBKDF2-100000 for legacy vaults). Allowing an unverified "New PIN" would derive a mismatched key, making all your existing photos, videos, and documents permanently unreadable! - PIN Reset via Recovery Phrase: If you forgot your Old PIN, use "Forgot PIN / Recover Vault" with your 12-Word Recovery Phrase to set a new PIN (6-8 digits). Recovering is key-preserving: it keeps the existing vault file key so your files stay readable, re-enrolls this device under a fresh random device seed, purges the old PIN/legacy slots, and leaves every other device's seed slot intact. A Confirm / Cancel warning precedes the step.
Strict Device-Specific Lock (Option A) & Envelope Encryption
Each physical device binds locally to its own cryptographic slot in config.deviceSlots via BOUND_DEVICE_SALT_KEY. All files are encrypted using a single 256-bit sharedFileKey wrapped in each device slot, enabling seamless cross-device decryption while isolating PIN verification per device.
No Account-Level Escrow Key (Zero-Knowledge Integrity)
TG Drive does not use any account-level escrow key. Your vault file key is never derived from public data such as your Telegram user ID, and it cannot be reconstructed from the published #TG_DRIVE_VAULT_CONFIG# message alone — that message holds only public KDF salts, per-device slots (file key wrapped by that device's unpublished random 256-bit device seed; new slots never publish a PIN-wrapped key), an HMAC-SHA256 signature over the config that is verified on every unlock, and the recovery verifier wrapped by your 12-word phrase. To open an existing vault on a new device, log in with the same Telegram account and either enter the same Master PIN used on another device of this vault, or tap Forgot PIN / Recover Vault with your 12-word recovery phrase to set a different PIN. On a brand-new device the client refuses to fabricate a second, mismatched file key: if it cannot recover the existing key (via the same PIN or the recovery phrase) it blocks setup with a clear message. There is only ever one vault file key. Legacy vaults that still carry the deprecated escrow field have it removed automatically on the next republish.
Multi-Device Sync Without Central Servers
TG Drive eliminates centralized key servers by using personal Telegram Saved Messages as a decentralized state anchor. The #TG_DRIVE_VAULT_CONFIG# message contains only public salt and canary ciphertext. Logging in on a laptop or phone discovers this config automatically, enabling cross-device unlock with zero manual steps.
Accidental Deletion Self-Healing
If #TG_DRIVE_VAULT_CONFIG# is accidentally deleted in Telegram, encrypted files are NOT lost. Any active client with local salt auto-republishes the config on its next background check. If all devices are logged out, entering your 12-word recovery phrase reconstructs the vault config immediately.
Remote Telegram Session Revocation Watchdog
When a session is terminated from Telegram Devices, TG Drive intercepts AUTH_KEY_UNREGISTERED, holds your 12-word recovery phrase in volatile in-memory only (it is never written to disk), and presents the Session Safeguard Modal with Copy and Download as .TXT buttons before allowing cache clearance.
8-Tier Local Cache Purging on Final Logout
Confirmed logout invokes server-side MTProto Api.auth.LogOut() followed by an 8-tier local purge: IndexedDB session strings, Dexie VFS metadata, Browser Cache API thumbnails, in-memory blob URLs, LocalStorage accounts, SessionStorage tabs, and Android Biometric Keystore enclave keys.
Desktop Experience & Keyboard Shortcuts
Privacy, Stealth Shield & Security
TG Drive enforces strict zero-knowledge policies. We do not track, log, or store any personal data or Telegram credentials on external servers. Session Keys and encryption secrets are securely kept in local device memory and client-side IndexedDB.
Zero Data Storage
We never store your tokens, keys, file names, or metadata on external servers. Everything stays on your local device.
Zero-PII Telemetry
Firebase only records anonymous daily usage counters (DAU, country, device family). Never your user ID, phone, files, or IP.
Stealth Blur Shield
Independently blur username, phone number, and thumbnails with smooth hover reveals for public privacy.