None. YouTube Bulk Editor does not collect, store, transmit, or share any personal data, video data, usage data, or analytics of any kind.
By using YouTube Bulk Editor, you agree to be bound by the YouTube Terms of Service. This tool accesses the YouTube Data API v3 and is subject to the YouTube API Services Terms of Service and the Google Privacy Policy.
This tool uses Google OAuth 2.0 to authenticate you with YouTube. Here is exactly what happens:
#token=...). URL fragments are never sent to servers or written to server logs.sessionStorage only. It is never written to any database, file, or external service.sessionStorage and revoked at Google immediately.All YouTube API calls - reading your video list, reading metadata, saving edits - go directly from your browser to the YouTube Data API v3. Our backend server is never involved in these requests. Your video titles, descriptions, and tags never pass through our server at any point.
Our backend is a small server hosted on Google Cloud Run (Mumbai, India). It handles exactly two things:
The server has no database connection. It does not log requests. It does not store tokens. The complete source code is publicly readable at github.com/imchikachirag/youtube-bulk-editor.
No third-party analytics, advertising, tracking, or data-sharing SDKs are used. The only external services this tool communicates with are:
All three are Google services subject to Google's Privacy Policy.
This tool does not use cookies of any kind.
This tool is intended for YouTube channel owners and managers. It is not directed at children under 13.
If this policy changes, the updated date at the top of this page will be updated. Since we collect no data, there is nothing substantive to change.
Since YouTube Bulk Editor stores no data about you, there is nothing to delete on our end. Your OAuth access token exists only in your browser's sessionStorage for the duration of your session and is automatically removed when you close the tab.
To revoke this tool's access to your YouTube account at any time:
Either method fully and permanently removes this tool's access to your YouTube account.
YouTube Bulk Editor accesses the following Google user data via the YouTube Data API v3:
The app requests the minimum scopes necessary: youtube.force-ssl for reading and updating video metadata, and youtube.readonly for reading channel and video data.
The data accessed is used solely to display your video library in the editor interface and to apply the title, description, and tag edits you make back to your YouTube channel via the YouTube Data API. No data is used for any other purpose including advertising, analytics, profiling, or training machine learning models.
YouTube Bulk Editor does not share any Google user data with any third parties. There are no analytics services, advertising networks, data brokers, or other external services that receive your data. The only external service the app communicates with is the YouTube Data API (googleapis.com) to read and update your video metadata on your behalf.
YouTube Bulk Editor stores no Google user data. The OAuth access token is held exclusively in your browser's sessionStorage for the duration of your active session. It is never written to any database, file, server log, or external service. Our backend server (Google Cloud Run) performs only the one-time OAuth code exchange and immediately forwards the token to your browser - it does not retain the token or any user data at any point. The complete server source code is publicly available at github.com/imchikachirag/youtube-bulk-editor for independent verification.
Since no Google user data is stored by YouTube Bulk Editor, there is no data to retain or delete on our end. The OAuth access token exists only in your browser's sessionStorage and is automatically removed when you close the browser tab.
To permanently remove this app's access to your Google account:
Questions about this privacy policy? Contact Chirag Mehta at jain.chirag+youtubebulkeditor@gmail.com or on Twitter at @imchikachirag.