Privacy Policy
Last Updated: June 11, 2026
Introduction
We value your privacy and only access Google user data necessary to provide the core functionality of this application. SendToYTBot is a Telegram bot that allows users to upload video files directly to their own YouTube channel. All Google data accessed by the app is used solely to authenticate the user and perform uploads on their explicit request.
Data Accessed
This app requests the following Google OAuth scope:
What this scope grants: Write-only permission to upload videos to the authenticated user's own YouTube channel. This scope does not grant read access to any YouTube data.
Specific data accessed:
- Written to Google: Video file content, video title, and video description — provided directly by the user when they send a file to the bot.
- Received from Google: After a successful upload, Google returns the video ID and video URL. This data is passed back to the user and is not stored by the app.
- OAuth credentials: Google provides an OAuth access token, refresh token, and token expiry time during the authorization flow. These are stored to maintain the user's connection without requiring re-authorization.
Data explicitly NOT accessed: This app does not access, read, or collect any of the following Google user data: YouTube channel details or statistics, existing videos or playlists, watch history, subscriptions, comments, YouTube analytics, Google profile information (name, email, profile photo), Google Drive, Gmail, or any other Google service data.
Purpose: Enables the bot to upload video files sent by the user to their own YouTube channel on their explicit request.
Justification: This is the minimum scope required to provide the app's core functionality. No narrower scope can achieve authenticated video uploads to a user's own channel.
This app's use of Google API Services is subject to the YouTube API Services Terms of Service and the Google API Services User Data Policy.
How We Use Your Data
Google user data is used exclusively for the following purposes:
- Authenticate the user's YouTube account via OAuth 2.0
- Upload video files to the user's YouTube channel when explicitly requested
- Refresh authentication tokens to maintain an active connection
No other processing of Google user data occurs. All uploads happen in direct response to a user action (sending a video file to the bot).
Data Sharing
- Google user data is never shared with third parties under any circumstances
- No third-party analytics, advertising, or tracking services have access to any user data
- Data is transmitted only between the bot's server and the Google/YouTube APIs to perform the requested upload
- No Google user data is used for any purpose other than providing the core upload functionality
Data Storage & Protection
What is stored
The following data is stored in a secured database to maintain your YouTube connection between sessions:
- Your Telegram user ID
- Your Google OAuth access token and refresh token
- Token expiry time
No video content is stored. Files are downloaded, uploaded to YouTube, and immediately deleted from the server.
Security
- All communications with Google services use HTTPS/TLS encryption
- OAuth tokens are stored in an encrypted-at-rest database and never exposed to third parties
- The database is not publicly accessible
Data Retention & Deletion
Retention policy
OAuth tokens are stored until the user explicitly disconnects their account. Video files are deleted from the server immediately after the upload completes or fails.
How to delete your data
Send /disconnect to the bot at any time. This immediately deletes all stored tokens from the database and revokes the bot's access to your YouTube account.
You can also revoke access directly through your Google Account at myaccount.google.com/permissions.
User Rights & Control
Revoking access
- Send
/disconnectto the bot — this deletes all stored data and calls Google's token revocation endpoint immediately - Or visit your Google Account security settings and remove "SendToYTBot" from connected apps
- Either method permanently stops all access
Transparency
- You are prompted for explicit consent via Google's OAuth screen before any YouTube access is granted
- All uploads occur only at your direct request by sending a video file to the bot
For questions or support: gritty.cowled_7a@icloud.com