Google OAuth Verification
OAuth Scopes Justification
Clipper Emsa Pro requests the minimum Google OAuth scope needed for its user-facing YouTube upload feature.
| Requested scope | https://www.googleapis.com/auth/youtube.upload |
|---|---|
| Purpose | Upload a final generated short video to the YouTube channel authorized by the user. |
| API used | YouTube Data API v3 video upload endpoint for creating a resumable upload session and uploading the MP4 file with snippet and status metadata. |
| Why this is minimum | The app needs to insert/upload videos. Read-only scopes cannot upload, and broader YouTube scopes would grant unrelated access that the app does not need. |
Why youtube.upload Is Required
The core user action is publishing the generated short video to the user's YouTube channel. The app must be able to create a YouTube upload session and send the final MP4 file plus user-visible metadata such as title, description, tags, category, made-for-kids setting, and privacy status.
Scopes Not Requested
Clipper Emsa Pro intentionally does not request broader or unrelated Google scopes:
https://www.googleapis.com/auth/youtubeis not requested because broad management of the user's YouTube account is not needed.https://www.googleapis.com/auth/youtube.force-sslis not requested because the app does not need to edit comments, ratings, captions, or permanently delete YouTube videos.https://www.googleapis.com/auth/youtube.readonlyis not requested because reading YouTube account data is not the user-facing feature.- Gmail, Drive, Calendar, Photos, Analytics, and Workspace scopes are not requested.
Scope Use In The App
- User clicks the YouTube connection button in the app.
- The app redirects the user to Google OAuth with only
youtube.upload. - After consent, the app stores the refresh token server-side.
- When a user-approved clip is ready, the app refreshes a short-lived access token.
- The app uploads the generated MP4 and receives a YouTube video ID and URL.
- The app stores the upload result for user-visible status, audit, duplicate prevention, and troubleshooting.
Public API Keys and Source Discovery
The app may use public source video URLs or API-key based discovery for queue building. That does not require Google OAuth user data. The OAuth scope described on this page is only for uploading videos to a user's YouTube channel after consent.
Limited Data Handling
The app does not use the requested scope to read unrelated private data, sell data, serve ads, train generalized AI models, or provide data to information resellers. See the Privacy Policy for storage, sharing, retention, security, and deletion details.