Privacy Policy

1. Google Drive API Scopes & Complete File Management Operations

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

• File Uploading: Transferring files, media, archives, and documents sent by you on Telegram directly into your designated Google Drive folders or Team Drives.
• File Renaming: Modifying the display names and file extensions of files stored in your Google Drive as instructed by your Telegram commands.
• File Deletion: Removing and permanently purging selected files from your Google Drive storage upon your explicit confirmation and command.
• File Moving & Folder Organization: Relocating files between directories, creating subfolders, and organizing storage paths across personal and shared Team Drives.
• File Editing & Metadata Management: Updating file descriptions, captions, and access settings for files managed by the bot.

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.

No AI / ML Training: 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.

2. Information We Collect

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

• 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) on your behalf.
• Telegram Profile Identifiers: Your unique Telegram User ID is stored solely to map your authorization session and bot preferences to your Telegram account.
• 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.

3. How We Use and Process Data

We use the collected information exclusively to:

• Execute user-requested file operations: uploading, renaming, deleting, moving, and editing files in your connected cloud storage.
• Maintain your authenticated session so you don't have to log in on every individual command.
• Provide status feedback, progress bars, and direct link generation upon task completion.
• Ensure service security, prevent quota abuse, and maintain bot stability.

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

4. Information Sharing & Third-Party Disclosure

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.

5. Data Security & Storage Standards

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

• AES-256 Encryption at Rest: All stored OAuth 2.0 tokens and database records are encrypted with industry-standard AES-256 encryption.
• TLS 1.3 Encryption in Transit: All communications between users, our systems, Telegram APIs, and cloud storage providers are encrypted using modern Transport Layer Security (TLS 1.3 / HTTPS).
• Zero Unauthorized File Access: Files are never accessed, opened, or analyzed for commercial or algorithmic purposes.

6. User Controls, Token Revocation & Data Deletion

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

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

7. Children's Privacy

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.

8. Policy Updates

We may update this Privacy Policy periodically to reflect new bot features or regulatory standards. Any revisions will be published on this page with an updated Effective Date. Continued use of LK BotVerse services after updates constitute your agreement to the modified policy.

9. Developer & Support Contact

For questions, support, or privacy inquiries, contact the developer directly: