About This Application
Railway Research Desk (youtube.com/@RailwayResearchDesk) is a private, single-owner digital publishing tool operated by Rahul Sarkar. It prepares original educational short-form videos in Bengali explaining Indian Railways rules and has prepared code to upload them with a title, description and a first source-citation comment exclusively to the operator's own YouTube channel (Channel ID: UCrZGJ4wCSgXda0BwSUaQbvQ) via the YouTube Data API v3.
This application is strictly an internal automation tool for its sole owner. It is not offered to the public, has no external user sign-ups or accounts, and never reads, collects, or modifies any other user's YouTube data.
YouTube API Services Disclosure
This application uses YouTube API Services. By using or viewing this service, you agree to be bound by the YouTube Terms of Service. Google's handling of data is governed by the Google Privacy Policy. The operator can revoke this application's access to Google data at any time via the Google Security Permissions page.
Business & Compliance Contact
Operator: Rahul Sarkar
Business Email: rahul.business001@gmail.com
Privacy Policy
Effective Date: October 15, 2026
1. Operator & Scope
Railway Research Desk is operated solely by Rahul Sarkar (the "operator"), who is also its only user. The application does not collect personal data from website visitors or YouTube viewers.
2. Google User Data Accessed
The application accesses Google account data only after the operator explicitly signs in via Google OAuth 2.0 and approves the consent screen for the operator's own YouTube channel. The prepared upload-and-comment configuration uses these YouTube Data API v3 scopes:
https://www.googleapis.com/auth/youtube.upload— to upload the operator's original video files to the operator's own YouTube channel.https://www.googleapis.com/auth/youtube.force-ssl- for the prepared first-comment feature, posting the operator's official source citations below the operator's own uploaded videos.
The prepared module includes video upload, a source-citation first comment, authorized-channel verification and a recent-upload duplicate lookup. It remains OFF and has not been activated or deployed. The restored features have offline mock tests only; no live first-comment or end-to-end test has been performed. Google Cloud Console lists youtube.upload and youtube.force-ssl again. The previously issued OAuth token has not been changed or reauthorized. The application is intended only for the operator's own channel.
3. Data Storage, Limited Use & Sharing
- OAuth credentials used for the completed upload tests are stored in a private working directory with owner-only file permissions (
0600). An encrypted credential backup is also retained. The prepared script has not been deployed to the operator's server. - The prepared script uses a local SQLite database for video IDs, upload-session progress, status, pending comment text, errors, timestamps and daily quota counts. Pending comment text is retained for retry and deleted with its upload-state row at the same 30-day cutoff. Comment text is cleared from completed upload rows when the database is opened or used. Existing test-result files are separate from this database.
- No YouTube API data is sold, shared with third parties, used for advertising, or used to train machine learning models. Railway Research Desk's use and transfer of information received from Google APIs strictly adheres to the Google API Services User Data Policy, including its Limited Use requirements.
4. Data Retention, Deletion & Revoking Access
The prepared, locally tested script deletes SQLite upload-state records, including any stored pending comment text, aged 30 days or more when the database is opened or used. Age is measured from first storage in the revised code, not the most recent retry. Legacy records use their last known timestamp; records with missing or invalid timestamps are deleted. Daily quota rows are also removed at the 30-day cutoff. The script provides an offline --purge-only --state-db PATH maintenance command. This copy is not deployed and no daily maintenance schedule is active. If the script is stopped, cleanup waits until its next run; calendar-time cleanup requires a separately configured scheduled maintenance run. OAuth credentials and encrypted credential backups are excluded so authentication is not silently broken. Separate test-result files, external logs, backups, source media and videos stored on YouTube are not deleted by this database purge. These local files require separate manual deletion. Revoking Google access does not itself delete local copies. For deletion requests, contact rahul.business001@gmail.com. No blanket 30-day deletion guarantee is made for all data.
Access to Google data can be revoked immediately at any time on the Google Security Permissions page (https://myaccount.google.com/permissions).
5. Google Privacy Policy
Use of YouTube API Services is also subject to the Google Privacy Policy.
Terms of Service
Effective Date: October 15, 2026
1. YouTube Terms of Service
By using Railway Research Desk, you agree to be bound by the YouTube Terms of Service and the YouTube API Services Terms of Service.
2. Educational Purpose & Disclaimer
All content published by Railway Research Desk is for educational and public legal awareness regarding Indian Railways rules. It does not constitute formal legal advice, and Railway Research Desk is an independent research initiative not affiliated with Indian Railways or IRCTC. Official government Gazette notifications and circulars always prevail.
3. Permitted Use & No Warranty
This software is a private internal tool for its operator and is provided "as is" without warranties of any kind. Contact: rahul.business001@gmail.com.
Official Primary Sources Referenced
Our educational videos cite official public notifications from: