CEClipper Emsa Pro

Google OAuth Verification

Application Use Case

Clipper Emsa Pro is a web app that creates short video clips and uploads approved generated videos to the user's own YouTube channel after the user grants Google OAuth permission.

Primary User-Facing Use Case

The primary use case is creator-authorized YouTube video upload. A user connects a Google account, authorizes YouTube upload permission, prepares a short video through the Clipper workflow, and allows the app to upload the generated MP4 to the connected YouTube channel.

Who uses it

Content operators, creators, or account owners who manage a YouTube channel and want to turn approved source material into short vertical uploads.

What the user sees

A public app site, YouTube OAuth test page, dashboard workflow status, generated media metadata, upload result, YouTube video ID, and publish URL.

Why Google OAuth is needed

The app cannot upload to the user's YouTube channel unless the user grants permission through Google's OAuth consent screen.

What is uploaded

Only the final user-approved generated short video and its metadata, such as title, description, tags, category, and privacy status.

Workflow

  1. User opens Clipper Emsa Pro and adds or selects a source video link or queue item.
  2. The app processes the content into a short vertical clip and creates publishing metadata.
  3. User connects YouTube through Google OAuth if YouTube upload is enabled.
  4. The app requests only the YouTube upload scope.
  5. After consent, the app stores the refresh token server-side for scheduled upload jobs.
  6. When the clip is ready, the app generates a short-lived access token and uploads the video to YouTube.
  7. The app records the upload result so the user can see the YouTube URL and status.

Acceptable Use Alignment

The app aligns with a user-facing content publishing use case: the user grants access so Clipper Emsa Pro can upload generated videos to a YouTube channel the user controls. The app does not use Google user data for hidden background profiling, advertising, data resale, unrelated analytics, or training generalized AI models.

Not Part of This Google OAuth Use Case