Clip Launch is a privately operated/internal tool. This policy describes its use of Google OAuth 2.0 and the YouTube Data API for authorized YouTube publishing workflows.
Information We Access
When a user authorizes Clip Launch through Google OAuth, the application may access information made available through the permissions granted to it and required by the YouTube Data API. This authorization is used for requested YouTube publishing operations, not merely for account login. The information may include:
- YouTube channel identification and basic channel information needed to identify the authorized channel.
- Video metadata, including titles, descriptions, privacy settings, scheduling information, and upload status.
- Information about videos uploaded through Clip Launch, including YouTube video IDs.
- OAuth authorization credentials or tokens required to access the authorized YouTube account.
Clip Launch may also process content supplied locally by the user for a publishing job, including video files, thumbnail files, titles, descriptions, and scheduled publication times.
How Information Is Used
Information is used only to provide Clip Launch's publishing workflow, including:
- Authenticating the user's authorized YouTube account.
- Uploading videos and custom thumbnails.
- Setting or updating video titles, descriptions, privacy settings, and scheduling settings.
- Scheduling videos through YouTube's native scheduling functionality.
- Retrieving upload results, video IDs, and upload status.
Google User Data
Google user data received through Google APIs is used only to provide Clip Launch's YouTube publishing integration and the specific functions described in this policy. Clip Launch does not sell Google user data, does not use Google user data for advertising, and does not share Google user data with unrelated third parties.
OAuth tokens may be stored locally or securely by the application so that the authorized user does not need to authenticate again for every publishing job. Local video files, thumbnails, and job details may also remain in the application's local configuration or working storage as needed to operate the tool. Clip Launch does not retain data longer than necessary for these purposes.
Clip Launch's use of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements where applicable.
Data Retention and Account Access
Application data is retained only as necessary to operate Clip Launch and complete or track authorized publishing jobs. The user can revoke Clip Launch's access at any time through the Google Account permissions page. Locally stored Clip Launch credentials and configuration can also be removed by deleting the application's stored configuration.
Data Security
Reasonable measures are used to protect authentication credentials and application data, including limiting access to the privately operated application and avoiding unnecessary collection. No method of storage or transmission is completely secure, and Clip Launch cannot guarantee absolute security.
Third-Party Services
Clip Launch uses Google's OAuth and YouTube Data API services. Those services are operated by Google and are governed by Google's own policies and terms. Clip Launch does not control Google's handling of information once it is processed by Google services.
Contact
For questions about this policy or Clip Launch's handling of information, contact contact@cliplaunch.net.