LK BotVerse
Legal & Trust Compliance
Google Limited Use Verified • Strict Ephemeral In-Transit Security

Privacy Policy

Full disclosure regarding Google OAuth 2.0 authorization, zero-retention cloud streaming, and comprehensive file management operations across the LK BotVerse Telegram fleet.

verified Official Channel
Effective Date November 6, 2026
Security Architecture AES-256 • TLS 1.3
Official Domain https://lkbotverse.store
Compliance Status
Google Verified / Zero-Log
policy

Universal Privacy Policy

Zero-retention data flow protocols governing Telegram bots & Mini-Apps

Audit Ver. 4.2
verified Google API Services User Data Policy Compliance

LK BotVerse's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Strict Limited Use • No AI/ML Training Permitted
Clause 1.0

1. Google Drive API Scopes & File Management Operations

Google Scopes

When you connect your Google Account with our G.Drive Uploader Telegram bot (@GDUploader_LKBot), we request permissions via Google OAuth 2.0 to perform user-directed file management tasks. We specifically handle:

upload File Uploading

Transferring files, media, archives, and documents sent by you on Telegram directly into your designated Google Drive folders or Team Drives.

edit File Renaming

Modifying the display names and file extensions of files stored in your Google Drive as instructed by your Telegram commands.

delete File Deletion

Removing and permanently purging selected files from your Google Drive storage upon your explicit confirmation and command.

drive_file_move Moving & Organization

Relocating files between directories, creating subfolders, and organizing storage paths across personal and shared Team Drives.

lock User-Initiated Actions Only

The bot never modifies, moves, renames, or deletes any file automatically or autonomously. Every single operation requires an explicit, authenticated command issued directly by the user via Telegram.

psychology_alt Strict AI / Machine Learning Prohibition

We explicitly confirm that user data obtained through Google Workspace APIs or Google Drive APIs is never used to develop, train, fine-tune, or improve generalized Artificial Intelligence (AI) or Machine Learning (ML) models.

Clause 2.0

2. Information We Collect

Minimal Scope

To deliver cloud file management utilities, we collect only the minimal information strictly required:

  • key
    OAuth 2.0 Authentication Tokens: When you authorize Google Drive, Dropbox, or OneDrive, we receive OAuth 2.0 access and refresh tokens. These tokens enable the bot to authenticate authorized API calls (upload, rename, delete, move, edit) strictly on your behalf.
  • badge
    Telegram Profile Identifiers: Your unique Telegram User ID is stored solely to map your authorization session and bot preferences to your Telegram account.
  • description
    Transient File Metadata: During active file management tasks, our servers temporarily process file names, sizes, paths, and MIME types solely to display progress bars and execute the requested command.
Clause 3.0

3. Ephemeral In-Transit Processing & Zero Storage

Zero Disk Retention

Files processed through our bots are handled as high-speed data streams in volatile system RAM. We do not permanently store, mirror, download, or inspect the contents of your files on server hard drives. Once an operation completes, all memory buffers are purged immediately via POSIX memory unmapping.

Data Categories LK BotVerse Never Records:
  • cancel User file payloads or file contents
  • cancel Chat message histories or personal logs
  • cancel Plaintext Google or Microsoft passwords
  • cancel Telemetry linking files to personal identity
Clause 4.0

4. Information Sharing & Third-Party Disclosure

No Data Sales

We do not sell, rent, trade, lease, or monetize your personal information or credentials under any circumstances.

User data is communicated only to official third-party cloud APIs (such as Google Drive APIs, Dropbox API, Microsoft Graph API) strictly when you initiate an operation. We never share user data with advertisers, third-party analytics trackers, or data brokers.

Clause 5.0

5. Data Security & Storage Standards

AES-256 Verified

We implement stringent security protocols to safeguard your credentials and files:

lock AES-256 at Rest

All stored OAuth 2.0 tokens and database records are encrypted with industry-standard AES-256 encryption.

shield TLS 1.3 in Transit

All communications between users, Telegram APIs, and cloud providers are encrypted using modern Transport Layer Security.

visibility_off Zero File Access

Files are never accessed, opened, or analyzed for commercial or algorithmic purposes.

Clause 6.0

6. User Controls, Token Revocation & Data Deletion

1-Click Purge

You have full autonomy over your credentials and cloud connections at all times:

terminal
In-Bot Revocation: Send /revoke or /logout to any LK BotVerse bot. This immediately and permanently deletes your OAuth credentials from our active database.
link_off
Google Account Security Dashboard: You can revoke LK BotVerse permissions directly via Google Account Security at https://myaccount.google.com/permissions.
mail
Direct Deletion Request: Contact the developer directly at lakshan.bandara.dev@gmail.com, and all associated session data will be permanently wiped within 24 hours.
Clause 7.0

7. Children's Privacy

Under 13

Our services are not intended for individuals under 13 years of age. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with credentials or personal information, please contact us immediately for deletion.

Clause 8.0

8. Developer & Support Contact

Support Hub
Primary Developer Email lakshan.bandara.dev@gmail.com For security audits, data deletion requests, and administrative queries.
Telegram Channel & Support @LKBotsUpdates Real-time developer fleet status and community inquiries.
lock_clock Verified Protocol Integrity • Real-Time Cloud Security

Questions regarding your cloud tokens or permissions?

Connect directly with the maintainers in our official channel. Get real-time changelogs, status alerts, and instant protocol revisions.