Last Updated: October 2026
Welcome to the Privacy Policy for DS GDrive Bot, developed by the DS GDrive Bot Team. Your privacy and security are our highest priorities. This policy explicitly outlines how we collect, use, protect, and handle your data when you use our Telegram bot to interact with cloud storage protocols.
Because our ecosystem operates on a dual-bot model, the data and permissions we request depend on which bot you are using:
This bot operates as a verified Google application using our own Client ID and Client Secret. We strictly request the limited auth/drive.file scope. This means we securely collect and store your generated OAuth access/refresh tokens, but the bot can only access, view, or modify files that it directly created. It cannot read your preexisting personal Drive files.
To provide unrestricted full Drive access (auth/drive) without compromising your privacy, the Pro Bot utilizes a BYOC architecture. You generate and provide your own Google Cloud Developer credentials. You act as the developer of your own application. We securely store the credentials.json file and tokens you provide strictly to automate file processing on your behalf, acting solely as an authorized client interface.
We will use your data solely to provide you with the services you requested. Specifically, your OAuth tokens and credentials are used to stream files from Telegram directly into your private cloud storage, clone links, and allow you to manage (rename, delete, move) your files directly from the Telegram interface. We do not use your data for advertising, market research, or to train artificial intelligence models.
We do not sell your data to third parties. We do not transfer or disclose your information to third parties for purposes other than the ones provided (providing the core file-transfer service), unless explicitly required by applicable law.
Security procedures are in place to protect the confidentiality of your data. We use industry-standard encryption to protect your information, specifically securing your OAuth tokens and BYOC credentials both in transit and at rest. No human developer or third party is permitted to access, read, or download your personal cloud files.
We retain your encrypted tokens and credentials only for as long as you maintain an active connection with the bot. We do not permanently store your actual files on our transit servers. You may revoke the bot's access at any time via your Google Account security settings, or by deleting your BYOC credentials from your Google Cloud Console. To request immediate deletion of any stored user data or tokens from our database, you can contact the developer team directly.
Because our primary interface is operated via Telegram, we do not utilize web tracking cookies or fingerprinting scripts. Backend operational logs are kept strictly for maintaining system integrity, diagnosing errors, and preventing abuse. These logs are automatically rotated and securely purged.
DS GDrive Bot'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.